Using Autopilot to Sync New Tables

Artie moves your operational database data into warehouses and lakes - in real time, with minimal overhead. And today, we’re making it even easier to sync new tables, without manual intervention.

‍

The Pain of Manually Managing New Tables

If you’re running a production database, you know the story: new tables show up all the time. Half the time, nobody even tells the data team it’s happening.

So you either:

• Beg engineers to ping you when they spin up a new table. (Good luck with that.)
• Or spend hours manually combing through your database, trying to spot changes before something breaks.

‍

Neither one scales.

That’s why we’re introducing a quality of life upgrade: Autopilot for New Tables.

‍

Introducing Autopilot for New Tables

Autopilot does what you’d hope: automatically detects new tables in your source databases - alerts you, and automatically syncs them over to your destination.

Spend less time managing pipelines and more time building.

‍

‍

If you’re already using Artie, you can turn on Autopilot today:

Edit your deployment → Destination settings → Advanced settings → turn on “Auto-replicate new tables”.

‍

‍

When Autopilot Is a No-Brainer (And When It’s Not)

Autopilot is a huge quality of life upgrade, but it's important to know when to use it.

Turn it on if:

• You want every new table replicated automatically.
• You don’t need manual audits for PII/PHI before replication.
• You want to stop waking up to missing data surprises.

‍

Maybe hold off if:

• You have strict governance processes that require approval per table.
• You’re super sensitive to storage or compute costs, and want to cherry-pick what gets replicated.