Blog

Skip to main content

Your Software Factory Stops at the Database

· 11 min read
Ariel Mashraki
Building Atlas

In August, I wrote that the AI-native SDLC playbook stops at the database. Code is cheap to regenerate. The data in your production database isn't. Software factories make this sharper. An agent takes a ticket, writes the code, runs the tests, and ships it, with no human in the loop. That works for code because code has gates. Tests say whether it's correct, and a bad deploy rolls back.

A migration has no such gate. It can pass every test and still lock your largest table for minutes, because what it costs depends on the data, not the code. Today, the gate is a person who reads the migration and knows which tables are big. A factory doesn't have that person.

In this post, I'll show how we close that gap in Atlas. The team writes down what database code may cost: migrations, queries, functions, procedures, and triggers. Atlas measures every agent's change against those limits twice, first on synthetic data in the agent's sandbox, then on a masked production snapshot before deploy.

Atlas v1.4: Security Scanning, Database Profiler, Agent Skills, Drift Detection, and More

· 37 min read
Ariel Mashraki
Building Atlas

Hey everyone!

We're excited to announce Atlas v1.4. This release brings security scanning to your databases: the new atlas security scan command reports the CVEs affecting your database servers and extensions, from the CLI, CI, or Kubernetes. It also introduces agent skills, a profiler for the Atlas testing framework that works on production-like data, and drift checks between deployments.

Here is what you can find in this release:

  • Security Scanning for Databases - Vulnerability detection for your database servers and extensions with atlas security scan, from CI to Kubernetes, and blast-radius checks for roles.
  • Atlas Agent Skills - Teach Claude Code, Codex, Cursor, and GitHub Copilot to plan, lint, and test schema changes with Atlas.
  • Profiler for the Testing Framework - Measure the locks, rewrites, and space of migrations, queries, and database code, over a masked Amazon RDS snapshot, CSV files, or synthetic rows. In preview.
  • Drift Detection Between Deployments - atlas migrate drift reports every object that diverged from your migrations, for one database or every tenant.
  • Schema Repositories in Your Own Storage - Store schema repositories in your own S3, GCS, or Azure Blob Storage bucket, or an OCI registry, instead of Atlas Cloud.
  • Database Driver Improvements - Snowflake governance policies, SQL Server linked servers and filegroups, PostgreSQL temporal keys, Databricks metric views, Redshift datashares, and more.
  • Atlas Binaries Are Moving to atlasbinaries.com - Starting December 2026, release.ariga.io redirects to atlasbinaries.com. Direct downloads only need the new hostname.

Managing YugabyteDB Schemas with the Atlas Kubernetes Operator

· 16 min read
Noa Rogoszinski
DevRel Engineer
Luan Tran Minh
Software Engineer

Teams don't adopt YugabyteDB by accident. They choose it when a single relational database primary can no longer keep up with their writes from payments, order processing, inventory, etc.

A distributed database carries more than just columns and types: every table and index records how data is split across the cluster, and those choices determine how the database performs at scale. Many teams run YugabyteDB next to their services on Kubernetes, where every other part of the system is versioned in a repository, reviewed in a pull request, and deployed by changing a manifest. A change to how a table is split deserves the same review as a change to its columns, and the same rollout to every cluster.

On YugabyteDB, Atlas models colocation, tablet pre-splitting, and index sharding as part of the schema, so the distribution layout is versioned, diffed, and deployed with the rest of it, instead of living in handwritten DDL that drifts between clusters. The Atlas Kubernetes Operator completes the picture: it applies each version of the migration directory to the database from a Kubernetes resource, the same way the cluster deploys a new image.

This post walks through how an application team can use Atlas and the Operator to declare, review, and evolve their distributed YugabyteDB schema.

PostgreSQL 19: Security Changes and Preparing with Atlas

· 13 min read
Noa Rogoszinski
DevRel Engineer

PostgreSQL 19 is scheduled for general availability on November 19, 2026, one week after PostgreSQL 14 reaches end of life on November 12. From then on, servers on PostgreSQL 14 get no more security fixes. Versions 15 through 18 are still supported, but version 19 will be supported the longest, into late 2031.

This post covers what version 19 changes for security and the schema objects that block an upgrade to it, and how to use the week before GA to prepare with Atlas: scan your servers for their versions and CVEs, keep upgrade blockers out with schema rules, and apply the same schema, roles, and grants to the new instance from code.

ClickHouse CVEs: Find Vulnerable Servers with Atlas

· 10 min read
Noa Rogoszinski
DevRel Engineer

