Ledger is core, not incidental
Balances, holds, and settlement are central to your product — correctness has to be a platform guarantee.
Design partner program
Shape the ledger you'll build on.
Design partners are a small group of teams building serious value-movement systems who work with us closely during private preview — bringing a real workload, getting direct access to the engineering team, and influencing what the engine becomes.
- Limited cohort
- A handful of teams, not a waitlist
- Direct access
- A line to the engineering team
- Roadmap influence
- Your workload shapes priorities
- Early capabilities
- First to evaluate what's next
A mutual commitment
A partnership, not a trial.
Design partnership works because both sides put something real in. Here's the exchange, stated plainly.
What you get
A line to the engineering team
Talk directly to the people building the engine — not a ticket queue.
Influence over the roadmap
Your workload's needs weigh directly on what we prioritize next.
Early access to new capabilities
Evaluate what's next before it's broadly available.
Hands-on integration support
Help modeling your ledger and wiring the SDK and gateway surfaces.
Evidence for your review board
Correctness and recovery artifacts you can take to architecture and security review.
What we ask
A real workload to model
Actual value-movement patterns from your system — not a toy example.
Regular, candid feedback
Tell us what works, what's missing, and what would block adoption.
A named technical contact
Someone on your side who owns the evaluation and can make decisions.
Willingness to run drills
Participate in controlled recovery and correctness exercises.
Time from your team
A working cadence across the engagement, not a one-off review.
How the engagement works
From first conversation to a working pilot.
A design partnership moves through four stages. Each one has a clear purpose, so both sides know whether to continue.
Fit conversation
We confirm the workload is a fit for a ledger-first engine and that the timing works for both sides.
Scoped evaluation
Architecture review of your value-movement model, mapped onto the write path and reservation lifecycle.
Integration pilot
Wire a representative workload through SDK and gateway surfaces and observe recovery behavior.
Feedback loop
A working cadence where your findings shape fixes and roadmap priorities.
Who it's for
A good design partner looks like this.
You have a real workload
Concrete value-movement patterns and volume you can bring — enough to stress the model meaningfully.
You'll engage closely
A named technical owner and a team ready to give candid feedback across the engagement.
Still private preview: a design partnership is for architecture review, performance review, and controlled integration pilots. It is not a statement of general availability, production certification, or deployment approval — production use still requires deployment-specific security review, operational drills, and validation.
Design partner program
Bring a real workload. Help shape the engine.
Tell us what you're building and what you'd want to influence. Write from your work address and we'll follow up to explore fit.