Datacentric gives your relational database columnar-speed analytics and a single governed endpoint for your AI agents. Take heavy analytics off your primary database and add AI in minutes — no migration, no app rewrite. Your app keeps running exactly as it does today, now enhanced with lightning fast analytics and AI.
Your apps, your dashboards, and now your AI agents all hit the same data. The old answer was a separate system for each — a warehouse, an ETL pipeline, a bespoke AI integration. Datacentric puts ClickHouse behind the relational databases you already run and serves them through one governed interface — no migration and no app changes, so you go from your existing database to live analytics and AI in minutes, not a multi-month project.
Same engine, same features, same performance. The only difference is which relational database sits on the OLTP side.
For teams running PostgreSQL.
For teams running MySQL.
For teams running Apache Ignite.
Posthouse/Myhouse/Ighouse sits between your application and both databases, routing queries to the right engine and keeping data in sync.
Declare tables with ENGINE = columnar (ClickHouse-backed) or ENGINE = relational (local DB only). The hybrid catalog tracks everything.
Your application writes to PostgreSQL, MySQL, or Ignite as usual. Rows destined for ClickHouse are enqueued in a transactional outbox — same ACID guarantees.
A background worker claims outbox rows, batches them, and applies to ClickHouse via HTTP. Retry logic and dead-letter handling ensure delivery.
Run SQL against your relational DB, ClickHouse, or both through a single wire-protocol connection or the HTTP API. Cross-engine joins are handled transparently.
Point Claude, opencode, or any MCP client at the gateway. The agent queries relational and columnar data through one endpoint — governed and metered like every other client.
Outgrow background sync? Stream from Kafka or Solace with parallel per-table pipelines. Prometheus metrics, health checks, and dead-letter recovery are built in.
Step-by-step guides for every feature. Each tutorial works on Posthouse, Myhouse, and Ighouse with copy-pasteable SQL.
Run Postgres + ClickHouse from one SQL surface, then onboard a table you already have (no migration), dashboard it, and put an AI agent on it — in 5 minutes.
MyhouseRun MySQL + ClickHouse from one SQL surface, then onboard a table you already have (no migration), dashboard it, and put an AI agent on it — in 5 minutes.
IghouseRun Ignite 3 + ClickHouse from one SQL surface — create your first dual-engine table and query it across both.
Keep ClickHouse live: enrich Kafka or Solace events through PostgreSQL JOINs into ClickHouse in real time — no ETL to write. Ships with a prebuilt Superset dashboard.
MyhouseKeep ClickHouse live: enrich Kafka or Solace events through MySQL JOINs into ClickHouse in real time — no ETL to write. Ships with a prebuilt Superset dashboard.
IghouseKeep ClickHouse live: enrich Kafka or Solace events through Ignite 3 JOINs into ClickHouse in real time — no ETL to write. Ships with a prebuilt Superset dashboard.
Point Claude — or a free local model via opencode — at one endpoint that spans both engines, with semantic catalog search to find tables by meaning. Any MCP client.
MyhousePoint Claude — or a free local model via opencode — at one endpoint that spans MySQL and ClickHouse, with semantic catalog search to find tables by meaning. Any MCP client.
IghousePoint Claude — or a free local model via opencode — at one endpoint that spans Ignite and ClickHouse, with semantic catalog search to find tables by meaning. Any MCP client.
How the gateway keeps two engines in sync: engine modes, the outbox replication pipeline, backfill/join-export, and direct dual-writes.
MyhouseHow the gateway keeps two engines in sync: engine modes, the outbox replication pipeline, backfill/join-export, and direct dual-writes.
IghouseHow the gateway keeps two engines in sync: engine modes, the outbox replication pipeline, and backfill/join-export with Ignite 3.
PosthouseYour existing tools just work — point psql, psycopg2, or Superset at the gateway, no new client to learn. Plus a streaming API for large exports.
MyhouseYour existing tools just work — point the mysql CLI, mysql-connector-python, PyMySQL, or Superset at the gateway, no new client to learn. Plus a streaming API for exports.
IghouseConnect Ignite thin clients, Python, or Superset to the gateway, with a streaming API for large exports.
All plans include Posthouse, Myhouse, and Ighouse. Start standalone — analytics behind your database with no broker — and move up to streaming Kafka/Solace pipelines when you need to let it fly. Evaluating? The free Dev tier is one click away.
Standalone · production workloads
Streaming · your first pipelines
Streaming · let it fly
Streaming · custom scale and support
Prices shown are fixed monthly rates. Online checkout is coming soon — for now, pick a plan, hit Talk to us, and we’ll have your license keys issued within one working day.
A real reply within one working day from one of the people building it — not a sales-floor bounce.
Email contact@datacentric.online for paid-tier inquiries, on-prem deployments, or just to talk through whether this is the right fit. The free Dev tier doesn't need to go through us — click the button to the right and your license keys land in your inbox in seconds.
No credit card. No call required.