- BFSIBanking, Financial Services & Insurance
- HealthcareComing soon
- ManufacturingComing soon
- Retail & E-CommerceComing soon
Redgate Flyway
Secure the front door. Email is where most attacks arrive — Redgate Flyway is database version control, migrations & deployment — developer/CLI-first, versioned SQL migrations across 30+ databases. It brings DevOps discipline to schema change, in your CI/CD pipeline — the flagship of Redgate’s stack.
Buy through TechBag
Same software. Better outcome — at no extra cost.
Free, vendor-neutral, 30 minutes
How it’s rated
Full scoreboard ↓Quick answer
The Redgate platform family
This page covers Redgate Flyway — the flagship. The rest of the Redgate stack:
Quick facts
30-second orientation- Product
- Redgate Flyway — DB migrations & version control
- Vendor
- Redgate (founded 1999 · Cambridge, UK)
- The category
- Database DevOps — migrations / version control
- What it does
- Version, migrate & deploy schema across 30+ DBs
- The approach
- CLI-first, versioned SQL migrations; huge OSS community
- Editions
- Community (free) · Teams · Enterprise
- Heritage
- Acquired 2019; absorbed ‘Redgate Deploy’
- Scale
- 30+ databases · part of a 200,000+-user stack
- Vs
- Liquibase (big rival), MS SSDT (free), Bytebase, Atlas
- In India via
- TechBag — scoping, honest compare, GST
Understand database DevOps before you buy it
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
What is Redgate Flyway?
Database version control, migrations & deployment across 30+ databases — developer/CLI-first, versioned SQL migrations, huge OSS community. The flagship of Redgate’s DevOps stack.
Manual schema change vs Flyway migrations — the honest table
What consolidation actually replaces, dimension by dimension.
| Dimension | Unprotected / signature email | Redgate Flyway (Redgate) |
|---|---|---|
| Change model | Manual, ad-hoc SQL | Versioned migrations (tracked) |
| Environments | Drift, ‘works here’ | Deterministic, converge |
| Deployment | Hand-run scripts | Automated in CI/CD |
| Audit | ‘Did that run?’ | Schema-history table |
| Databases | A tool per engine | One workflow, 30+ DBs |
| Developer fit | GUI-bound / opaque | CLI-first, plain SQL |
| Drift | Undetected | Detected (commercial) |
| Best fit | (varies) | Developer/CLI-first cross-DB migrations |
Redgate Flyway is database version control, migrations & deployment — developer/CLI-first, versioned SQL across 30+ databases, automated in your CI/CD pipeline (it absorbed the old ‘Redgate Deploy’). Honest: its big rival is Liquibase (more changelog-flexible/enterprise); and if you’re SQL-Server-only, native MS SSDT is free. Redgate is premium vs OSS and now PE-owned. TechBag scopes it & adds GST.
The five pieces of the platform
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Version the Schema
Flyway puts your database SCHEMA under version control — every change is a versioned migration script that lives in your repo alongside application code. Know exactly what the schema is, and how it got there. Version control for the database. The single source of truth.
Write Versioned Migrations
Each change is a numbered migration script (plain SQL, or repeatable). Flyway applies them IN ORDER and records which have run in a schema-history table — so every environment converges deterministically. Ordered, tracked, repeatable. No more ‘did that change run here?’.
Migrate Up Through Environments
Run the same versioned migrations from dev through test to production — via the CLI or your CI/CD tool — with a clear audit of what ran where. Promote change safely, the same way every time. Consistency across environments.
Deploy in CI/CD (Deploy)
Flyway automates DATABASE deployment inside your existing pipeline — the capability that absorbed the old ‘Redgate Deploy’ — so schema change ships alongside app change, no manual scripts. Database releases, automated. The last DevOps gap, closed.
Across 30+ Databases
Flyway works across 30+ databases (SQL Server, PostgreSQL, Oracle, MySQL, MongoDB and more) — one migrations workflow for a polyglot estate. Standardise database change everywhere. One discipline, many engines.
One agent on every machine, one console over all of them — modules attach without a second operational world.
Twelve capabilities. Version, migrate, deploy.
Flyway brings version control & automation to the database — versioned migrations across 30+ engines — the database-DevOps flagship of portfolio, and paired with the human firewall.
Database Version Control
Put the database schema under version control — migrations live in your repo alongside app code, so you always know the state and history. Version control for the database. The single source of truth.
Versioned SQL Migrations
Express each change as a numbered, versioned SQL migration — plain, transparent and easy for developers to reason about — or as repeatable migrations for views/procs. Simple, SQL-native, developer-friendly. No black box.
Schema-History Tracking
Flyway records exactly which migrations have run (and in what order) in a schema-history table — so every environment’s state is knowable and auditable. Know what ran where. A reliable audit trail.
Deterministic, Ordered Apply
Migrations are applied strictly in order, once — so dev, test and production converge to the same state deterministically. No drift from manual, out-of-order changes. Same order, every environment. Deterministic by design.
Callbacks, Baselines & Undo
Hook logic before/after migrations (callbacks), baseline an existing database into Flyway, and (in commercial editions) undo migrations — the controls real projects need. Bring existing databases in. Handle the real world.
Drift Detection & Governance
Commercial editions detect DRIFT (out-of-process changes to a database) and add governance/reporting — so unauthorised changes are caught and the estate stays controlled. Catch the out-of-band change. Keep the estate honest.
CLI-First Automation
Flyway is CLI-first — a single, scriptable command-line tool that drops cleanly into any CI/CD pipeline, script or container. Automate database change anywhere. Scriptable by design.
CI/CD Pipeline Integration
Integrate database deployment into Jenkins, Azure DevOps, GitHub Actions, GitLab and more — so schema change ships alongside application change automatically. Database releases in your pipeline. No manual scripts.
Automated Deployment (ex-Redgate Deploy)
The deployment automation that was ‘Redgate Deploy’ now lives in Flyway Enterprise — pipeline-driven database releases with the controls enterprises need. One flagship, deployment included. The DevOps gap closed.
Cross-Database (30+ Engines)
One migrations workflow across 30+ databases — SQL Server, PostgreSQL, Oracle, MySQL, MongoDB and more — so a polyglot estate gets one consistent database-change discipline. Standardise everywhere. Many engines, one method.
Community, Teams & Enterprise
The free Community edition covers core migrations; Teams and Enterprise add cross-database estate features, drift detection, governance and support — grow into what you need. Start free, scale to enterprise. Right-sized.
The Anchor of Redgate’s DevOps Stack
Flyway is the flagship — pair it with Redgate Monitor (estate health), Test Data Manager (safe test data) and the SQL Toolbelt (developer productivity) for the full database-DevOps discipline (see those pages). Start at Flyway, extend across the stack. One thesis.
Watch Redgate Flyway in action
The overview, getting started, and protecting M365 email.
Flyway — Database Migrations, Introduced
The flagship, explained.
Flyway with PostgreSQL
Cross-database migrations in action.
Flyway with MySQL
One workflow, another engine.
Want a live, India-context walkthrough on your own fleet?
Book a guided demo →The endpoint catches what arrives. Email stops it arriving.
Here’s what genuinely sets Flyway apart (and where free/OSS alternatives are worth weighing).
Bring version control & automation to the database (the last DevOps gap)
The single biggest reason teams choose Flyway is that it closes the last gap in DevOps: the DATABASE. Application code has had version control, CI/CD and automated deployment for years — but database schema change often stayed manual, ad-hoc and risky, the slowest and most dangerous part of a release. The problem it solves: databases are STATEFUL — you can’t just redeploy a fresh copy, you must EVOLVE the existing schema and data safely — so changes were frequently applied by hand, out of order, inconsistently across environments, with no reliable record of what ran where. That’s slow, error-prone, and a real source of outages. What Flyway provides: every change becomes a versioned migration script that lives in your repo alongside app code (VERSION); Flyway applies them deterministically, in order, once, tracking exactly what ran in a schema-history table (MIGRATE); and it automates database deployment inside your existing CI/CD pipeline (DEPLOY). So database change becomes repeatable, auditable and automated — the same discipline you already have for code. Why it matters: it removes the database as the release bottleneck, cuts deployment risk, and gives you a clear audit trail — the highest-value thing a database-change tool can do. The value: Flyway brings version control, deterministic migrations and pipeline automation to the database — closing the last DevOps gap. For faster, safer, repeatable database releases, this matters. TechBag helps teams adopt database DevOps with Flyway. TechBag helps you treat the database like code.
Developer-first & CLI-first — with a huge open-source community
A defining strength of Flyway is that it’s DEVELOPER-first and CLI-first, backed by one of the largest open-source communities in database tooling — which makes it approachable, transparent and easy to automate. The problem it solves: many enterprise database tools are heavyweight, GUI-bound or abstraction-heavy — hard for developers to reason about and awkward to slot into modern, automated pipelines. What Flyway provides: plain, versioned SQL migrations (transparent — developers can read exactly what a change does, no black box), a single scriptable command-line tool that drops cleanly into any CI/CD system, script or container, and a free Community edition plus a massive OSS community (documentation, examples, answers, plugins). Developers adopt it fast because it works the way they already work — in the repo, in the pipeline, in SQL. Why it matters: developer adoption is what makes database DevOps actually STICK — a tool developers like and can automate gets used consistently, which is the whole point. The CLI-first, SQL-native, OSS-backed design means low friction to start (free Community edition), easy automation, and a huge base of shared knowledge. Honest note: this developer/CLI-first style is also the key contrast with Liquibase, which leans more enterprise/changelog-abstraction (see the comparison). The value: Flyway is developer-first and CLI-first with a huge OSS community — transparent versioned-SQL migrations, easy automation, low friction to start. For developer adoption and automation, this matters. TechBag helps teams adopt Flyway. TechBag helps your developers own database change.
Cross-database — one workflow across 30+ engines
A distinctive strength of Flyway is its BREADTH: one migrations workflow across 30+ databases — so a polyglot estate gets one consistent database-change discipline instead of a different tool per engine. The problem it solves: modern organisations rarely run just one database — SQL Server here, PostgreSQL there, Oracle, MySQL, MongoDB across teams. Managing schema change with a different, engine-specific approach for each is fragmented and hard to govern. What Flyway provides: a single, consistent migrations model that works across 30+ databases — the same versioned-migration discipline, the same CLI, the same pipeline integration, whatever the engine. It’s the anchor of Redgate’s cross-DB DevOps strategy (Flyway was acquired in 2019 precisely to take Redgate beyond its SQL Server heritage). Why it matters: standardising database change across a polyglot estate means less tooling sprawl, consistent governance, and portable skills — developers learn one workflow, not five. Honest note: Flyway’s cross-DB breadth is genuine and is where Redgate is broadest (some other Redgate tools remain SQL-Server-strongest) — always validate the specific features you need per engine. The value: Flyway gives you ONE database-change workflow across 30+ engines — consistent discipline for a polyglot estate. For standardising database DevOps across many databases, this matters. TechBag maps Flyway’s coverage to your database mix. TechBag helps you standardise change across every engine.
Start free, grow to enterprise — Community to Enterprise
A practical strength of Flyway is its edition path: a genuinely useful FREE Community edition that teams can start with immediately, growing into Teams and Enterprise editions as needs mature — so adoption is low-risk and scales with you. The problem it solves: teams want to prove a tool works before committing budget — and heavyweight, all-or-nothing licensing is a barrier to adopting database DevOps at all. What Flyway provides: the Community edition (free, open-source) covers the core migrations workflow — enough to run real projects — while commercial editions add what enterprises need: cross-database estate features, drift detection, undo, governance/reporting, and Redgate support. The deployment automation that was ‘Redgate Deploy’ now lives in Flyway Enterprise. So you can start free, prove value, and step up only when you need the enterprise controls. Why it matters: the free-to-enterprise path removes the barrier to STARTING (huge for grassroots developer adoption) while still offering the governance and support larger organisations require — you don’t over-buy on day one. Honest note: Redgate is premium versus free/OSS at the paid tiers; the Community edition and rivals (Liquibase’s OSS core; free MS SSDT for SQL-Server-only) are real alternatives to weigh (see the honest scope). The value: Flyway lets you start free (Community) and grow to Teams/Enterprise as you scale — low-risk adoption, enterprise controls when you need them. For a right-sized path, this matters. TechBag right-sizes the edition for you. TechBag helps you start free and scale sensibly.
The anchor of Redgate’s database-DevOps stack — and local via TechBag
Flyway is the FLAGSHIP and anchor of Redgate’s wider database-DevOps stack — and for Indian teams TechBag adds the local scoping, honest comparison and INR/GST support that make adopting it straightforward. Flyway in the stack: version and migrate with Flyway, then pair it with Redgate Monitor (estate health & performance), Test Data Manager (safe, realistic, masked test data), and the SQL Toolbelt Essentials (developer productivity — SQL Prompt, SQL Compare, SQL Source Control) for the full discipline: version, deploy, monitor, test, comply. One thesis — treat the database like code — across the whole lifecycle. Redgate the company: founded 1999 in Cambridge, UK; 200,000+ users; 92% of the Fortune 100; now PE-majority-owned by Bregal Sagemount (2026), with CEO Jakub Lamik since 2021. Where TechBag adds value: Flyway is quote-priced at the paid tiers (Community is free) — so TechBag adds honest scoping (which editions, which databases), honest comparison (Flyway vs Liquibase vs free native SSDT), CI/CD adoption help, INR/GST invoicing and local support (with no confirmed Redgate India office, the local layer matters). The value: Flyway anchors the Redgate database-DevOps stack — and TechBag adds local scoping, honest comparison, INR/GST and support. TechBag supplies it with local support. TechBag provides Flyway, made local for India.
The honest scope
Redgate Flyway is Redgate’s flagship — an open-source-rooted, CLI-first tool for database version control, migrations and deployment across 30+ databases, bringing app-grade DevOps discipline to schema change. From Redgate (founded 1999, Cambridge UK; now PE-majority-owned by Bregal Sagemount, 2026). The honest framing — strengths, and the real alternatives: Flyway’s strengths are genuine — developer/CLI-first design, plain versioned-SQL migrations, a huge OSS community, cross-database breadth (30+ engines), and a free-to-enterprise edition path. But be clear-eyed about the alternatives: (1) LIQUIBASE is the big rival. Both have open-source cores plus commercial editions; the honest split is style — Flyway is more developer/CLI-first with versioned-SQL migrations and a huge OSS community, while Liquibase is more enterprise/changelog-flexible (SQL or database-agnostic XML/YAML/JSON changelogs), which some large multi-DB enterprises prefer for abstraction and governance. Note Liquibase moved to a Functional Source License (FSL) in 2025, changing its OSS terms. Neither is simply ‘better’ — it’s a fit question. (2) NATIVE MS TOOLING is free. If you’re SQL-Server-ONLY, Microsoft’s SSDT/DACPAC is free (state-based, SQL-Server-only) and ‘good enough’ for some teams. (3) Others: Bytebase, Atlas (Ariga) and DBmaestro address adjacent database-change/governance needs. Other honest notes: Redgate is PREMIUM versus free/OSS at the paid tiers, and it’s a focused specialist — Flyway does database change superbly but isn’t an all-in-one data platform. So the honest positioning: for developer/CLI-first, versioned-SQL migrations with a huge OSS community across 30+ databases, Flyway is excellent and often the best fit; for changelog abstraction and enterprise-governance flexibility, weigh Liquibase; if you’re SQL-Server-only and cost-sensitive, native SSDT is free. TechBag scopes Flyway honestly — comparing vs Liquibase and native tooling — and licenses and supports it locally with GST.
The numbers behind the platform
What your Flyway journey looks like
Scoping (& Flyway vs the alternatives)
Your database platforms (SQL Server only, or cross-DB?), your pipeline, and how you deploy schema today. TechBag scopes it and compares honestly vs Liquibase (changelog-flexible) and free native SSDT (SQL-Server-only).
Version & baseline
Put your schema under version control — baseline existing databases into Flyway and start expressing changes as versioned migrations in your repo. Begin free on the Community edition. The single source of truth.
Migrate & automate in CI/CD
Apply migrations deterministically through dev, test and production via the CLI — and wire Flyway into your CI/CD pipeline so database releases ship alongside app releases. Repeatable, automated, audited.
Scale & extend the stack
Step up to Teams/Enterprise for drift detection, governance and support as you scale — and pair Flyway with Redgate Monitor and Test Data Manager for the full lifecycle. TechBag supports you locally (GST).
Trusted across regulated industries in 100+ countries
The review scoreboard
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
Quick poll — what’s driving your evaluation?
Talk to an advisor“Flyway made our database deployments as repeatable as our code deployments — versioned migrations in the repo, applied deterministically through every environment. The database stopped being the risky part of a release.”
“CLI-first was the win — it dropped straight into our CI/CD pipeline with a single command. Our developers picked it up in a day because it’s just plain versioned SQL, no black box.”
“One migrations workflow across SQL Server AND PostgreSQL — we finally have one discipline for a polyglot estate instead of a different approach per engine.”
“We started on the free Community edition to prove it, then moved to Enterprise for drift detection and support as we scaled. The free-to-enterprise path made adoption low-risk.”
“Honest: we evaluated Flyway against Liquibase. We went Flyway for the developer/CLI-first style and the huge OSS community; a peer picked Liquibase for changelog abstraction. TechBag laid out the trade-off straight.”
“For our SQL-Server-only team, free SSDT was tempting — but Flyway’s cross-DB path and CI/CD fit won as we added PostgreSQL. TechBag was candid that native was an option first.”
“Flyway is the anchor — we pair it with Redgate Monitor and Test Data Manager for the full lifecycle. One thesis: treat the database like code.”
“Redgate is premium versus OSS, and it’s now PE-owned — TechBag surfaced both, scoped the editions, compared vs Liquibase honestly, and added INR/GST. A clear-eyed buy.”
Where everyone sits — the grids
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the database-migrations market — tap any vendor to see why it sits where it does.
TechBag Email-Security Grid
Execution strength vs product vision — the classic market map, minus the paywall.
Developer/CLI-first cross-DB migrations. This page's product.
Detection × Portfolio Integration
The grid nobody publishes — how strong the email detection is vs how integrated with the wider security portfolio.
Migrations depth + OSS community.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Redgate Flyway vs the database-migrations field
Liquibase, Bytebase, Atlas, native MS SSDT and DBmaestro — honest lanes; the edge is developer/CLI-first versioned-SQL migrations + a huge OSS community across 30+ databases. Want changelog abstraction? Liquibase. SQL-Server-only & cost-sensitive? Free SSDT. We say so.
| Dimension | Redgate Flyway | Liquibase | Bytebase | Atlas (Ariga) | MS SSDT/DACPAC | DBmaestro |
|---|---|---|---|---|---|---|
| Position | Developer/CLI-first migrations (30+ DBs) | Enterprise/changelog-flexible migrations | DB CI/CD & change collaboration UI | Declarative schema-as-code (OSS) | Free, state-based, SQL-Server-only | DB release automation + governance |
| Open source + commercial | OSS Community + Teams/Enterprise | OSS core + commercial (FSL, 2025) | OSS + paid tiers | OSS + paid | Free (native MS) | Commercial |
| Cross-database breadth | 30+ databases | Very broad (many DBs) | Several major DBs | Growing | SQL Server only | Several DBs |
| Migration style | Versioned SQL (transparent) | Changelogs (SQL or XML/YAML/JSON) | Versioned + UI review | Declarative (desired-state) | State-based (DACPAC) | Pipeline-driven |
| CLI-first / CI-CD automation | CLI-first, drops into any pipeline | CLI + integrations | CLI + UI | CLI-first (dev-tool feel) | MSBuild/Azure DevOps | Pipeline + approvals |
| Best fit | Developer/CLI-first cross-DB migrations + OSS community | Changelog abstraction & enterprise governance | DB change with review UI & collaboration | Declarative schema-as-code (OSS-first) | SQL-Server-only & cost-sensitive (free) | Heavier release governance/approvals |
Which email-security approach fits you?
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
Choose Redgate Flyway if…
- ✓You want developer/CLI-first, versioned-SQL migrations that drop into any CI/CD pipeline
- ✓You want ONE database-change workflow across 30+ databases (polyglot estate)
- ✓You value a huge OSS community and a free-to-enterprise edition path
- ✓You want it as the anchor of a database-DevOps stack (Monitor, Test Data Manager) — with TechBag adding scoping & GST
Liquibase if…
- ✓You want changelog abstraction (SQL or XML/YAML/JSON) and enterprise-governance flexibility across many databases (note the 2025 FSL move)
MS SSDT / DACPAC if…
- ✓You’re SQL-Server-ONLY and cost-sensitive — native state-based tooling is free and ‘good enough’ for some
Bytebase / Atlas if…
- ✓You want a modern review-UI/collaboration workflow (Bytebase) or declarative schema-as-code (Atlas)
DBmaestro if…
- ✓You want heavier database release governance, approvals and enterprise change control
What do email threats cost you?
Drag the sliders (databases/environments; deployments per month; hour cost as loaded rate). Estimates contrast manual/ad-hoc schema change (drift, hand-run scripts, failed/rolled-back deployments, no audit) vs Flyway (versioned migrations, deterministic apply, CI/CD automation) — the wins are deployment time saved, failed-deployment cost avoided, and audit/compliance effort saved. Illustrative — TechBag scopes your estate.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models actual device counts and modules.
Three ways to consume it
Redgate Flyway has a FREE Community edition (open source); Teams and Enterprise editions are quote-priced (per-user, subscription — not perpetual), adding cross-database estate features, drift detection, governance and support. Treat any third-party figures as indicative. Redgate bills in its list currency; TechBag right-sizes the editions and handles INR/GST — quote current figures.
Flyway (Community free / paid by quote)
Best for database DevOps + CI/CD
- Versioned SQL migrations & database version control
- CLI-first — drops into any CI/CD pipeline
- One workflow across 30+ databases (polyglot)
+ Platform add-ons
Best for a broader rollout
- Scoped to your estate
- Add-on modules as needed
- Phased, right-sized deployment
+ editions & local support
Best value with TechBag
- Edition right-sizing (Community → Teams → Enterprise) + honest Liquibase/SSDT comparison
- Premium vs free/OSS; now PE-owned (Bregal Sagemount)
- TechBag adds INR/GST invoicing, CI/CD adoption help & local support
Buy it for less — TechBag pricing beats list
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Get an India-ready quote
Tell us your device counts and current tools — we’ll model it against what you spend today.
The 8 questions to ask every vendor
Take this into your next vendor call — including ours.
Deploying schema by hand, out of order, inconsistently? Flyway makes it versioned, deterministic and automated.
Want database releases in your pipeline? Flyway is CLI-first — drops into Jenkins, Azure DevOps, GitHub Actions.
Running more than one database engine? Flyway gives ONE migrations workflow across 30+ databases.
Want a tool developers actually use? Flyway is developer/CLI-first with plain versioned SQL and a huge OSS community.
Want to prove it first? Start on the free Community edition, grow to Teams/Enterprise for drift/governance/support.
Weighing Liquibase? It’s more changelog-flexible/enterprise; Flyway is more developer/CLI-first. TechBag lays out the fit.
SQL-Server-only and cost-sensitive? Free MS SSDT may suffice — TechBag is candid about when native is enough.
Paid editions are quote-priced (Community is free) — TechBag right-sizes editions and adds INR/GST invoicing.
Questions buyers ask
Ready to bring DevOps to your database?
Scope Redgate Flyway (developer/CLI-first database version control, migrations and deployment across 30+ databases — in your CI/CD pipeline) — and let a TechBag advisor right-size the editions, compare honestly vs Liquibase and free native SSDT, and add INR/GST and local support.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.