7.2 SaaS Pricing Structure

For details please contact our sales team or email [email protected]

The Orbit Platform SaaS offering uses a credit-based pricing system that provides flexibility and transparency. This section details how credits work and the available subscription models.

Credit-Based System

Our credit system provides a consistent unit of measurement across all platform activities:

1 credit = approximately $0.10 in value

Credits are consumed based on specific operations:

  • Document retrieval and processing

  • LLM-based analysis and content generation (1 credit per LLM call)

  • API operation execution

  • Document monitoring services

Each operation has a defined credit cost based on computational resources required, with transparency into consumption rates for all activities.

Pay-As-You-Go Model

The Pay-As-You-Go model is designed for individual users or small teams with focused use cases:

Individual users purchase monthly credit allocations starting at 1,000 credits. This subscription includes:

  • Personal workspace environment

  • Access to standard document sets and bots

  • Credit consumption dashboard for tracking usage

  • Monthly credit renewal with no rollover

  • Ability to purchase additional credit blocks as needed

Users can select specific bots and document sets relevant to their workflow, with the flexibility to adjust their subscription as requirements evolve.

Enterprise License

The Enterprise License is designed for organizations requiring broader platform access and predictable costs:

Organizations commit to annual contracts with monthly credit allocations starting at £10,000 platform fee. Enterprise licensing includes:

  • Organization-wide user management

  • Pooled credit sharing across all users

  • Administrative controls for user permissions

  • Volume discounts for larger credit commitments

  • Priority support services and implementation assistance

  • Custom training and onboarding

Enterprise licensing provides predictable costs while accommodating fluctuating usage patterns across teams and departments.

Last updated