Change Data Capture for Your Business
Change data capture services stream every insert, update and delete from your PostgreSQL database into BigQuery or Snowflake as it happens, without slowing the app. Omeiro builds the pipeline on Debezium and Kafka, so analysts query fresh data instead of yesterday's dump.
What change data capture looks at
The main areas we work through. The exact scope depends on your package and is agreed before we start.
Questions first
- What decisions it supports
- Who uses it
- How often
Data sources
- Sheets, CRM, ads, shop
- Refresh schedule
- Access rights
Charts and KPIs
- Clear definitions
- Simple chart types
- Filters people need
Handover
- Short walkthrough
- Notes on each metric
- Who to ask
What we cover The exact scope depends on your package and your data, and is agreed before work starts.
What you get with change data capture
Change Data Capture with Debezium and Kafka. Real-time zero-impact continuous transactional data replication from PostgreSQL to BigQuery and Snowflake.
Basic Package
CDC replication of up to 10 Postgres tables to BigQuery or Snowflake. 4-day delivery, 2 revisions.
Standard Package
Debezium; Kafka, 40 tables, schema change handling, lag alerts; docs. 8-day delivery, 2 revisions.
Premium Package
Full database, multiple targets, backfill; monitoring; 30 days support. 14-day delivery, 2 revisions.
Clear brief first
We confirm what you need before work starts, so the scope is clear on both sides.
Revisions listed
Each package shows its revision rounds. A round is one list of changes sent together.
Yours once paid
Copyright of the final work passes to you once the order is paid in full.
Your data stays in your own accounts and tools wherever possible, and access is removed when the work is done.
How our change data capture works
Check the source
We review your Postgres version, write-ahead log settings and table list.
Deploy the connectors
Debezium and the transport layer are configured for your tables.
Backfill and verify
Existing rows are loaded, then row counts are compared between source and target.
Monitor lag
Alerts watch replication delay and schema changes so problems surface early.
Change data capture from PostgreSQL: what to check first
Change data capture depends on how your source database is configured. PostgreSQL needs logical replication enabled, a replication user and enough disk to hold the write-ahead log while the connector catches up. Share your Postgres version, hosting provider, table list and largest tables, so the initial snapshot is planned. Tables without primary keys need a decision, since updates and deletes are harder to apply.
A common mistake is ignoring replication slots, which can fill the source disk if a consumer stops. Change data capture here includes lag monitoring and alerts on higher tiers, and a documented recovery path. Deletes are handled deliberately, either as soft flags or removals in the target. The result is a warehouse copy that follows your application closely instead of waiting for nightly dumps.
In short
- Delivery in 4 to 14 days, by package.
- Fixed price, shown before you order.
- Engineering teams whose analytics lag a day behind the live product.
- Data leads wanting real time database replication without touching application code.
- Copyright yours after full payment.
Change Data Capture: common questions
How much does change data capture cost?
Prices are fixed and shown by package on our Change Data Capture pricing page, so you see the full price before you order. You can also ask for a custom quote.
How long does debezium consulting take?
Delivery depends on the package: Basic 4-day delivery; Standard 8-day delivery; Premium 14-day delivery.
What is included in the Basic Package?
The Basic Package includes: CDC replication of up to 10 Postgres tables to BigQuery or Snowflake. Higher packages add more scope, revisions and support.
Can I get a custom postgres CDC implementation package?
Yes. If none of the packages fits, use the custom package form on our pricing page to describe what you need, and our team sends you a fixed price.
Will CDC slow down my production database?
It reads the transaction log rather than running heavy queries, so the added load is typically small.
What happens when I change a table's columns?
Standard and Premium handle schema changes so the target keeps up.
Do I need Kafka experience?
No, we set it up and document it. Your team just needs to run it afterwards.
Is BigQuery or Snowflake the better target?
Both are supported on every tier. Choose whichever your analysts already use.
What is a replication slot in Postgres?
A replication slot makes the database keep change logs until a consumer has read them.
Who owns the final work?
Copyright of the final work passes to you once the order is paid in full. Paid fonts, stock files or licences, if used, are licensed in your name.
Ready to start your change data capture?
Compare the packages and pick the one that fits. Not sure which? Write to us and we will help you choose.