Softwr

Business Intelligence · head to head

Dundas BI vs TiDB

Dundas BI logo

Dundas BI

Business Intelligence

Flexible business intelligence platform

From
$500/month
Rated
-
TiDB logo

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

  • Only TiDB has a free tier, so it costs nothing to try first.
  • Each has a real cost: Dundas BI the published Embedded BI Package starts from about $4,738.70 USD per month billed annually for 8 core capacity; 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: Dundas BI covers White-labeling, TiDB covers MySQL wire compatibility.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which Dundas BI and TiDB actually diverge.

Attributes where Dundas BI and TiDB differ
AttributeDundas BITiDB
Starting price$500/monthFree
Pricing modelsubscriptionfreemium
Free tierNoYes
PlatformsWeb, Embedded, MobileCloud, AWS, Azure, Google Cloud Platform, Self-managed
CategoryBusiness IntelligenceDatabases
Founded19922015

Identical on both: 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 Dundas BI

  • White-labeling
  • Embedded Analytics
  • Data Preparation
  • Custom Visualizations
  • API
  • SQL Server
  • Oracle
  • PostgreSQL

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.

Dundas BI

  • Embedding dashboards and analytics inside another applicationnot TiDB
  • Self service business intelligence and ad hoc reportingnot TiDB
  • Building custom data visualisations against open BI APIsnot TiDB

TiDB

  • A MySQL workload that has hit the write ceiling of a single primary and would otherwise need an application-level sharding layernot Dundas BI
  • Reporting that must run against current transactional data, where the columnar replica removes the delay and the cost of an ETL pipelinenot Dundas BI
  • Multi-region deployments needing a single logical database with automatic failover rather than manual primary promotionnot Dundas BI
  • Migrating off a sharded MySQL estate where the sharding logic in the application has become the main source of bugs and operational toilnot Dundas BI

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Dundas BI

  • The published Embedded BI Package starts from about $4,738.70 USD per month billed annually for 8 core capacity
  • That figure reflects a limited time 35 percent promotional discount rather than list price
  • Licensing is by CPU core capacity rather than by user, so cost scales with server hardware
  • Dundas is now part of insightsoftware following acquisition
  • The page states that a pricing plan is worked out together with the vendor rather than published as a rate card

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

Dundas BI

$500/month
  • Professional$500/month
    • Full Platform
    • Embedding
    • Support
  • EnterpriseFree
    • Unlimited Users
    • Multi-tenant
    • Premium Support

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 Dundas BI if

  • You need white-labeling.
  • You work on Web, Embedded, Mobile.
  • You also want embedded 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 Dundas BI or TiDB better?
Neither clearly leads. Dundas BI starts at $500/month and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dundas BI or TiDB?
TiDB has a free tier; the other does not. Paid plans start at $500/month for Dundas BI and Free for TiDB.
Does Dundas BI or TiDB run on more platforms?
Dundas BI runs on Web, Embedded, Mobile. TiDB runs on Cloud, AWS, Azure, Google Cloud Platform, Self-managed.
Can I use TiDB for free?
Yes. TiDB has a free tier, so you can try it without paying. Dundas BI starts at $500/month.
What is Dundas BI best used for?
Dundas BI is most often used for embedding dashboards and analytics inside another application, self service business intelligence and ad hoc reporting, building custom data visualisations against open bi apis. Of those, embedding dashboards and analytics inside another application and self service business intelligence and ad hoc reporting are not what TiDB is typically brought in for.
What can Dundas BI do that TiDB cannot?
Dundas BI covers White-labeling, Embedded Analytics, Data Preparation, Custom Visualizations. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.

Answered from the vendors’ own pages

Dundas BI: How much does Dundas BI cost?

Dundas BI does not publish specific pricing. The vendor emphasizes 'smarter licensing models to scale appropriately and achieve ROI rapidly' and offers 'custom plans that fit your needs' rather than standardized tiers. Customers must contact Dundas directly for pricing quotes tailored to their enterprise or embedded analytics use case.

Source
TiDB: 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.

Dundas BI: What licensing options does Dundas BI offer?

Dundas BI describes their approach as flexible licensing designed to scale based on deployment needs. Specific licensing models and per-seat or concurrent-user costs are determined through custom quotes.

Source
TiDB: 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.

TiDB: 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.

TiDB: 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.

TiDB: 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.

Share

Related pages

Other head to heads