Softwr

Energy · head to head

EnergyCAP vs TiDB

EnergyCAP logo

EnergyCAP

Energy

Utility bill and energy management software

From
$1000/month
Rated
-
Full reviewWebsite
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
-
Full reviewWebsite

The short version

  • Only TiDB has a free tier, so it costs nothing to try first.
  • Each has a real cost: EnergyCAP priced per meter per year, so cost scales with how many utility connection points exist rather than with users or sites; 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: EnergyCAP covers Utility bill management, TiDB covers MySQL wire compatibility.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which EnergyCAP and TiDB actually diverge.

Attributes where EnergyCAP and TiDB differ
AttributeEnergyCAPTiDB
Starting price$1000/monthFree
Pricing modelsubscriptionfreemium
Free tierNoYes
PlatformsWeb, ApiCloud, AWS, Azure, Google Cloud Platform, Self-managed
CategoryEnergyDatabases
Founded19802015

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 EnergyCAP

  • Utility bill management
  • Energy accounting
  • Cost allocation
  • Sustainability reporting
  • Weather normalization
  • Rate analysis
  • Budgeting
  • Benchmarking

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.

EnergyCAP

  • Tracking utility bills and energy consumption across a property portfolionot TiDB
  • Reporting on energy spend and emissions for an organisationnot TiDB

TiDB

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

Where each one falls short

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

EnergyCAP

  • Priced per meter per year, so cost scales with how many utility connection points exist rather than with users or sites
  • No figure is published at any level, and every package is quoted by sales
  • Emissions, interval data, bill capture and bill pay are separately priced add ons rather than part of the core platform

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

EnergyCAP

$1000/month
  • Essential$1000/month
    • Utility bill management
    • Energy tracking
    • Basic reporting
  • Professional$2500/month
    • Advanced analytics
    • Sustainability reporting
    • Budgeting tools
  • Enterprise$undefined/month
    • Unlimited users
    • Custom integrations
    • API access

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 EnergyCAP if

  • You need utility bill management.
  • You work on Web, Api.
  • You also want energy accounting.
EnergyCAP review

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

Questions people ask

Is EnergyCAP or TiDB better?
Neither clearly leads. EnergyCAP starts at $1000/month and TiDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, EnergyCAP or TiDB?
TiDB has a free tier; the other does not. Paid plans start at $1000/month for EnergyCAP and Free for TiDB.
Does EnergyCAP or TiDB run on more platforms?
EnergyCAP runs on Web, Api. 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. EnergyCAP starts at $1000/month.
What is EnergyCAP best used for?
EnergyCAP is most often used for tracking utility bills and energy consumption across a property portfolio, reporting on energy spend and emissions for an organisation. Of those, tracking utility bills and energy consumption across a property portfolio and reporting on energy spend and emissions for an organisation are not what TiDB is typically brought in for.
What can EnergyCAP do that TiDB cannot?
EnergyCAP covers Utility bill management, Energy accounting, Cost allocation, Sustainability reporting. TiDB covers MySQL wire compatibility, Horizontal write scaling, Distributed ACID transactions, TiFlash columnar replica.

Answered from the vendors’ own pages

EnergyCAP: What is EnergyCAP's pricing model?

EnergyCAP pricing is based per meter per year. The company allows customers to customize their package by adding premium features such as emissions tracking, interval data analytics, finance modules, bill capture, and bill pay services based on business needs.

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.

EnergyCAP: How much does EnergyCAP cost?

EnergyCAP does not publish specific pricing amounts. Customers must contact sales for a customized quote based on their meter count and selected features.

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

More on EnergyCAP

More on TiDB

Keep looking

Other head to heads