Skip to main content

​
Pricing Overview

BlockDB offers flexible pricing models tailored to your usage patterns and requirements. Choose the right delivery method and pricing structure based on your data access needs, volume, and use case.
Pricing is customized based on your organization’s needs, data volume, and access patterns. Reach out to [email protected] for a personalized quote.

​
Delivery Methods & Pricing

BlockDB offers three primary delivery methods, each with its own pricing model:

API (Usage Limits)

Pay-per-request pricing based on computational complexity. Ideal for on-demand queries, deltas, and filtered data access.

WSS (Real-Time)

Real-time data streaming with subscription-based pricing. Perfect for event-driven architectures and live data feeds.

Archive Delivery

Bulk data exports via SFTP, S3, Azure, Snowflake, etc. Fixed-cost snapshots for comprehensive historical data.

​
Quick Decision Guide

Use API when:
  • Fetching deltas and incremental updates
  • Querying specific time ranges or addresses
  • Performing filtered, targeted queries
  • Ad-hoc exploratory analysis
Use WSS when:
  • Real-time data streaming is required
  • Building event-driven architectures
  • Subscribing to specific events and streams
  • Low-latency interactive applications
Use Archive Delivery when:
  • Getting broad market views (all ERC-20 tokens)
  • Comprehensive historical data (all swaps on all DEXes)
  • Full dataset snapshots and backfills
  • Bulk analytics and data warehousing
Using the API for broad queries (e.g., “get all ERC-20 tokens” or “all swaps last month”) can consume thousands of Compute Units. Archive delivery provides these datasets as complete snapshots at a fixed cost.

​
Hybrid Approach

Most production systems use a combination:
  1. Initial backfill: Archive Delivery to load historical data
  2. Incremental updates: API to fetch deltas outside chain reorganization windows
  3. Real-time streaming: WSS for live data and event-driven architecture (prepare for potential chain reorganization)
The _tracing_id field is consistent across all delivery methods, allowing you to reconcile records and track lineage regardless of delivery method.