Fifteen years of databases, end to end
Fifteen years of database platforms at AWS, Oracle, Tessell, OpenSCG, and EnterpriseDB — and how they became CortexBolt, the autonomous operations platform.
Introducing CortexBolt
CortexBolt watches your data, decides with AI, and runs the work — across databases, APIs, and services. You approve what matters.
Connects PostgreSQL MySQL MongoDB SQL Server ClickHouse Redis Oracle DuckDB
Streams Kafka PostgreSQL CDC MySQL CDC
01 The loop
01 The problem
Every incident pulls a senior engineer away from planned work. The fix is rarely documented — it stays with the person who found it. So the next outage takes just as long to resolve, and the expertise leaves when they do.
02 The insight
Each fix becomes a visual workflow the whole team can read. A cron schedules it. A webhook fires it. Or CDC catches the change inside the database and starts the flow the instant data moves. AI reads the live state and decides every next step — at machine speed, around the clock.
03 The result
When something breaks, the response is already running. AI triages, decides, and executes — before a human would have read the page. Irreversible steps hold at an approval gate until you sign off. Every action audited. Every run observable. Nobody fights the same fire twice.
02 How it works
Triggers, queries, AI prompts, MCP tools, approval gates — connected on one canvas. Every edge is configurable. Every run is audited.
03 Change streams
Change-data-capture reads PostgreSQL's logical replication stream and MySQL's binlog — and does two things with every insert, update, and delete: replicates it to the stores that need it, and fires whole workflows that act on it. Not just replication. Reflexes.
04 Flow debug
Click a node to set a breakpoint and run. The workflow pauses live — inspect every variable the step received, then continue, step, or abort. Fan-outs pause per element, so you can watch one row at a time.
05 Notifications
A first-class mobile app, purpose-built for your team — on the phone and on the wrist. Alerts, AI insights, and approval requests from your databases, APIs, and streams land there the moment they happen, and on every paging channel you already use: email, Slack, PagerDuty, or any webhook. No dashboards to watch.
9:41
Friday, May 15
06 Access control
An autonomous platform earns trust two ways: by what it refuses to do without permission, and by what it writes down when it acts.
01 Scoped
Users and groups carry six built-in roles — admin, IAM admin, namespace owner, editor, runner, viewer — scoped per namespace. Delegation is explicit: you can only grant a role your own grant lets you pass on.
02 Sealed
Connector credentials are AES-256-GCM encrypted at rest, write-only in the UI, and never returned by the API. Passwords hash with Argon2id, and the bootstrap password must be rotated on first login.
03 Accounted
Runs, approvals, grants, deletes, disables — human or AI, every consequential action writes an audit event with who, what, and when. Authorization is enforced at dispatch, where the work actually happens.
07 From the blog
Fifteen years of database platforms at AWS, Oracle, Tessell, OpenSCG, and EnterpriseDB — and how they became CortexBolt, the autonomous operations platform.
CortexBolt by CortexRidge
Early access is open — one email away.
or write to [email protected]