Pick a tier, run as many migrations as you need within its limits. No metering on every record. No "message" charges. No surprise bills when you scale.
Level 1 + soft quotas. Shared compute, shared Cosmos DB, fair-use throttling. Suitable for low-volume, non-time-critical migrations.
InfrastructureAzure Functions Consumption plan, shared SQL connection pool, standard queue priority. Concurrent-job and job-size caps enforced at submission.
Best forSolo consultants, small ISVs, or teams trialling Cygenix before committing to a higher tier.
Level 2. Shared infrastructure with hard-enforced per-tenant quotas. Priority queue allocation isolates Pro traffic from Starter-tier load.
InfrastructurePremium-plan Azure Function instance, dedicated Cosmos DB partition with reserved RU/s, isolated SQL connection pool. Durable Functions checkpointing removes the 10-minute execution cap.
Best forSaaS vendors, agencies, and in-house data teams with regular migration workloads and uptime expectations.
Level 2 + dedicated queue. Shared compute pool, but your workload runs on its own Azure Service Bus queue with guaranteed throughput.
InfrastructurePremium Function App with reserved instances, dedicated Cosmos containers, isolated connection pools per tenant. Durable orchestrations with custom retry policies.
Best forLarger ISVs, consultancies running concurrent client migrations, or organisations migrating multi-hundred-million-row legacy estates.
Level 3 or 4. Dedicated Function App, dedicated Cosmos account, dedicated networking — or a fully single-tenant deployment in your own Azure subscription.
InfrastructureProvisioned via Bicep/Terraform per customer. Optional VNet integration, Private Link to your databases, customer-managed keys via Azure Key Vault, and regional residency controls.
Best forRegulated industries, large enterprises, public sector, or any organisation that needs data never to traverse shared infrastructure.
No "talk to sales for a connector list". Here's exactly what's in each plan.
| Feature | Starter | Pro | Business | Enterprise |
|---|---|---|---|---|
| Capacity | ||||
| Concurrent migrations | 1 | 3 | 10 | Unlimited |
| Max rows per job | 1M | 10M | 100M | Unlimited |
| Monthly job submissions | 50 | 500 | 5,000 | Unlimited |
| Queue priority | Standard | Priority | Dedicated queue | Dedicated infra |
| Sources & targets | ||||
| SQL Server (on-prem & cloud) | ✓ | ✓ | ✓ | ✓ |
| Azure SQL Database | ✓ | ✓ | ✓ | ✓ |
| PostgreSQL | — | ✓ | ✓ | ✓ |
| MySQL / MariaDB | — | ✓ | ✓ | ✓ |
| CSV / flat-file imports | ✓ | ✓ | ✓ | ✓ |
| Custom connectors | — | — | ✓ | ✓ |
| MS SQL Server objects (packages, logins, objects) | — | — | ✓ | ✓ |
| Platform features | ||||
| AI column mapping | ✓ | ✓ | ✓ | ✓ |
| Validation engine | ✓ | ✓ | ✓ | ✓ |
| Project planner | ✓ | ✓ | ✓ | ✓ |
| Agentive migration mode | — | ✓ | ✓ | ✓ |
| BI reporting & insights | Basic | Full | Full | Full + custom |
| Version control history | 10 versions | 50 versions | Unlimited | Unlimited |
| Job history retention | 30 days | 90 days | 365 days | Unlimited |
| Notifications | ||||
| Email alerts | ✓ | ✓ | ✓ | ✓ |
| Daily digest | — | ✓ | ✓ | ✓ |
| Slack integration | — | — | ✓ | ✓ |
| Custom webhooks | — | — | ✓ | ✓ |
| Security & compliance | ||||
| UK data residency | ✓ | ✓ | ✓ | ✓ |
| SSO (Microsoft / Google) | ✓ | ✓ | ✓ | ✓ |
| Audit logs | 30 days | 90 days | 365 days | Unlimited |
| Customer-managed keys | — | — | — | ✓ |
| Private networking / VNet | — | — | — | ✓ |
| BYO Azure subscription | — | — | — | ✓ |
| Support | ||||
| Email support | Standard | Priority | SLA-backed | SLA + named CSM |
| Response time SLA | Best effort | 1 business day | 4 hours | 1 hour |
| Onboarding session | — | 30 min | 2 hours | Custom |
| Dedicated success manager | — | — | — | ✓ |
If something's not covered here, get in touch — we'd rather answer your question now than after you've signed up.
A row is a single source-table record processed by a migration job. We count rows once when read from your source database — re-validations, retries, and target-side writes are not double-counted. A 10M-row job means 10M source records, regardless of how complex the transformations are.
Jobs that exceed your tier's row cap are paused and you'll be prompted to either split the job into smaller batches or upgrade. No surprise overage charges — you stay in control of what you spend. If you regularly hit your limits, we'll proactively suggest the next tier.
Pick Starter or Pro, enter your card details to start, and you won't be charged for 14 days. Cancel anytime during the trial and you pay nothing. Your card is only charged on day 15 if you haven't cancelled. We'll email you on day 12 as a reminder.
Yes. Upgrades take effect immediately and we prorate the difference for the current billing period. Downgrades take effect at the end of your current period. You can switch as often as you need — no contracts, no penalty.
Cygenix never stores your production data — we move it from source to target and don't keep copies. What we retain is metadata: job logs, mapping configurations, and validation results. After cancellation, this metadata is held for 30 days (so you can reactivate seamlessly), then permanently deleted. You can also export everything as JSON before you cancel.
No. Cygenix runs in Azure UK South. Source and target connections are made directly from our UK infrastructure. Enterprise customers can additionally deploy into their own Azure subscription for full data sovereignty.
Two ways. First, Cygenix is purpose-built for SQL database migration — not general iPaaS — so the workflow, validation, and AI mapping are tuned specifically for that job. Second, we charge a flat subscription, not per-document/per-message. A migration of 50 million rows costs the same on Pro as a migration of 1 million rows. With Boomi, that difference can be tens of thousands of pounds.
Yes — pay annually and save 20% on Starter, Pro, and Business plans. Toggle "Annual" at the top of the page to see annual pricing. Enterprise contracts are always annual and priced per engagement.
All major credit and debit cards via Stripe. Annual Business and Enterprise contracts can be invoiced with bank transfer (BACS / SEPA / SWIFT) on net-30 terms. VAT is added where applicable; UK VAT-registered customers can supply their VAT number to be charged net.
Yes — that's what Enterprise is for. If your needs sit between two tiers (e.g. you need Business-level concurrency but not the full row cap), get in touch and we'll work something out. We'd rather build a plan that fits than push you onto a tier you don't need.