whichdb

Yaacomo

discontinued

by Q2WEB GmbH · since 2011 · also known as Yaacomo DBMS

German GPU-accelerated relational in-memory DBMS for real-time analytics (c. 2011-2023); defunct.

relationaldatabase engineproprietarylegacy
Website Compare Find similar

discontinued. Website static for years and offline by 2025; dbdb.io marks the project as failed (end year 2023). Consider HeavyDB, Kinetica or Brytlyt.

Overview

Yaacomo was a relational in-memory database from Q2WEB GmbH in Germany that used massively parallel algorithms on graphics processors (with a CPU fallback) for real-time analytics and big-data queries. Its marketing stressed energy efficiency, claiming server-class performance from a palm-sized, 10-watt device, and it won a GreenIT award in 2011; it was also pitched for embedded and machine-to-machine systems and could run on APUs and mobile hardware. The site stayed online, largely unchanged, into 2023 and has returned 404 since; dbdb.io lists the project as failed. HeavyDB, Kinetica and Brytlyt are active GPU databases.

Real-time analyticsAnalytics (OLAP)IoT & telemetry

Strengths & trade-offs

Strengths

  • +GPU-parallel query execution for fast analytics on modest hardware
  • +Low power footprint, suited to embedded deployments

Trade-offs

  • −Defunct vendor; no downloads or support
  • −Little technical documentation was ever published

Great for

  • +History of GPU-accelerated databases
  • +Context for evaluating GPU database vendors

Think twice for

  • −Any new deployment

Capabilities

Native or official first-party support · 2 of 25 tracked

✓Joins
✓In-memory
–Transactions
–Secondary indexes
–Full-text search
–Vector search
–Geospatial
–JSON
–Change data capture
–Triggers
–Stored procedures
–Materialized views
–TTL / expiry
–Pub/Sub
–Columnar storage
–Durable persistence
–Compression
–Encryption at rest
–Role-based access
–Time travel
–Branching
–Online schema changes
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Small · ≤ 100 GB
Horizontal scaling
None
Multi-region
No
Transactions
Limited ACID
Consistency
Strong
Schema
Strict
Architecture
In memory, Single node
Query languages
SQL

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

Alternatives to Yaacomo

Compare all→
HEAVY.AI (HeavyDB)Columnar / OLAP14.3

GPU-native columnar SQL database with visual analytics, fully open-sourced by NVIDIA in 2026.

yaacomo vs heavydb →
KineticaColumnar / OLAP6.4

GPU- and vector-accelerated database for real-time spatial, time-series and vector analytics.

yaacomo vs kinetica →
BrytlytRelational0.0

GPU-accelerated analytics database built on PostgreSQL; technology acquired by Opensignal in 2024.

yaacomo vs brytlyt →
SAP HANARelational39.7

SAP's in-memory columnar HTAP database, the mandatory engine under S/4HANA.

yaacomo vs sap-hana →
RisingWaveRelational17.4

An Apache-licensed, Postgres-compatible streaming database that stores state on S3 and writes Iceberg.

yaacomo vs risingwave →
InMemory.NetColumnar / OLAP0.2

Commercial in-memory columnar SQL engine for .NET that speeds up reporting over hundreds of millions of rows.

yaacomo vs inmemory-net →

Yaacomo FAQ

What is Yaacomo?

Yaacomo is a relational database by Q2WEB GmbH, first released in 2011. Yaacomo was a relational in-memory database from Q2WEB GmbH in Germany that used massively parallel algorithms on graphics processors (with a CPU fallback) for real-time analytics and big-data queries. Its marketing stressed energy efficiency, claiming server-class performance from a palm-sized, 10-watt device, and it won a GreenIT award in 2011; it was also pitched for embedded and machine-to-machine systems and could run on APUs and mobile hardware. The site stayed online, largely unchanged, into 2023 and has returned 404 since; dbdb.io lists the project as failed. HeavyDB, Kinetica and Brytlyt are active GPU databases.

Is Yaacomo open source?

No. Yaacomo is proprietary, closed-source software. License: Commercial.

Does Yaacomo support ACID transactions?

Partly. Yaacomo offers limited ACID guarantees (for example, single-record or single-partition transactions), with strong consistency.

Does Yaacomo scale horizontally?

Yaacomo does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at small scale (≤ 100 GB).

How can I run Yaacomo?

You can self-host it and embed it in your application.

What is Yaacomo best for?

Yaacomo is a strong fit for history of GPU-accelerated databases and context for evaluating GPU database vendors. Think twice for any new deployment.

What are the best alternatives to Yaacomo?

Common alternatives to Yaacomo include HEAVY.AI (HeavyDB), Kinetica, Brytlyt, SAP HANA and RisingWave. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

Is Yaacomo still maintained?

Yaacomo is discontinued. Website static for years and offline by 2025; dbdb.io marks the project as failed (end year 2023). Consider HeavyDB, Kinetica or Brytlyt.

How popular is Yaacomo?

Yaacomo has little measurable public adoption today, so it ranks near the bottom of the WhichDB Score.