Now onboarding a small number of design-partner integrations — get in touch
Shapewire
Scoped per engagement, not self-serve

A flat fee to build the bridge. A monthly fee to keep it running.

Every legacy system is different, so we don't force it into a one-size menu. The three bands below are drawn from real past engagements — pick the one closest to your situation to see what's typically included and what a reconciled month looks like at that scale.

A 30-minute call, no obligation
Pick what's closest to your situation

Click a tier to see a sample reconciled month at that scale

$ tail -f logs/run.log | jq 'select(.msg=="pipeline run finished")' — starter
 
{ "rowsExtracted": 340, "rowsDelivered": 338, "rowsSkipped": 0, "rowsFailed": 2,
  "connectors": 1, "runsPerDay": 1, "reconciled": true }

A typical night at the Starter scale — one connector, a few hundred rows, one run, fully reconciled.

Every tier, no exceptions

What's included no matter which band you land in

Every run reconciled — in = delivered + skipped + failed, checked automatically
Failed rows quarantined with the exact reason, never dropped
Idempotent delivery — a re-run can never send the same record twice
Read-only client console — see what synced, what didn't, and why
Alerting the moment a reconciliation fails, not after your customer notices
Read-only access to your source only — we never write back to your legacy system

These are the five guarantees behind every engagement — see how they're enforced on every run →

About pricing, specifically

Questions worth asking before you book a call

Why not just publish a fixed price?

Because a nightly CSV drop and a mainframe extract with three custom formats take genuinely different amounts of work — pricing them the same would either overcharge the simple case or underprice the hard one. The bands above are honest ranges from real engagements, not a marketing trick to hide a number.

What exactly does the monthly fee cover?

Hosting the pipeline, running it on schedule (or on demand), monitoring every run's reconciliation, alerting us the moment something fails, and keeping your read-only console available. It's the "keep it running and catch problems first" fee, not a support retainer you have to remember to use.

Is there a minimum contract length?

We ask for a modest initial minimum to cover the setup work honestly — we'll tell you the exact term on the call, and it scales with how much scoping the integration needs. No multi-year lock-in.

What happens if our data volume grows a lot?

The pipeline itself doesn't care — reconciliation and idempotency hold at any volume. If growth pushes you into a higher band (more connectors, more frequent runs), we'll flag it and requote transparently before anything changes, never a surprise invoice.

Can we move between tiers later?

Yes — most engagements start at Starter or Standard and grow into Complex as you connect more of the enterprise customer's systems. You only pay for the added setup work when you actually add a connector.

Get in touch

Tell us what you're connecting to.

Book 30 minutes — tell us what the legacy system is and roughly how much data moves, and we'll come back with a real number.