The Design Partner Program

Build the proof with us.

We’re selecting a small number of design partners in healthcare and financial services. Run a real pilot on CID, get early access and founder-level attention, and shape the verifiable AI infrastructure while the roadmap is still wet.

Apply to the ProgramExplore CID
What founding partners get

Founding partners lock in terms that won’t be offered after launch.

We don’t publish pricing — terms are set in the scoping conversation, in writing, before the pilot begins.

Early access

Run CID before general availability — the full platform, every surface unlocked. Dashboard, CLI, and MCP server from day one.

Founder-level attention

Your pilot is run by the three people who built the platform over two years. Questions go to the engineers who wrote the answer, not a ticket queue.

Shape the roadmap

Your use case becomes a first-class blueprint. Connectors, compliance mappings, and workflow decisions get made with you in the room — while they’re still decisions.

Evidence your auditors can use, early

Every pilot round produces tamper-evident attestations. Your compliance team walks away with verifiable artifacts they can check today.

4–6 wksTo first pipeline run
8–12 wksTo first production federation
2Target industries this cohort
4 / 4Criteria — we should talk this week
What we’re looking for

The program is small by design. Four things make a partnership work.

If you have all four, we should talk this week.

A regulated AI use case

You’re in healthcare or financial services, with a model that a regulator, auditor, or counterparty will eventually ask hard questions about.

Data readiness

Training data that exists, is accessible in your environment, and has an owner. It does not need to be perfect — it needs to be real.

An executive sponsor

Someone with the authority to greenlight a pilot and act on its results. Pilots that report to no one produce evidence that persuades no one.

Willingness to run a real pilot

Defined success criteria, your environment, your data. A sandbox tour proves nothing — and proof is the entire point.

How a pilot works

Five steps, no ambiguity.

First pipeline run in 4–6 weeks; first production federation in 8–12.

Scoping conversation

Thirty minutes with the founders. We map your use case to the platform — or tell you honestly if it isn’t a fit yet.

30 min · founders

Use case + success criteria

We write down, together, what the pilot must demonstrate and how success will be measured. Before anything deploys.

fixed in advance · in writing

Pilot deployment in your environment

BYOC — the platform runs in your cloud accounts. Your data never touches STEAV’s infrastructure.

first pipeline run · wk 4–6

Evaluation against criteria

Results are attested and recorded as they happen — evaluated against the criteria we wrote in step two, fixed in advance.

attested results · yours to keep

Decision point

A clear go/no-go on the evidence. Either way, you keep the attested results — they’re yours.

go / no-go
Apply

Either way, you keep the evidence.

30-minute scoping calls

A scoping conversation is thirty minutes with the founders — and an honest no if it isn’t a fit yet.

Apply to the Program