Status: Mongock is now in maintenance mode from and reaching end-of-life at the end of 2026.
No new features will be added. critical bug fixes and security updates only.
Existing Mongock versions will continue to work as they do today, but we recommend using Flamingock for new projects and future development.
Your current Mongock versions will keep working as-is.
When you are ready to move to Flamingock, the migration path is intentionally simple. Flamingock was designed so that your existing change units can remain untouched. In most cases, the transition only requires a couple of small configuration changes.
- Your current Mongock versions will keep working as-is.
- You do not need to rewrite your existing changes.
- Migration mainly involves a few configuration updates.
- Upgrade help: How to move from Mongock to Flamingock
We have also created an Agent skill to help guide and automate parts of the migration process.
We are the original authors of Mongock.
Over the past couple of years, we have been building Flamingock: a new platform inspired by what worked well in Mongock, but designed for a broader scope.
Mongock helped teams evolve NoSQL databases safely. But real-world systems rarely evolve in one place only. Database migrations are still important, but modern applications often require coordinated changes across services, infrastructure, events, APIs, configuration, feature flags, and operational rules.
Flamingock was built to support that broader model from day one: auditable, deterministic evolution across your entire system.
It is not a drop-in continuation of Mongock. It is a new platform, built by the same team, carrying forward Mongock’s core migration ideas while expanding them into system-wide change orchestration.
Same creators. Broader scope. Better foundations.
Flamingock supports the core MongoDB and NoSQL migration use cases Mongock was known for, while introducing stronger foundations for modern systems:
- System-wide change orchestration, beyond databases
- Improved failure handling and recovery
- Retry, rollback, and operational safety mechanisms
- Deterministic and auditable execution
- Multi-stage workflows
- Native GraalVM support
- Flexible/low-code templates for defining changes
Learn more in the docs → Flamingock Overview
A Flamingock Cloud offering is also in progress.
The goal is to give teams a central control plane to:
- Monitor executions across environments
- Inspect audit history
- Understand and recover from failures
- Define approval flows for sensitive changes
- Govern who can run, approve, or retry changes
- Track change status across services and systems
- Improve operational visibility for engineering teams