Technology · head to head
Heap vs TiDB

TiDB
Databases
Apache 2.0 distributed SQL database with MySQL wire compatibility and a separate columnar replica for analytical queries.
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Heap no built-in A/B testing or feature flags; requires integration with separate tools for experimentation; TiDB a production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
- They diverge on capability: Heap covers Autocapture, TiDB covers MySQL wire compatibility.
- Prices and features above were last checked on 30 August 2026.
Where they differ
Only the attributes on which Heap and TiDB actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).
What each one covers
Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Heap
- Autocapture
- Retroactive analytics
- Session replay
- Funnel analysis
- User segmentation
- Path analysis
- Data science
- Virtual events
Only in TiDB
- MySQL wire compatibility
- Horizontal write scaling
- Distributed ACID transactions
- TiFlash columnar replica
- Automatic rebalancing
- Raft replication
- Apache 2.0 licence
- Online schema change
What people use each for
The jobs each tool is most often brought in to do.
Heap
- User behavior analysisnot TiDB
- Conversion optimizationnot TiDB
- Product adoptionnot TiDB
- Customer journey mappingnot TiDB
- A/B testing analysisnot TiDB
TiDB
- A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Heap
- Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Heap
- Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Heap
- Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot Heap
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Heap
- No built-in A/B testing or feature flags; requires integration with separate tools for experimentation
- Group analytics and advanced features require a sales conversation, not self-serve
- Cloud-only deployment; no self-hosted option for data security or compliance requirements
- Session replay lacks developer debugging tools compared to PostHog
- Pricing for Growth and Pro plans requires direct sales contact; no transparency on how pricing scales
TiDB
- A production cluster needs several placement driver, storage and SQL nodes before it is fault tolerant, so the minimum viable footprint is far larger than a MySQL server and TiDB is never the economical choice for a small database.
- Every transaction takes a timestamp from the placement driver and crosses the network to storage nodes, so simple point queries are slower than on single-node MySQL and latency-sensitive paths need to be measured, not assumed.
- MySQL compatibility is at the wire and dialect level but not complete; stored procedures, triggers and events are not supported, so an application that pushed logic into the database cannot simply be repointed.
- The columnar replica is an extra full copy of the data on its own nodes, so hybrid analytics roughly doubles storage and adds hardware that must be sized and paid for separately.
- Operating it well requires cluster-specific expertise in TiUP or the Kubernetes operator, region hot spots, and rebalancing behaviour, so the licence is free but the running cost includes an engineer who understands distributed storage.
Pricing, plan by plan
Heap
Free- FreeFree
- Up to 10,000 monthly sessions
- Basic charts
- 6 months data history
- Growth$undefined/custom
- Custom session pricing
- Sense AI assistant
- 12 months data history
- Pro$undefined/custom
- Custom session pricing
- Account analytics
- Engagement matrix
- Premier$undefined/custom
- Custom session pricing
- Data warehouse integration
- Unlimited projects
TiDB
Free- ServerlessFree
- 5GB storage
- 50M request units
- Free forever tier
- Dedicated$250/month
- Dedicated resources
- SLA guarantees
- Enterprise support
Which should you pick?
Choose Heap if
- You need autocapture.
- You want to start without paying.
- You work on Web, iOS, Android.
- You also want retroactive analytics.
Choose TiDB if
- You need mysql wire compatibility.
- You want to start without paying.
- You work on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
- You also want horizontal write scaling.
Questions people ask
- Is Heap or TiDB better?
- Neither clearly leads. Heap starts at Free and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Heap or TiDB?
- Heap starts at Free and TiDB at Free.
- Does Heap or TiDB run on more platforms?
- Heap runs on Web, iOS, Android. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
- Can I use Heap for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Heap best used for?
- Heap is most often used for user behavior analysis, conversion optimization, product adoption, customer journey mapping. Of those, user behavior analysis and conversion optimization are not what TiDB is typically brought in for.
- What can Heap do that TiDB cannot?
- Heap covers Autocapture, Retroactive analytics, Session replay, Funnel analysis. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.
Answered from the vendors’ own pages
Heap: What does Heap's autocapture feature do?
Heap's autocapture is a single code snippet that automatically captures every click, swipe, tap, pageview, and form fill on your website and apps without requiring manual event setup. Once installed, Heap captures the entire digital experience of every user on every platform with no ongoing engineering maintenance needed.
SourceTiDB: Is TiDB a drop-in replacement for MySQL?
At the protocol and dialect level it is close, and most applications connect unchanged. Stored procedures, triggers and events are not supported, and latency characteristics differ, so it needs testing rather than assumption.
Heap: What are Heap's pricing plans and how much do they cost?
Heap offers a Free plan for up to 10,000 monthly sessions. Growth, Pro, and Premier plans use custom session-based pricing that requires contacting sales for a quote. Free includes basic charts and 6 months data history. Growth adds the Sense AI assistant. Pro adds account analytics. Premier adds data warehouse integration and dedicated customer success management.
SourceTiDB: What licence is it under?
Apache 2.0, for both TiDB and the underlying TiKV storage engine. TiKV is a graduated CNCF project, which is a meaningful governance signal in a market where several competitors moved to source-available licences.
Heap: Does Heap include session replay and A/B testing?
Heap includes integrated session replay showing exactly what users did on your site. However, Heap does not include built-in A/B testing or feature flags. Teams requiring these capabilities must use separate tools or integrate with third-party platforms.
SourceTiDB: Do I need TiFlash?
Only for analytical queries. It is an optional columnar replica; without it TiDB is a distributed transactional database. With it you get analytics on live data at the cost of an additional full copy.
Heap: What integrations does Heap support?
Heap supports over 100 integrations connecting to business tools including marketing platforms, CRMs, and data warehouses. This allows insights to reach relevant teams and ensures data flows to other business systems automatically.
SourceTiDB: Is the managed cloud the same software?
TiDB Cloud runs the same engine, with the control plane, scaling and operational tooling provided as a service. The entry tier is metered differently from a dedicated cluster, so the cost model rather than the engine is what changes.
Heap: Does Heap offer self-hosting or is it cloud-only?
Heap is cloud-only and does not offer self-hosted options. Organizations requiring on-premises deployment should consider alternatives like PostHog which supports self-hosting alongside its cloud product.
SourceTiDB: When is TiDB the wrong choice?
When the database is small enough for one server, when latency on single-row lookups is the primary constraint, or when the application depends on MySQL stored procedures and triggers.
Heap: What is Sense and how does it help with analytics?
Sense Chat is Heap's AI assistant that enables users to access analytics without extensive technical knowledge. It allows teams to ask questions about user behavior and get answers directly without lengthy onboarding or technical expertise, making insights more accessible to non-technical stakeholders.
SourceRelated pages
Other head to heads
- Heap vs Mixpanel
- Heap vs PostHog
- Heap vs Amplitude
- Heap vs Pendo
- Heap vs Userpilot
- Heap vs Segment
- Heap vs RescueTime
- Heap vs Lovable
- Heap vs Coda
- Heap vs Istio
- Heap vs Linear
- Heap vs Terraform
- Heap vs Intercom
- Heap vs LaunchDarkly
- Heap vs Monday.com
- Heap vs Cockroach Labs
- Heap vs Vitess
- Heap vs Elasticsearch
- Heap vs SingleStore
- Heap vs BigQuery
- Heap vs DuckDB
- Heap vs Amazon Redshift
- Heap vs ClickHouse
- Heap vs Apache Druid
- Heap vs Couchbase
- Heap vs MariaDB
- Heap vs TimescaleDB
- Heap vs Redpanda
- Heap vs RisingWave
- Heap vs ScyllaDB
- Heap vs Solace PubSub+
- Heap vs SQLite
- Heap vs StarRocks
- TiDB vs Mixpanel
- TiDB vs PostHog
- TiDB vs Amplitude
- TiDB vs Pendo
- TiDB vs Userpilot
- TiDB vs Segment
- TiDB vs RescueTime
- TiDB vs Lovable
- TiDB vs Coda
- TiDB vs Istio
- TiDB vs Linear
- TiDB vs Terraform
- TiDB vs Intercom
- TiDB vs LaunchDarkly
- TiDB vs Monday.com
- TiDB vs Cockroach Labs
- TiDB vs Vitess
- TiDB vs Elasticsearch
- TiDB vs SingleStore
- TiDB vs BigQuery
- TiDB vs DuckDB
- TiDB vs Amazon Redshift
- TiDB vs ClickHouse
- TiDB vs Apache Druid
- TiDB vs Couchbase
- TiDB vs MariaDB
- TiDB vs TimescaleDB
- TiDB vs Redpanda
- TiDB vs RisingWave
- TiDB vs ScyllaDB
- TiDB vs Solace PubSub+
- TiDB vs SQLite
- TiDB vs StarRocks

