vs

GT.M vs YottaDB

GT.M: FIS's high-throughput M (MUMPS) database and compiler, behind major core-banking systems. YottaDB: Open-source MUMPS/M hierarchical key-value database forked from GT.M, with SQL via Octo.

key differences

  • YottaDB can run embedded in your application process.

choose gt-m for

  • +FIS Profile and other M-based core-banking systems
  • +VistA and M-based health record systems

best at · OLTP

choose yottadb for

  • +VistA and other M-based EHR systems
  • +Core-banking platforms built on M
  • +Migrating GT.M or Caché applications to open source

best at · OLTP

overview
Primary model
Hierarchical
Hierarchical
Also supports
Key-Value
Key-Value
Type
Database engine
Database engine
Status
Active
Active
Developer
FIS (Fidelity National Information Services)
YottaDB LLC
First release
1986
2017
Latest version
V7.2-001 (Aug 2026)
r2.06 (Apr 27, 2026)
License
Open source (copyleft)GNU AGPL v3.0 (Linux x86_64); commercial on other platforms
Open source (copyleft)GNU AGPL v3.0
Free tier
✓
✓
popularity
WhichDB Score
8.1
7.9
Rank
#331
#333
GitHub stars
–
93
Stack Overflow questions
90
7
scale & guarantees
Comfortable data size
Medium (≤ 10 TB)
Medium (≤ 10 TB)
Horizontal scaling
Manual
Manual
Multi-region
Read replicas
Read replicas
ACID
Full
Full
Consistency
Strong
Strong
Schema
Schemaless
Schemaless
Architecture
Single node, Primary replica
Single node, Primary replica, Embedded
deployment
Self-hosted
✓
✓
Vendor-managed cloud
—
—
Serverless
—
—
Embedded
—
✓
Edge
—
—
Clouds
–
–
capabilities
Transactions
✓
✓
Joins
—
—
Secondary indexes
—
—
Full-text search
—
—
Vector search
—
—
Geospatial
—
—
JSON
—
—
Change data capture
—
—
Triggers
✓
✓
Stored procedures
—
—
Materialized views
—
—
TTL / expiry
—
—
Pub/Sub
—
—
Columnar storage
—
—
In-memory
—
—
Durable persistence
✓
✓
Compression
—
—
Encryption at rest
✓
✓
Role-based access
—
—
Time travel
—
—
Branching
—
—
Online schema changes
—
—
Streaming ingest
—
—
Offline sync
—
—
Runs in WebAssembly
—
—
interfaces
Query languages
M (MUMPS)
M (MUMPS), SQL (Octo)
Client languages
M, C
M, C, Go, Rust, Python, Node.js, Perl, Lua
Best for
OLTP
OLTP

GT.M vs YottaDB: FAQ

What is the difference between GT.M and YottaDB?

GT.M: FIS's high-throughput M (MUMPS) database and compiler, behind major core-banking systems. YottaDB: Open-source MUMPS/M hierarchical key-value database forked from GT.M, with SQL via Octo. YottaDB can run embedded in your application process.

When should I choose GT.M over YottaDB?

Choose GT.M for FIS Profile and other M-based core-banking systems; and VistA and M-based health record systems. Choose YottaDB for VistA and other M-based EHR systems; core-banking platforms built on M; and migrating GT.M or Caché applications to open source.

Is GT.M or YottaDB more popular?

GT.M ranks #331 on the WhichDB Score (8.1/100) and YottaDB ranks #333 (7.9/100). Popularity is not fit: check the requirements that matter for your project.

Are GT.M and YottaDB open source?

Yes. GT.M is open source. License: GNU AGPL v3.0 (Linux x86_64); commercial on other platforms. Yes. YottaDB is open source. License: GNU AGPL v3.0.