Proposed deployment architecture: SaaS-first delivery with customer key custody, alongside a separately sold self-hosted source stack. Commercial pricing, licensing terms, and support commitments are pending owner approval.
SaaS-first deployment where keys and signing remain under customer custody. First integration target: platform operations.
Full engine source code sold separately for operators requiring internal deployment, complete infrastructure autonomy, and local modification.
Inspect repository architecture, examine signing specifications, and evaluate the non-payable local simulation demo.
Read the quickstart| Dimension | SaaS Platform (Proposed) | Self-Hosted Stack (Separately Sold) | Technical Preview |
|---|---|---|---|
| Deployment model | Hosted control plane (customer keys) | Self-hosted on customer infrastructure | Local repository development |
| Key custody & signing | Customer retained (never leaves tenant) | Customer retained on local nodes | Simulation / ephemeral keys only |
| Source code availability | Client SDK and integration libraries | Full source stack sold under commercial license | Repository inspection and reference docs |
| Commercial pricing | Pending owner approval | Pending owner approval & legal review | Non-commercial evaluation only |
| Licensing terms | SaaS subscription terms pending | Separately sold non-exclusive license pending | Evaluation only — no commercial license |
| Support commitments & SLA | Terms pending approval | Terms pending approval | None — technical preview only |
| Production status | Under active architectural validation | Requires independent operational deployment | Non-payable simulation preview |
The primary planned model is SaaS-first with customer key custody, where the client keeps signing keys and funds under their own control while using a hosted control plane. A full self-hosted deployment with source code is planned as a separately sold commercial edition for operators who run their own infrastructure.
Prices, licensing terms, and billing models are currently under evaluation and have not yet been approved. Neither free perpetual usage nor specific fee schedules are authorized until owner decisions and legal reviews are finalized.
No guaranteed response times, emergency response SLAs, or dedicated engineer assignments are currently approved. Service level commitments will be published only after commercial terms and operational capacity are formalized.
No volume-based fees or percentage-of-custody pricing are approved. The system architecture enforces customer key custody, meaning customer funds never pass through a vendor-held float.
Developers can review the bounded context architecture, examine the signing specifications in the documentation, and test workflows using the non-payable local simulation demo.
Review integration guides and explore the local non-payable simulation demo while commercial terms are finalized.