ORACLE & PostgreSQL
EVOSCAEvolve your development process to a new edition.
Schema change management that starts in the database.
The record lives in the database: versions, approvals and history are tables you can query.
EVOSCA captures what developers actually changed in their schemas, then promotes those changes through a gated approval chain — dev → integration → staging → production.
Today: hosted PostgreSQL, as a preview by invitation. Self-hosted downloads open at the first 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.
- PostgreSQL download; Oracle as early access on request
- Full promotion chain, dev → production
- Approval gates & conflict detection
- In-database audit log, queryable any time
- Drift detection in every environment, whenever you check
- Scriptable from CI, with a GitHub Actions recipe
- Your infrastructure, your data
Free in production for up to 6 environments and 2 schemas — 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.
All state is stored as tables and procedures inside your database — no external service, no third-party dependency for the record of what happened.
Runs from your pipeline
Every evosca command can be scripted, with stable exit codes and a dry-run report your CI can show as a summary. A GitHub Actions recipe is included; other CI systems call the same commands.
Drift detection
EVOSCA tells you when production stopped matching what you promoted.
A migration tool knows an environment through the scripts it applied to it. A fix made by hand on production isn't one of them, so it can go unnoticed until a later migration fails against a schema nobody expected.
EVOSCA records what it promoted into every environment, not only developer sandboxes, and whenever you check, compares each environment against it. Changes that arrived outside the chain are listed, and flagged again before the next promotion — so they get acknowledged deliberately, or put back.
evosca deviations --check
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.
Recent updates
What has been shipping
Loading…
Get started
Ready to put your database in control?
Hosted PostgreSQL is open by invitation today. For the self-hosted build, leave an address and we will tell you the moment it is out — no account, no sales call.