Start evolving your database changes with pipelines developers can fully trust

The control surface lives in the database — not in a pile of migration files.

EVOSCA captures what developers actually changed in their schemas, then promotes those changes through a gated approval chain — dev → integration → staging → production — with every step recorded inside the database itself.

See how it works Get notified at release →

Built for teams where the database is the system of record — and auditors ask the database, not a dashboard.

What it will cost

Self-hosted, when the first build ships.

Oracle & PostgreSQL support
Full promotion chain, dev → production
Approval gates & conflict detection
In-database audit log, queryable any time
Fits your existing CI/CD
Your infrastructure, your data

Free for small teams in production — see pricing.

The problem

Three ways schema management breaks

Scripts drift from reality

Real schema work happens in a developer's own schema — not in a hand-authored migration file. When the file and the database disagree, nobody knows which one to trust.

Promotions rely on people, not gates

Someone runs scripts in the right order at the right time. When that person is busy, on leave, or simply human, production feels it. Promotion should be a worker's job.

Collisions are found too late

Two developers change the same package. One silently overwrites the other. By the time anyone notices, production is broken and the trail is cold.

The promotion chain

Five stages. Every step recorded in the database.

Who promoted what, when, under which approval, and against which version — all queryable from inside your own database.

1Dev sandboxEach developer works in their own schema.

2CaptureChanges captured from the schema itself.

3IntegrateMerged; conflicts flagged and logged.

4StagingPromoted under approval, as a versioned edition.

5ProductionCutover moves the current version forward.

All state is stored as tables and procedures inside your database — no external service, no third-party dependency for the record of what happened.

Fits your existing pipeline

The promotion worker is designed to be triggered from your CI/CD tooling. Plug it into the delivery process you already have — no rearchitecting required.

CI/CD pipeline trigger Conflict auto-detection Approval-gated promotion Queryable in-database audit log Oracle & PostgreSQL — one process

How it differs

Migration tools are good. EVOSCA starts somewhere different.

For script-first, forward-only workflows, Flyway and Liquibase are excellent. EVOSCA is built for teams where developers work directly in schemas and the database is the authority.

vs. file-first migration tools

Flyway, Liquibase and similar

These treat an ordered set of scripts as the source of truth and the database as the target. Clean when every change is authored deliberately as a migration. Awkward when developers work directly in schemas — because what they did and what the script says can drift apart silently.

EVOSCA starts from the database: it captures the change from the developer's schema, so the record follows the work rather than the other way round.

vs. change-review platforms

Bytebase and similar

Review-and-approval workflow over migrations is genuinely useful — EVOSCA has approval gates too. The difference is where the control surface lives: promotion state, versions, approvals and the conflict log are tables and procedures inside the managed database.

For teams whose auditors ask the database rather than a dashboard, that distinction matters.

One tool. Both engines. The same commands, the same promotion model and the same approval flow on Oracle and PostgreSQL. Teams running both stop maintaining two different processes.

Recent updates

What has been shipping

Loading…

Get started

Ready to put your database in control?

Not released yet. Leave an address and we will tell you the moment the first build is out — no account, no sales call.

Get notified at release Full product walkthrough →