Security and compliance
Ensure data security and compliance with monitoring and change traceability
Secure database deployments in your CI/CD pipelines
Ship database changes safely with the same speed and governance as application code.
Why Redgate Flyway Enterprise excels in pipeline-as-code database deployments
Flyway Enterprise gives teams everything they need to automate database deployments in a pipeline-as-code approach. Using a single, scriptable CLI and the MCP server for AI-assisted workflows, Flyway Enterprise works seamlessly with CI/CD pipelines for faster, governed and reliable database deployments every time.
Key capabilities
Fully-scriptable workflow for seamless pipeline integration
Every step in Flyway Enterprise has CLI support. Chain commands together for zero-touch automation in any CI/CD pipeline or shell script.
Zero-touch standardization across RDBMS
Experience a standardized approach to database deployments - Flyway’s CLI commands and workflows are supported across the most popular RDBMS.
Catch database issues in development, not in production
A single Flyway CLI command triggers automatic policy-as-code checks across every deployment, enforcing standards consistently before changes reach production.
Robust schema comparison built into the CLI
Compare databases, detect differences, and generate validated migration scripts with Flyway Enterprise’s best-in-class database comparison engine - all from a single binary, with no separate tools required.
Repeatable, version-controlled migrations for auditability
Every auto-generated database migration script is a plain SQL file - reviewable, auditable, and committed to source control like any other code asset.
Auto-generated migration scripts
Generate versioned and undo migration scripts in one command – giving teams a safety net for rollback and branch development.
Why automate database deployments alongside application code?
For many teams, database schema changes are the special case deployments that too often sit outside the automated code deployment workflow and tooling. They’re the bottleneck that slows down delivery of value. 39% of organizations still rely on manual testing and deployment of database changes, introducing variability and risk at a critical stage of the delivery process (State of Database Landscape, 2026). DORA's 2025 State of DevOps research backs this up: the speed vs. stability trade-off is a myth - elite performers achieve both simultaneously.
Flyway Enterprise solves this challenge. With a set of simple CLI commands, Flyway Enterprise consolidates the entire database development workflow - versioning changes, generating migration scripts, validating them in CI/CD environments, and deploying safely to target environments.
“Time's the biggest saving with Flyway Enterprise. Our latest release took less than 6 minutes for 60 databases, that's a huge win. It means we're ready to adapt and scale”
Deploy database changes in the same way as application code
Flyway Enterprise makes it safe and easy for database changes to be handled in the same way as application code, with governance and guardrails built in.
- Seamless CI/CD integration means database changes can be part of the same pipeline as application code - tested, reviewed, and deployed together.
- Chained commands allow schema comparison, modeling, script generation, and deployment (diff, model, generate, and migrate ) to run in sequence with no interactive prompts.
- Verbose logging exposes every underlying command, making it easy to understand, debug, and extend automated workflows.
- Automated script generation replaces time-consuming, manual scripting with precise, deterministic and validated SQL migration scripts.
- MCP server integration lets AI coding assistants trigger Flyway commands directly, blending AI-assisted development with deterministic, validated script generation, so teams can accelerate their workflows while maintaining the same governance and auditability.
How it works
Full control of the deployment pipeline - no new workflows required
Flyway Enterprise is built from the ground up to integrate seamlessly with existing CI/CD pipelines. No new workflows. No friction. Just faster, more stable database releases that are versioned, tested and deployed to the same pace and workflow as your application code.
By running database deployments through the same pipeline and processes as application code, teams benefit from automated testing, policy checks and validation – providing the governance and guardrails to deploy changes with confidence.
Developer
SQL + app code changes
AI assistant
Edits schema model only
Flyway MCP Server
Flyway generates migration script
Deterministic versioned and undo scripts
Commit and PR raised
Human reviews and approves
CI / CD
Validate migrations, code quality checks, unit tests
Check and drift reports
Impact and drift reports generated before release, optional human review
Deploy
Auditable, versioned, deterministic deployment
Every change, human- or AI-authored, flows through the same governed pipeline: deterministic script generation, human review, automated CI checks, and auditable deployment.
“One of the key things is developer confidence and enabling them to take risks because the pipeline is going catch it. With all of the tests in place, they can make big changes and they don’t have to worry about remembering all of the database migrations. It just all flows through, so developers deliver faster and they’re more confident.”
Environment configuration that's safe to version control
Flyway environments keep connection details out of shared project configuration, mirroring how application projects are already structured — shared config in the repository, secrets managed externally. Personal connection details stay local; in CI/CD pipelines, secrets management integrations resolve credentials at runtime from trusted stores.
- User-side configuration (flyway.user.toml) keeps a developer's personal connection details out of the repository and off shared infrastructure - it's excluded from version control and never used by CI/CD pipelines.
- Secrets management integration resolves credentials from HashiCorp Vault, AWS Secrets Manager, Google Cloud Secret Manager, or your pipeline's native secrets at runtime, so CI/CD credentials are never stored in a file at all.
- Named environments make deployment commands portable - flyway migrate -environment=prod works the same way for every team member and every pipeline.
- Supports any number of environments - dev, shadow, QA, staging, pre-prod, production - all configured once, referenced by name.
- Automation templates generate bash, PowerShell, and GitHub yaml files making onboarding and CI runner provisioning consistent and repeatable.
Flyway script types, auto-generated from a single diff for repeatability
Flyway Enterprise’s generate command can produce versioned and undo migration scripts from the same diff artifact, using a deterministic approach that means consistent, repeatable scripts every time. Baseline scripts are generated separately as a one-off full build of the schema. Teams specify what they need using the -generate.types parameter - and Flyway Enterprise handles the rest, including automatic validation before saving.
- Versioned migrations (V) take the database from one known version to the next, applying a discrete, sequenced set of schema changes. These are the backbone of every Flyway deployment.
Flyway Enterprise also supports a schema-model-driven approach: teams can author changes against a version-controlled schema model and let Flyway Enterprise generate the migration scripts, rather than writing migrations by hand. This gives object-level Git history - visibility into which table or procedure changed in which commit - and is often the better fit for teams where AI coding assistants are proposing schema changes, since every AI-generated change still produces a deterministic, reviewable migration script rather than an unreviewed direct edit.
- Undo scripts (U) reverse the changes introduced by a corresponding versioned migration. Ideal for branch development where changes need to be tested, reverted, and re-applied rapidly. In production, the standard philosophy is to fix forward with a corrective migration; undo and snapshot rollback are for lower environments and in emergencies, with backups remaining the system of record for data recovery.
- Baseline migrations (B) provide a full build script for a specific database version, starting from empty. Typically generated once per project rather than alongside every change. Useful for spinning up ephemeral test environments, providing the reference point for shadow database comparisons and change reports, and provisioning new environments from scratch.
- Combined generation — -generate.types=versioned, undo — produces the versioned and undo scripts together for each change, in one step. Baseline scripts are the exception: they're typically generated once, rather than alongside every change - so they're usually run as a separate command.
- Users can also provide their own Repeatable migrations (R), which re-run automatically whenever their checksum changes, making them the right fit for scripts that need to run whenever their contents change.
Built for large teams working with CI/CD pipelines
Flyway Enterprise also supports a schema-model-driven approach: teams can author changes against a version-controlled schema model and let Flyway Enterprise generate the migration scripts, rather than writing migrations by hand. This gives object-level Git history - visibility into which table or procedure changed in which commit - and is often the better fit for teams where AI coding assistants are proposing schema changes, since every AI-generated change still produces a deterministic, reviewable migration script rather than an unreviewed direct edit.
Whether the goal is wiring database migrations into a GitHub Actions pipeline, building a platform engineering toolkit that abstracts deployment complexity from application teams, or producing auditable migration artifacts for regulated release processes. Flyway Enterprise provides the foundation for teams to scale up database deployments to meet software delivery demands.
- CI/CD integration - structure Flyway commands as build, check, and migrate stages in any pipeline runner - GitHub Actions, Azure DevOps Pipelines, GitLab CI, and more - so bad changes are caught before they reach production, not just deployed faster.
- Guardrails for deployment - wrap Flyway commands in existing platform tooling to expose safe, opinionated database deployment workflows to application teams without requiring direct database access and ensure policies are enforced.
- Traceable deployments for compliance – every Flyway-generated script is a plain SQL file with a full audit trail from diff artifact to deployed version, providing the traceability required in regulated environments.
- Multi-environment rollout - apply the same validated migration to QA, staging, pre-prod, and production with a consistent single-command pattern.
- Change reports before production - generate a change report that compares pending migrations against the baseline and already-deployed scripts to highlight exactly what will change, with drill-down detail so teams have a clear understanding of impact before any deployment proceeds.
- Drift detection and resolution - confirm Production hasn't changed unexpectedly outside the migration pipeline, so pre-production deployments accurately reflect what's really there. If drift is found, Flyway auto-generates drift resolution scripts to bring the target environment back into line and keep releases flowing.
Further Learning
Book a consultation
Whether you want more details about Redgate Flyway, a demo, or to know about best practice – get in touch.
Book a consultation