Skip to main content
This section explains how usage is measured, how limits are defined, and how billing is structured within Avigrah. Avigrah is designed as an enterprise AI execution environment. Because every organization has different data complexity, scale, and intelligence needs, usage is not fixed — it is tailored and contractually defined.

​
How Usage is Measured

Usage in Avigrah is based on how your organization stores, processes, and executes AI workloads. The following components contribute to overall usage: Data & Storage
  • Context storage (processed AI-ready data)
  • Data storage (raw and transformed datasets)
  • Lakehouse storage (analytical data layer)
AI Infrastructure
  • Vector storage (for semantic search and retrieval)
  • Vectorization (cost of converting data into embeddings)
  • Cache memory (for faster repeated AI responses)
AI Execution
  • LLM token consumption (input + output processing)
  • RAG (Retrieval-Augmented Generation) calls
  • AI task executions (analysis, workflows, automation runs)
  • Automated executions (scheduled or trigger-based workflows)
Workspace Scale
  • Number of projects
  • Number of teams
  • Number of collaborators (users)

​
Intelligent Units

Avigrah introduces Intelligent Units as the primary way to measure AI usage. An Intelligent Unit represents the combined complexity of data, AI processing, and execution required to generate outcomes. This is influenced by:
  • The type of AI template used (e.g., Customer Intelligence vs Investor Intelligence)
  • Volume and frequency of data
  • Depth of analysis and workflows
  • Number of integrations and real-time signals
Two organizations using the same feature may consume very different Intelligent Units depending on their scale and use case.

​
Usage Limits

All usage limits are defined per organization via contract, not hardcoded plans. Your agreement specifies:
  • Allocated Intelligent Units
  • Storage limits (data, vectors, lakehouse)
  • Execution capacity (tasks, automations)
  • Access scale (projects, teams, users)
Limits are designed to align with your expected workload and business requirements.

​
Overage Policy

If usage exceeds the agreed limits:
  • Additional usage is billed as overages
  • Overage rates are predefined in your contract
  • Billing is transparent and usage is tracked in real-time
This ensures uninterrupted execution while maintaining cost control.

​
Billing Structure

Avigrah operates on a contract-based billing model, not self-serve pricing. Each organization is onboarded with:
  • Custom pricing based on use case and scale
  • Defined usage allocations (Intelligent Units + infrastructure)
  • Clearly documented overage terms

​
Commitment Terms

All plans include a minimum commitment period:
  • 3 months
  • 6 months
  • 12 months
The commitment duration depends on the scope of deployment and agreed commercial terms.

​
Key Principle

Avigrah is not priced as a generic SaaS tool. It is structured as an AI execution infrastructure, where:
  • Usage reflects real business complexity
  • Costs align with actual intelligence delivered
  • Scale is flexible, not restricted by rigid plans
If you need clarity on your organization’s usage or limits, please refer to your agreement or contact your Avigrah representative.