Technical fit
Docs-first evaluation
Teams that already know what they need can go directly into deployment, connector, and developer docs.
Pricing posture
Pricing stays honest about the current phase.
Universal AI Bridge does not present unsupported checkout or billing automation as current functionality. This page explains the current evaluation lanes and where teams should start instead.
Current entry lanes
These lanes reflect the current product and business maturity without promising Phase 7 billing work ahead of time.
| Dimension | Evaluation | Design partner | Self-hosted evaluation |
|---|---|---|---|
| Current entry path | Product walkthrough and docs-led evaluation through the current public routes. | Partner-led rollout for teams that need tighter connector, governance, or deployment collaboration. | Docs-guided deployment review for teams validating bridge fit inside their own infrastructure. |
| What is available now | The current platform surface, public docs, connector/runtime proof, and secure workspace shell. | Priority collaboration around the current connector-neutral and governance-focused roadmap. | The current deployment contract, runtime model, and audit-oriented control plane without SaaS lock-in. |
| Billing automation | Not active yet. Do not treat this route as self-serve checkout. | Handled manually while monetization work remains out of scope for the current phase. | Not active yet. The current focus is technical evaluation rather than automated billing. |
What this means in practice
The current public pricing posture is designed to help visitors self-qualify without misrepresenting billing maturity.
Commercial fit
Partner-led conversations
Teams with deeper rollout questions can use the enterprise or contact path instead of being forced into a fake self-serve purchase flow.
Roadmap honesty
No billing theater
The site avoids implying active plans, quotas, or checkout mechanics that do not yet exist in the platform.
Next step
Move from public overview to a real evaluation path.
Use the docs when you want the current technical contract, or use the enterprise branch when you want a conversation about deployment fit and rollout posture.