E / 01
Early tester program

Pick one workflow.
Bring back evidence.

The public tracks run locally from source with synthetic data. Managed discovery is invite-only and starts with fit, safety, and rollback.

01Choose a track

Start with the smallest path that answers your question.

A complete, partial, blocked, or stopped evaluation is useful when the evidence is concrete.

A30-60 min

Toolkit evaluator

Developers building webhook contracts, docs, signing, adapters, or portal experiences.

Run the credential-free smoke workflow, exercise the contract CLI, and tell us where the first useful result becomes unclear.

Open the toolkit guide
B45-90 min

Delivery evaluator

Platform and reliability engineers evaluating outbound webhook infrastructure.

Run a local signed delivery, then exercise PostgreSQL-backed retry behavior without production endpoints or customer data.

Open the delivery guide
C2-4 weeks

Design partner

B2B and API teams with active customer-facing webhooks and a reversible sandbox.

Start with discovery. Managed access is invite-only, keeps the existing delivery path active, and stops when fit or safety is unclear.

Review the tester program
Safety boundary

Local, synthetic, sanitized.

  • Use included contracts and local receivers.
  • Never post payloads, secrets, tokens, or private URLs.
  • Report vulnerabilities through private security channels.
  • Record the exact repository commit and environment.
02Definition of done

A clear stop is as valuable as a smooth finish.

We are looking for decision-quality evidence, not inflated completion rates.

Completed

You reached the intended result and can name what was useful.

Partial

You reached a meaningful midpoint and captured the next gap.

Blocked

You found a reproducible failure with a sanitized trace.

Stopped

The project is not a fit, and the deciding reason is explicit.