Enterprise DNA

Instead of Liquibase Secure

Stop renting Liquibase Secure. Own your database release desk.

We build your version around your review rules and release process, bring your Liquibase execution history across, and run the agreed workflow for you. Your authorised operators keep control of production changes.

Liquibase Secure quotes its Starter, Team, Business and Enterprise plans privately. Compare your renewal with the database types, capacity, controls and support your team actually needs.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

The Liquibase Secure bill

Separate the release record from the execution platform

The subscription combines automation, governance and support. Decide which capabilities your team must retain and which review records it can own. Plan details checked against the vendor pricing page on 6 November 2026.

storage

Capacity for database targets

Plans include different target allowances. Review the capacity you use and what expansion would add to your quote.

layers

Coverage for database types

The included number of database types varies by plan. Your current estate determines which execution capabilities a replacement needs.

shield

Change automation and governance

Both appear across the Secure plans. Identify the approval, testing and deployment controls that your team depends on before changing service.

monitoring

Change Intelligence

This capability is available from Team upwards. Your version can bring the release decisions and recorded outcomes together around your own review questions.

group

Role-based access controls

The pricing page includes these in Business and Enterprise. Enterprise DNA scopes identity and reviewer permissions for your version.

support_agent

Support and implementation

Standard and premium support differ by plan. Professional services and the operational help you require need to be included in a fair comparison.

Your release record

A change is ready when its current evidence is ready

Change preparation

Keep the proposal and the recovery plan together

Each change carries an environment, owner, due date and risk. Its current version includes the proposed work, the checks and the recovery notes.

  • check Review the upcoming change window by environment
  • check See overdue changes by owner
  • check Preserve earlier versions when the proposal changes
  • check Read the impact and recovery notes in the change review document

Rehearsal

Test the supplied example before requesting approval

A disposable database runs the proposed change, its checks and its rollback against a supplied example. A failed check stays visible for follow-up.

  • check Record the stage that failed
  • check Require a passing result before approval
  • check Ask which changes have repeated rehearsal failures
  • check Keep production validation with the authorised deployment process

Independent review

Approval belongs to the version that was tested

The reviewer must differ from the recorded owner and author. Another rehearsal or a revision requires a fresh approval before a release pack can be prepared.

  • check Show the decisions waiting for a reviewer
  • check Find revisions with older approvals and no current decision
  • check Preserve rejection reasons and evidence references
  • check Prepare the exact reviewed work for the authorised operator

Outcome and history

Keep a failed release visible until recovery is recorded

Operators record the outcome and its evidence. Imported Liquibase history stays separate from the new review process and retains its original execution types.

  • check Chase failed deployments without a recovery record
  • check Keep marked-ran history distinct from executed work
  • check Compare complete history exports without overwriting differences
  • check Produce a branded evidence pack with decisions and outcomes

Make it yours

Design your own Liquibase Secure replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Liquibase Secure. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Liquibase Secure replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Liquibase Secure data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real command results from synthetic demo records. A passing rehearsal covers the supplied example only, not a production environment.

forum

Database Releases for Claude Code

Connected to your own database

Which changes need work before the release window?

DEMO-001

Title
Add dispatch marker
Environment
Demo reporting
Owner
Morgan
Due date
2026-11-02
State
needs approval

DEMO-003

Title
Review status constraint
Environment
Demo reporting
Owner
Morgan
Due date
2026-11-05
State
needs rehearsal

DEMO-002

Title
Add reporting index
Environment
Demo reporting
Owner
Ari
Due date
2026-11-08
State
needs rehearsal

Ask it anything

Ten questions across your own release records

These queries run today. We have not tested whether a configured Liquibase account can answer the same questions.

chat_bubble Which owners have overdue uncompleted changes?
chat_bubble Which high-risk changes have no passing rehearsal?
chat_bubble Which releases await independent approval?
chat_bubble Which revisions have older approvals but no current approval?
chat_bubble Which environments contain imported marked-ran history?
chat_bubble Which imported changes have no recorded checksum?
chat_bubble Which failed deployments still need a recovery record?
chat_bubble Which environments have changes but no imported vendor history?
chat_bubble Which reviewers approved the most versions?
chat_bubble Which changes have accumulated failed rehearsals?

Switching

How to switch from Liquibase Secure

