Migrating Schemas Across Many Neon Projects Using DrizzleORM

A practical guide to managing multiple databases per tenant with the same schema using DrizzleORM and Neon

In this blog post, we’ll explain how you can use a combination of DrizzleORM, GitHub Actions, the Neon API, and a couple of custom template scripts to manage multiple databases using the same database schema.

You can find all the code referenced in this blog post on this repo:

https://github.com/neondatabase-labs/neon-database-per-tenant-drizzle

But first,

What is Database Per Tenant? A database-per-tenant model is an architectural approach in which each tenant (user, client, or project) has its own dedicated database instance.