Repository files navigation

Evolve queues, DBs, APIs, configs, resources and more — governed, auditable, applied at startup in lockstep.

Flamingock bringsChange-as-Code (CaC) to your entire stack.
It appliesversioned, auditable changes to the external systems your application depends on — such as schemas, message brokers, databases, APIs, cloud services, and any other external system your application needs.

Unlike infrastructure-as-code tools, Flamingock runsinside your application (or via theCLI).
It ensures these systems evolvesafely, consistently, and in sync with your code at runtime.

Flamingock focuses onapplication-level changes that your code requires to run safely:

• Database schemas and reference data
• Message queues and schemas
• APIs and configuration values
• Cloud service resources directly tied to your application
• Configuration changes (feature flags, secrets, runtime values)

Flamingock isnot an infrastructure-as-code tool. It does not provision servers, clusters, or networks — those belong in Terraform, Pulumi, or similar. Instead, Flamingockcomplements them by handling the runtime changes your application depends on.

Flamingock is open source at its core, and powers three editions:

• Community Edition: Free and self-managed. Use your own audit store (e.g., MongoDB, DynamoDB). Ideal for basic change tracking.
• Cloud Edition: Fully managed SaaS with a built-in audit store, dashboard, observability, governance, and premium features.
• Self-Hosted Edition: Same advanced capabilities as Cloud, but deployable in your own infrastructure.

For more information about the editions, please feel free to ask us atsupport@flamingock.io.

Automate changes. Version changes. Control changes.

Flamingock is built around the principle ofChange-as-Code (CaC) — the idea thatevery change to your system’s behavior (whether it's a schema update, config toggle, or database change) should be authored, versioned, and reviewed like application code.

This enables truelockstep evolution between your application and the systems it relies on — ensuring everything stays compatible, consistent, and in sync across environments.

No more fragile scripts or untracked console changes. With CaC:

• All changes live in your VCS and follow strict ordering
• Executions are automated and recorded in a centralized audit log
• Rollbacks and multi-environment consistency become first-class citizens

Just like Infrastructure-as-Code reshaped provisioning,Change-as-Code is redefining how systems evolve — and Flamingock brings that principle to life.

• Read thequick start tutorial.

• Change-as-Code (CaC): Treat changes to databases, queues, APIs, or configs as code — versioned, executable, and auditable.
• Unified system evolution: Orchestrate changes across your full stack: event schemas, feature flags, databases, S3, SaaS APIs, and more.
• Programmatic or declarative: Write changes in Java/Kotlin or define them in YAML using official or custom templates.
• Startup-Time synchronization: Apply versioned Changes when your app starts — keeping deployments consistent and safe.
• Audit logging & rollback: Every change is recorded externally; rollback logic is built into each Change.
• Multi-stage workflows: Organize and execute your changes in coordinated, stage-based flows across instances.
• Native GraalVM support: Compatible with native image builds for fast startup and low memory usage.
• Cloud-ready, OSS-Core: Use locally, self-host, or plug into our managed Cloud — all powered by the same open source core.

We welcome contributions from the community!
If you'd like to report a bug, suggest a feature, or open a pull request, check out ourCONTRIBUTING.md for guidelines.

⭐ Star the project to show support

• Report issues in theissue tracker
• Join the conversation inGitHub discussions

Flamingock is open source under theApache License 2.0.