Dual-Track Pricing start local quickly, then scale into enterprise operations.
Adoption ladder
graph TD A[Local builder] --> B[Team path] B --> C[Enterprise path] A --> D[Quickstart and provider setup] B --> E[Operations and governance] C --> F[Support and rollout planning]
| Track | Best fit | Includes |
|---|---|---|
| Local path | Solo builders and small teams | Local runtime, provider configuration, and quickstart onboarding |
| Team path | Shared internal AI workflows | Operational consistency, response contracts, and rollout discipline |
| Enterprise path | Governed multi-team environments | Policy-aware routing, implementation planning, and support alignment |
Cost depends on model mix, hardware profile, request volume, and whether you route primarily through local inference, specialist backends, or both.
Budget drivers
Quantization strategy and local hardware determine baseline throughput and operating envelope.
See product layersPrimary and fallback route design influences cost consistency under variable provider health.
Explore routing optionsValidation, startup checks, and rollout governance reduce failure-driven operational overhead.
Read operations guidanceBoth tracks include provider-agnostic routing, shared-state execution, and a migration path from local to enterprise operations.