Every industry has a database
that won’t sit still.
Marketplaces, multiplayer games, fleets of trucks, AI products, banks, hospitals, telcos, power grids — anywhere data changes, Remac moves it. Four deployments in depth, then a dozen more across the board.
A 40-million-SKU catalog that's finally consistent everywhere.
One source of truth, fanned out to the warehouse and the search index in real time — no nightly ETL, no 15-minute re-index cron.
A nightly job loaded the warehouse and a cron re-indexed Elasticsearch every 15 minutes. Buyers searched for items that existed but weren't indexed yet, and merch dashboards trailed a day behind.
One Remac binary on the catalog's replication slot fans every change out to three sinks at once — warehouse, search index, and a Kafka topic for downstream services — in order, with delivery guarantees.
"New products are searchable within seconds of being added, and the warehouse stays current. We deleted the re-index cron and the ETL DAG in the same sprint."
Leaderboards always current, game state consistent in every region.
CDC streams player data to Redis so leaderboards and session state are never stale, and replicates game tables to Postgres and MySQL nodes across regions — no TTL guesswork, no hand-rolled replicas.
Leaderboard data lived in Redis with TTL-based expiry — too short caused miss storms on hot keys, too long served stale standings. Three regions ran a mix of Postgres and MySQL read replicas, all hand-maintained, that regularly drifted, and nobody trusted the data in any of them.
Remac streams every row change to Redis so game state is always current, and replicates selected tables to Postgres and MySQL nodes across regions — one binary, one config, heterogeneous replication out of the box.
"Redis is fed by the WAL now, not by TTLs. Players in every region see the same data, and we stopped babysitting replication scripts."
Fleet telemetry in the lake, and a recovery story that holds up.
One binary running both modes: continuous data-lake ingestion via logical decoding, and physical PITR via the streaming archiver — replacing fragile scripts and nightly backups.
Custom scripts and Airflow DAGs landed vehicle telemetry in S3; nightly backups risked a full day of loss; and services polled each other for the latest vehicle state.
Remac streams CDC to S3 as JSONL and to Kafka for downstream services, while the streaming archiver captures raw WAL for point-in-time recovery — all from one process.
"One binary gives us streaming ingestion to the lake and point-in-time recovery. We retired the backup cron and three ingestion scripts."
The assistant stopped citing products that don't exist.
Real-time CDC kept a RAG assistant's vector index in lockstep with the catalog — embedding drift fell from hours to seconds, and the embedding cache cut API spend.
A nightly cron re-embedded the catalog; between runs the vector DB drifted, so the LLM answered with prices and products that had already changed — and full re-index runs burned the budget.
Remac + the AI Pack: a row change is captured, the embedding transformer calls OpenAI, and the vector lands in Pinecone within seconds. An embedding cache skips unchanged content.
This deployment runs on the AI Pack — the embedding transformer and vector-DB sinks that bolt onto any paid tier.
Explore the AI Pack →…and across every other industry.
If it runs on a database, it’s a fit. The same engine, the same single config — pointed at whatever your sector needs to move.
Stream every transaction to the warehouse; fraud runs on live data.
Every change captured at the log — complete and cannot be bypassed by application code.
Impressions and clicks to Kafka in real time, not hourly batches.
One source of learner state, fanned out to every service in order.
High-volume CDR and session events streamed straight to the lake.
Continuous ingestion of meter reads — no Airflow, no gaps.
Tamper-evident archive of every change to public records.
Rooms, rates, and availability consistent across search and channels.
One change, every downstream service and warehouse, guaranteed.
Feature store updates as soon as a watch or like lands.
Edge and plant-floor changes to the cloud, in order, with retries.
Stores, warehouse, and online stock in lockstep, all day.
Illustrative deployments drawn from common patterns —swap in your own logos, quotes, and numbers. Don’t see your industry? If it has a database, Remac fits.
Deploy once. Forget the pipeline exists.
Your data arrives where it needs to be, in order, with delivery guarantees — and your team never thinks about it again.