Pilot

See it work on your use case.

A pilot environment stood up in minutes with nothing installed on your side.

How a pilot runs

Three steps, no installation on your side.

A pilot is a private sandbox for your company only, shaped around one operation your business actually runs.

STEP 1

Tell us the use case

Which operation, on which network, with which approvals and which systems that need to hear about it. We agree what success looks like.

STEP 2

We stand up your sandbox

Your contracts registered, your policies and approvers configured, on a test network. You receive API keys for your engineers.

STEP 3

Your engineers try it

They call the API, receive the webhooks, break things on purpose and read the failure reports. Then you decide where it runs next.

What to expect

A sandbox that says it is one.

The sandbox exists so you can see everything without putting anything at stake: it holds test keys and uses test networks. It is never used for real value, and it says so wherever it appears.

A sandbox says it is one: in its logs, on its health endpoint and on every screen built over it. It is never supported for value.
Embedded as a library in your Node.js application, or run as a service with an HTTP API described in OpenAPI and generated SDKs.
Every failure comes with a report: the stage, a stable cause, whether a retry can work and on what condition, and the suggested action.
Signed webhooks, retried for about three days, then held in a dead-letter queue an operator can redeliver from.

After the pilot

From sandbox to your own deployment.

The same product runs in your infrastructure with your own keys, or is run for you once the external audit is done. Your integration code does not change: the API is the same in every shape.

Compare the deployment options.

Runs in your infrastructure, as a container image over your PostgreSQL, with schema migrations applied by an explicit command.
Run for you in production without ever holding a key of its own: signing stays on your side or in your own cloud account. Available for pilots
Keys never enter CryptoRail: signing happens in your HSM, your cloud KMS or your own signer, and only the development signer ever touches a key.