Design partner
A focused collaboration around one valuable, governed enterprise agent workflow.
- Architecture workshop
- One scoped agent workflow
- Connector and policy mapping
- Data-boundary and deployment review
- Live proof and readiness evidence plan
Private preview
Start with the workflow your risk profile requires.
Commercial prices and quotas are not yet public. We are selecting design partners for workflows that require governed reads, real writes, sensitive-data controls, or customer-controlled execution.
One real workflow. One explicit boundary. One live proof.
Adoption paths
Start now with a partner engagement. Scale into the topology you need.
The managed and enterprise cards describe planned packaging, not currently purchasable plans.
Managed
A guided path toward self-service on a shared regional runtime with conservative defaults.
- Managed control and data plane
- Published connector capabilities
- Baseline policy and protection
- Usage and entitlement controls
- Path to team adoption
Enterprise
Dedicated or customer-controlled topology for stricter security, residency, and operating needs.
- Dedicated or customer data plane
- Enterprise identity and directory
- Customer DLP, KMS, model, and audit providers
- Custom domains and private connectivity
- Scoped support and deployment controls
Good design-partner fit
Bring the workflow that gets stuck at security review.
We are most useful when a team already sees the agent value but cannot responsibly distribute credentials, move sensitive data, permit a write, or reconstruct the result.
- Multiple AI clients or internal agents need one control boundary
- Source permissions must remain authoritative
- An action needs exact-payload approval or separation of duties
- Data must be inspected, transformed, or kept on an approved model route
- Credentials, content, indexes, or workflows must stay customer-local
- Security needs evidence connecting intent, decision, and execution
Questions
Private-preview pricing FAQ
Why isn’t there a public price yet?
Onterix is in private-preview development. Commercial metrics, quotas, and packaging should follow verified product behavior and design-partner evidence—not precede them.
Can we begin without a sales process?
Axiom-like self-service is part of the target provisioning design, but it is not live today. The current path starts with a focused architecture and workflow session.
What makes a strong design-partner workflow?
A valuable read or write spanning real company systems, meaningful identity or data constraints, a clear approval owner, and a deployment boundary that cannot be hand-waved.
Are security controls enterprise-only add-ons?
No. Baseline isolation, permission checks, approval enforcement, redaction, idempotency, and audit integrity are platform invariants. Advanced providers and deployment operations may be packaged separately.
Can Onterix run in our environment?
Customer-data-plane and fully self-hosted deployments are target modes under active design. The architecture session maps which state and operations must remain local and what evidence is needed before availability.