Skip to main content
Orbit may explore a combination of subscriptions, usage-based developer access, enterprise services, and future device-related offerings. The final model should be driven by user value, sustainable unit economics, and transparent terms.

​
18.1 Individual plans

A subscription may provide higher usage limits, additional workspace features, or access to supported models. Plan pages should specify limits and exclusions. “Unlimited” should not be used if technical or fair-use limits apply.

​
18.2 Developer usage

API pricing may be based on model usage or other measurable resources. Developers need clear pricing units, billing records, budget controls, and predictable handling of rate limits.

​
18.3 Enterprise offerings

Enterprise needs may include centralized administration, identity integration, access controls, support commitments, contractual data terms, and deployment options. These should be offered only when they are implemented and supported.

​
18.4 Sustainability

Pricing should account for model inference, storage, networking, payment processing, support, security, and development costs. If a service costs more to operate than it earns, growth can make the problem larger rather than solve it.

​
18.5 Honest commercial communication

Do not publish projected customer counts as actual users, planned revenue as realized revenue, or a prototype as a commercially available device. Forecasts should be labeled as forecasts and based on explicit assumptions.