On October 30, 2026, ClickHouse published CVE-2026-116366, an unauthenticated remote code execution vulnerability in ClickHouse Server. Under certain conditions, a user with network access to the server can run arbitrary code on it without logging in. ClickHouse rates it Critical, with a CVSS v4.0 score of 9.5.

ClickHouse Cloud and BYOC deployments are already patched. Self-managed servers are not, and finding every one of them across your environments is the hard part. Atlas can do that for you: atlas security scan now checks the server version of each ClickHouse server against the Atlas Security Graph, and reports every published CVE that affects it, this one included, along with the release that fixes it.

Medallion Architecture on Snowflake with Atlas and dbt

· 7 min read
Nhan Nguyen
Analytics Engineer

In a Snowflake medallion architecture, raw data lands in Bronze, which dbt cleans into Silver and shapes into Gold. dbt owns the two upper layers completely. Every dbt run recreates the tables and views its models define, from code that is versioned, reviewed, and tested.

The bronze layer those models stand on has no such owner. This post is about that layer, and giving Bronze a proper owner without disrupting your dbt project.

Atlas Kubernetes Operator v0.8: Drift Detection, Security Scanning, and Per-Resource Dev Databases

· 7 min read
Noa Rogoszinski
DevRel Engineer

Hey everyone!

We just released Atlas Kubernetes Operator v0.8, which adds drift detection before and between deployments, security scanning for deployed databases, and a setting for controlling dev databases per resource:

  • Pre-Apply Drift Check: policy.drift on an AtlasMigration checks the database for drift before pending migrations are applied, and can block the deployment.
  • Scheduled Drift Checks: AtlasDriftCheck checks the database of an AtlasMigration for drift on an interval and reports the result through conditions and Kubernetes events.
  • Security Scanning: AtlasSecurityScan scans a database for extensions affected by published CVEs, on a schedule or after a schema change, and grades the findings against a policy.
  • Per-Resource Dev Database Prewarming: AtlasSchema and AtlasMigration accept prewarmDevDB, overriding the operator-wide default.

Case Study: How Deriv Automates Schema Migrations with Atlas

· 7 min read
Noa Rogoszinski
DevRel Engineer

"Managing schema as code was the mindset we were looking for, and it was a perfect match with Atlas. It's able to support our database and others, which gives us flexibility going forward."

– Raunak Kathuria, VP of Engineering, Deriv

Company Background​

Deriv is one of the world's largest online brokers, and was recently named Best Fintech Broker (Global) at the 2026 Global Forex Awards. They offer CFDs and other derivatives on forex, stocks and indices, cryptocurrencies, commodities, and Derived Indices to millions of registered users across the globe.

The company runs on PostgreSQL across many schemas and databases, including multi-tenant setups, and relies on advanced features like views, functions, triggers, stored procedures, and row-level security. All of it operates under compliance requirements, including SOC 2, HIPAA, and PCI, that demand full audit trails on every change. Deriv's engineering teams also actively use AI agents in their development work.

DACPAC for PostgreSQL: Where Atlas Fills the Gap

· 14 min read
Noa Rogoszinski
DevRel Engineer

If you've searched for "DACPAC for PostgreSQL," you already know the answer: there isn't one. DACPAC is a Microsoft file format, built into SQL Server Data Tools and deployed with SqlPackage, and it has no equivalent outside the SQL Server ecosystem. What you're actually looking for isn't the file format, it's the workflow: define the schema once, let the tool diff it against a live database, and deploy the result without hand-written migration scripts. Atlas gives you that workflow for PostgreSQL.

The AI-Native SDLC Playbook Stops at the Database

· 16 min read
Ariel Mashraki
Building Atlas

Anthropic recently published The AI-Native SDLC playbook, and it's the most concrete writeup I've seen discussing the effects of cheaper code generation on a delivery process, written by a company where AI authors 80% of merged code. If you run engineering at any scale, I suggest you read it.

It consists of six stages from Plan to Maintain that work in a loop rather than a linear chain of handoffs. Each stage commits an artifact that the next stage reads. The chain of commits is the audit trail. Humans stop reading every line and start judging intent and risk.

GitLab's CEO responded with the line that will likely outlive the playbook itself: "when implementation becomes abundant, trust becomes scarce."

Code is abundant now. Your data is not. An agent can regenerate your code in an afternoon, but it cannot regenerate the production state your company accumulated over years. The playbook's recovery model quietly assumes otherwise, which leads to our claim: the loop does not close at the database.

The database is the one stateful component in your infrastructure. It's where the history lives, and you cannot roll back history by redeploying an older version of it.