A history move can be done in a day when exports are ready, while replacing deployment automation is a separately tested project.

  1. 1

    Export your history

    Start with the documented DATABASECHANGELOG columns: changeset identity, author, source location, execution time, execution type and checksum. Use your approved database export tool to save them as CSV. If Liquibase Secure does not give you a clear way to export those records, check with Liquibase Secure about what your account allows before proceeding. Keep the export and linked evidence private.

  2. 2

    Test, then load the records

    Load the CSV into Database Releases for Claude Code against the right environment. Run the import as a test first. The test checks what would be brought across without saving it. Then run the import for real after you are satisfied with the result. Matching records remain unchanged, and conflicting history stops the import for investigation rather than being silently overwritten.

  3. 3

    Review what the import flags

    Check the import results against the original history. Confirm changeset identities and execution types, and investigate conflicts before continuing. The import preserves extra columns in the source row, but it does not bring across change instructions, rollback code, attachments, access controls or vendor policy packs. A record marked MARK_RAN stays marked as such, not proof that a deployment succeeded.

  4. 4

    Run both side by side

    Keep Liquibase Secure and your existing deployment process available while you use the new desk alongside them for a short period. Compare the imported history and review workflow, and validate the replacement against representative staging environments before changing how production work is deployed. The desk prepares reviewed work and records outcomes. It does not execute changes against production.

  5. 5

    Switch off Liquibase Secure

    Once the workflow and required connections have been validated, switch off Liquibase Secure only after you have backed up the new database and any linked evidence, then tested restoration. Keep your existing controlled deployment process unless its replacement has been separately scoped and tested. This avoids treating a successful history import as proof that deployment automation is ready to replace.

construction

Where the real effort goes

The import is usually the straightforward part when exports are ready. The work is deciding which history to carry over, reconciling identities and execution types, and mapping your own fields, change instructions, permissions, policy packs and evidence. Those items need separate migration work. If you have Enterprise DNA run it, Enterprise DNA handles this mapping and migration work as part of the agreed scope.

Not ready for a call?

Get your Liquibase Secure switch plan by email

We will send you the step-by-step plan for moving your business off Liquibase Secure, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Do it yourself, have it customised, or have it run for you

Open source

Do it yourself

Free, open source

  1. 1 Clone the repo, run npm install and npm test
  2. 2 Run npm run demo with Claude Code, Codex, OpenCode or Cursor
  3. 3 Export the documented Liquibase DATABASECHANGELOG history and test its CSV import
  4. 4 Author and rehearse your database changes, then validate your controlled production process separately
Get it on GitHub

Built around your business

We customise it

One setup fee, then a retainer for ongoing work

  • check Your environments, review stages, required evidence and recovery rules
  • check Your Liquibase history imported and reconciled against the originals
  • check A web front end, identity controls and a different technology stack where needed
  • check Your deployment connections built and validated to the agreed scope
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed with controlled access and tested backups
  • check Weekly release reviews and evidence packs prepared
  • check Your agreed review process and business connections maintained
  • check Run through Omni by Enterprise DNA beside the rest of your business
Book a 30-minute release review

Questions

Instead of Liquibase Secure, answered

Does this replace every part of Liquibase Secure? expand_more

The free version is a release review desk with disposable rehearsals and an execution-history import. It does not reproduce the full multi-engine deployment platform. Enterprise DNA can build the execution connections, identity controls and interfaces your team needs into its version. Keep your current deployment process until that scope has been validated against representative staging environments.

What comes across from our Liquibase history? expand_more

The import reads the documented execution-history export, including changeset identity, author, source location, execution time, execution type and checksum. Existing matching records stay unchanged. Conflicting history stops the import for investigation. Change instructions, permissions, policy packs and original evidence need separate migration work.

Does a passing rehearsal prove the production change is safe? expand_more

No. It proves only that the supplied example passed its forward and rollback checks in a disposable database. Production data, performance, permissions and recovery need separate staging tests and human review. The free version prepares reviewed work and records outcomes. Your authorised process executes real changes.

What happens when someone changes the proposal after approval? expand_more

A revision creates a new version and preserves the earlier evidence. The new version needs a fresh rehearsal and independent approval. Repeating a rehearsal also requires a fresh approval. Reviewer names are recorded assertions in the free version. We can build signed-in identity controls into your version.

How do we pay Enterprise DNA? expand_more

Choose the free version, have us customise it, or have us run the agreed workflow through Omni by Enterprise DNA. Our work starts with one setup fee, then a retainer. We agree the migration, review process, required connections and operating scope before building your version.

Bring your renewal and one recent release

Spend 30 minutes with Sam. We will work through the Liquibase service you pay for, the review evidence you need to keep and the deployment capabilities your version must retain.

Book a 30-minute call with Sam Get the free version

Database Releases for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Liquibase Secure?

Get your version built