Ross ROSS = Recommend OSS · open-source software intelligence for agents

schemahero/schemahero

A Kubernetes operator for declarative database schema management (gitops for database schemas) observed · 2026-08-28

github.com/schemahero/schemahero · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

98/100

  • Activity 98
  • Release rhythm 97
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 17
  • age_days: 2685
  • days_rel: 21
  • days_push: 12
  • n_releases_24m: 24

Full methodology

Adoption not part of the score

1148 stars · 98 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

SchemaHero is a database schema migration tool that lets you define table schemas declaratively in YAML and generates the SQL needed to reconcile the live database with that desired state. It works both as a standalone CLI (plan/apply workflow) and as a Kubernetes operator that manages schemas as Kubernetes resources, supporting in-cluster and external databases like RDS and CloudSQL.

Use cases

  • manage database schema migrations declaratively with yaml instead of numbered migration files
  • run gitops for database schemas in kubernetes
  • generate alter table statements from a desired schema definition
  • preview sql changes before applying them to a database
  • manage schemas for postgres, mysql and other databases across dev, staging and prod
  • apply schema changes to cloud databases like rds or cloudsql from a kubernetes operator

When to choose

  • you want declarative, git-reviewed schema changes instead of sequenced migration scripts
  • your team runs on kubernetes and wants schemas as cluster resources
  • you need the same schema definition to work across empty dev databases and existing staging/prod databases
  • you want to see exactly what sql will run before executing it

When to avoid

  • you prefer imperative, hand-written migration files with full control over each step
  • you are not using kubernetes and only need a simple migration runner
  • you need features like data migrations or seed data, which are out of scope

Facets

cli-tool · maturity active

database infrastructure-as-code deployment developer-tools databases cloud-computing infrastructure-as-code developer-tools cli go cloud self-hosted database-schema gitops kubernetes-operator schema-migration declarative-schema database-migrations plan-and-apply devops containers kubernetes docker

4 sources

Member repositories

RepositoryRoleHealth v2
schemahero/schemaheromain98

For agents

markdown · JSON · MCP: product_card(name="schemahero/schemahero")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem