Questions, answered
The things buyers ask first — and the honest answers we give them.
How is Bridge licensed?
A subscription license key activates the full platform. Plans scale by monthly rows synced, with a hard 3× monthly spend cap enforced by the engine — your invoice can never surprise you.
How does capture work on my source database?
Our log-based CDC reads redo / binlog / WAL logs directly from your database. Capture runs as a lightweight process with negligible impact on the source.
Can it run inside my VPC or on-prem?
Yes. Bridge is self-hosted by default and runs in your VPC or on-prem. For isolated networks, it can sync via file exchange across security gateways — no inbound connection required.
How many connectors are included?
100+ today across databases, warehouses, lakes, SaaS, files, streams, and IoT — with 300+ on the public roadmap. Enterprise includes custom-connector development.
How long until I see data moving?
Download, activate with your license key, and create your first pipeline in minutes. Most teams complete a safe dual-run migration from legacy ETL within days, not quarters.
What happens if I hit my monthly row cap?
The engine keeps running, but a spend-cap guardrail notifies you. We do not charge surprise overages; you can adjust your tier before the next cycle.
Can we migrate from our existing ETL tool?
Yes. Migration Studio lets you run Bridge beside your current tool, diff every row, and cut over pipeline-by-pipeline. Your downstream dbt models and dashboards stay untouched.
Who keeps the data?
You do. Bridge runs inside your perimeter. Your data never leaves your network unless you explicitly choose a target outside of it.
Still have questions?
Book a 30-minute demo or download a free evaluation license — whichever gets you answers faster.