Scoped pilot access

Start with the sandbox. Request pilot access when one sensitive action is ready to test.

The sandbox is open. Pilot access is reviewed. Payment happens only after scope approval. Production access is never automatic.

Request Pilot Access Try Sandbox

Choose the right access path.

Start public, then request a reviewed pilot only when a real sensitive-action scenario is specific enough to scope.

Sandbox

Open evaluation for developers and teams.

Scoped Pilot

Founder-reviewed paid pilot for one approved sensitive-action scenario.

DIDX Inquiry

For enterprise, platform, wallet, identity, or strategic discussions.

What scoped pilot access includes.

Scoped means limited by scenario, timing, and review context.

Includes

  • One approved sensitive-action scenario
  • Limited pilot access
  • Receipt examples
  • Basic setup support
  • Pilot summary

Does not include

  • No unrestricted production access
  • No compliance certification
  • No unlimited usage
  • No custom SLA
  • No legal guarantee

How it works.

Payment and access are never automatic from the public page.

1
Submit requestShare the sensitive action, stage, and timeline.
2
Scope reviewThe request is checked for fit and a narrow pilot boundary.
3
Private paymentPayment happens only after scope approval.
4
Scoped accessAccess is issued only after payment confirmation and stays limited to the approved scenario.
5
Receipt trailSensitive access decisions are receipted so the pilot decision path stays reviewable.

Request Pilot Access

This form prepares an email draft to [email protected]. Your email client will open so you can review and send it.

Submitting opens your email client. No access, payment, production use, or approval is granted by this public form.

Your request was received. Pilot access is reviewed for fit and scope. Access is not automatic, and production use is not granted through this form.

Control note: A scoped pilot is manually reviewed by the founder. Access is limited, revocable, and scenario-bound.