Pricing
Understanding Ormi pricing and billing
How Ormi Billing Works
Ormi uses a credit-based system where credit acts as the basic compute unit across all our products. Our pricing is metered and billed based on your actual usage, ensuring you only pay for what you need. Various products and services convert their basic compute units into credits for final billing.
For example, with Ormi Subgraphs, the compute charge is based on the number of entities stored in your subgraphs. For the final invoice, the total number of entities your account utilizes is converted into credits for billing.
Understanding Usage Metrics
We track two primary metrics:
- Active Subgraphs: The number of subgraphs you have running
- Stored Entities: The total amount of data stored across your subgraphs
Entity Storage Billing
Entity storage is calculated hourly across all your subgraphs:
- When you delete a subgraph, its stored entities are no longer billed
- All entities count toward your project’s cumulative usage
Entity Conversion to Credit
For Ormi Subgraphs, entities to credit conversion is the following:
1 credit = 250 entities
Below is a pricing table for unit pricing credit conversion.
| Plan Type | 1 Credit | Price per Credit |
|---|---|---|
| Developer | 250 entities | $0.01 |
| Enterprise | 250 entities | $0.0025 |
Below is a conversion table for bulk entity credit conversions and pricing.
| Plan Type | Price per 1,000 Entities | Price per 100,000 Entities |
|---|---|---|
| Developer | 4 credits ($0.04) | 400 credits ($4.00) |
| Enterprise | 4 credits ($0.01) | 400 credits ($1.00) |
Plans
Community Plan
Best for individuals and experimentation
- Price: Free
- Features:
- Support for 50+ chains
- Load balanced RPC proxy layer
- Enhanced monitoring
- Metrics and analytics dashboards
- Up to 3 custom subgraphs
- 100,000 entities storage included
- Rate limit: 20 requests / 10 seconds
- Email support
Developer Plan
Best for small teams and medium-sized projects
- Price: Pay as you go
- Features:
- Everything in Community plan
- Unlimited custom subgraph indexing
- Unlimited community data querying
- Rate limit: 50 requests / 10 seconds
- Priority email support
- $4.00 per 100,000 entities stored
Enterprise Plan
Best for large-scale operations
- Price: Custom pricing
- Features:
- Everything in Developer plan
- Optional dedicated environment
- 0xdb, dedicated indexing access
- Custom API and database sync
- Custom query limit
- 99.9% uptime, sub-50ms latency
- Custom SLA support
- Premium support via Email, Slack, and Telegram
- $1.00 per 100,000 entities stored
Usage Comparison
| Feature | Community | Developer | Enterprise |
|---|---|---|---|
| Entities stored | 100,000 free | $4.00 per 100,000 | $1.00 per 100,000 |
| Rate limit | 100 / 10s | 50 / 10s | Custom |
| Community subgraphs | Unlimited | Unlimited | Unlimited |
| Custom Subgraphs | 3 | Unlimited | Unlimited |
When does billing occur?
When does billing occur?
Usage is calculated hourly and billed monthly. If you pause a subgraph, it stops indexing new data, but you can still query it. Deleting a subgraph removes it completely. Billing continues for resources used up to that point. If you cancel your subscription on, for example, day 10 of the billing period, charges continue until day 30, when the cancellation takes effect in the next cycle. During this time, the subgraph can still be queried unless deleted manually. Fees accumulate only for resources already used, ensuring fair billing throughout the cycle.
When does a sample usage based bill looks like
When does a sample usage based bill looks like
| Description | Qty | Unit Price | Amount | Notes |
|---|---|---|---|---|
| Feb 3 - Mar 3, 2025 | ||||
| 0xgraph - Enterprise Tier | ||||
| First 400 | 400 | $0.00 | $0.00 | By default first 100k entities are free |
| Next 401 to 40,000 | 39,600 | $0.01 | $396.00 | Up to 10M entities (40k credits), billed at $0.04 per 1k entities |
| 40,001 and above | 200,000 | $0.0025 | $500.00 | Beyond 10M entities (40k credits), billed at $0.01 per 1k entities |
| Subtotal | $896.00 |
What happens if I exceed my plan limits?
What happens if I exceed my plan limits?
Community Plan: Service will be paused until usage returns below limits
Developer Plan: Additional usage is billed at standard rates
Enterprise Plan: Custom limits based on your agreement
How is entity storage calculated?
How is entity storage calculated?
Entity storage is measured hourly across all active subgraphs. For example:
- 3 subgraphs with 10,000 entities each = 30,000 total entities
- Deleting one subgraph reduces your billable entities accordingly
How do I keep my monthly subgraph cost low?
How do I keep my monthly subgraph cost low?
Subgraph costs are based on the number of entities, which correlate with storage and historical data usage. To reduce costs, you can: - Set the start block closer to the tip of the chain to limit historical data. - Specify the indexerHints: prune setting in your subgraph YAML file to prune old data. 👉 Learn more about pruning settings
Why is my subgraph incurring high charge, even though pruning is enabled?
Why is my subgraph incurring high charge, even though pruning is enabled?
- Pruning only applies to subgraphs with multiple entity versions.
- If your subgraph constantly updates entities (e.g., recalculating token balances or prices), pruning will remove older versions to save space. However, if your subgraph operates on immutable data or effectively immutable subgraphs (i.e., where every entity is always at its latest version and never overwritten), pruning does nothing. Examples include subgraphs that track indexed blocks. 👉 Learn more about pruning settings