Behind Migrata

I'm a Senior Data Engineer who's been working in recommendation systems, MLOps, and most recently LLMOps. By day I work with Python and Terraform, and by night you can find me coding in F# or Julia.

I'm also an open source developer, and for the past 4 years I've been maintaining Oxygen.jl, the #1 web framework in Julia.

I built Migrata because I was tired of writing and running migration files against large shared databases. Managing thousands of migration files in source control just to track state changes felt like the wrong approach. I wanted something better.

After working with Terraform for years, I knew there were better ways to track state. But unlike the cloud, databases already have a schema language to describe their state: plain SQL.

So rather than inventing some complex DSL, I decided to meet developers where they already are. Migrata lets you define your schema using regular CREATE statements for tables, views, constraints, and everything else.

When you make a change, like adding a column, it compares your local schema to the database and automatically generates the SQL needed to sync them. Just like Terraform, but for databases.