Deployment
Three ways to run Wirekite.
On-prem installer, Docker, or a managed cloud instance — pick what fits your security posture. Same product, same binaries, same speed.
The one thing every enterprise asks first
Your data never leaves your perimeter.
In every deployment mode — on-prem, Docker, or our managed cloud — the extractors, loaders, and change-capture processes run inside the deployment perimeter, touching your source and target databases directly. Customer data never transits Wirekite-controlled infrastructure.
Our managed cloud is single-tenant — every customer gets a dedicated GCP VM provisioned from a baked image. Your VM is yours. The extractors run on it; the rows flow between your source and target through it; we don't intercept.
The product is the data plane. We're not in the middle of it.
Three paths. One binary.
All three modes ship from the same build artifact. The behavior is identical end-to-end; only the install host and supervisor differ.
P1 · You run it
On-prem installer
A self-extracting .run
file you execute on any modern Linux host. Works on a VM, a bare-metal
server, or an air-gapped box. systemd-managed.
- →Ubuntu 20.04+ / RHEL 8+ / Debian 11+
- →Air-gapped install supported
- →Customer-managed upgrade path
- →Optional REST API on :9443
When to pick: full self-managed deployment, on-prem hardware, strict change-control.
P3 · You run it
Docker
One image, all engines, ~700 MB. Three commands to install. Same host requirements as on-prem, just inside a container — and easier to upgrade (pull a new tag, recreate the container).
- →Docker 20.10+ on any Linux distro
- →Air-gapped via
docker load - →Bind-mount your own data + change disks
- →Local-mode extraction (when DB co-located)
When to pick: container-native infrastructure, repeatable upgrades, ECS/k8s/Compose workflows.
P2 · We run it
Managed cloud
Single-tenant GCP VM, provisioned per customer, reachable at a
dedicated <you>.cloud.wirekite.io
URL. Zero install on your side — point a browser, create a root user, start migrating.
- →One dedicated VM per customer
- →We manage the OS, you own the data
- →Browser-trusted TLS at the edge
- →Pay-per-use or fixed term
When to pick: fastest time-to-value, no infrastructure team needed, cloud-native source/target.
Behaviorally identical. By design.
Cloud isn't a stripped-down SaaS port. It's the same product on a VM we operate. The codebase branches on deployment mode in exactly one place — the license module.
Local-mode extraction reads source binlogs or archive logs directly from disk (bypassing the replication API for higher throughput). It only works when Wirekite shares a host with the source database — not possible in our cloud.
License MAC + clock checks are skipped in cloud because the snapshot/clone model makes them architecturally impossible. License expiry and capacity caps are enforced in every mode.
Get started.
Not sure which deployment fits?
30 minutes. We'll walk through your security posture and show you the right install for your team.
Book a Demo