Artillery
Half the release notes are a Playwright version bump; the other half is cloud-runner damage control.
Comparison · DevOps
SchemaHero vs Postgres Operator
A side-by-side editorial comparison of SchemaHero and Postgres Operator — release velocity, themes, recent moves, and the top alternatives to consider.
SchemaHero vs Postgres Operator: at a glance
What is SchemaHero?
SchemaHero's beta train is CRD correctness work, one commit per tag.
The v0.26.0 beta line ships as a series of single-commit tags: Doppler added as a secrets source, the Slack app removed, RBAC role rules updated, and a fix enabling the status subresource on the Table custom resource. The status fix was the substantial one, correcting all four tracked CRD artifacts and finding the same omission on Function. Each tag carries one change, so the version count reflects commit granularity rather than release scope.
What is Postgres Operator?
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
The Postgres Operator has crossed from a long-running 1.x line into a v2 major release requiring an explicit migration. v2 brings Postgres 18 support, NodePort services, TopologySpreadConstraints, an ARM-compatible pooler image, IRSA for EKS, and globally configurable maintenance windows. The initial v2.0.0 tag shipped with an OperatorConfiguration CRD type mismatch that broke GitOps pipelines and was superseded by v2.0.1 the same day.
SchemaHero vs Postgres Operator: editorial side-by-side
SchemaHero
5.0DEVOPS
SchemaHero's beta train is CRD correctness work, one commit per tag.
◆ Current state
The v0.26.0 beta line ships as a series of single-commit tags: Doppler added as a secrets source, the Slack app removed, RBAC role rules updated, and a fix enabling the status subresource on the Table custom resource. The status fix was the substantial one, correcting all four tracked CRD artifacts and finding the same omission on Function. Each tag carries one change, so the version count reflects commit granularity rather than release scope.
◆ Where it's heading
This is operator hygiene rather than feature work: making the Kubernetes custom resources behave the way controllers expect, and widening where database credentials can come from. The addition of a regression test that verifies every served Table CRD version enables /status suggests the project is closing a class of bug rather than a single instance. Nothing in this window changes what SchemaHero does to a database schema.
◆ Prediction
The status subresource audit already spread from Table to Function and confirmed DatabaseExtension; finishing that sweep across the remaining custom resources is the work these entries point to.
Postgres Operator
6.3DEVOPS
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
◆ Current state
The Postgres Operator has crossed from a long-running 1.x line into a v2 major release requiring an explicit migration. v2 brings Postgres 18 support, NodePort services, TopologySpreadConstraints, an ARM-compatible pooler image, IRSA for EKS, and globally configurable maintenance windows. The initial v2.0.0 tag shipped with an OperatorConfiguration CRD type mismatch that broke GitOps pipelines and was superseded by v2.0.1 the same day.
◆ Where it's heading
The 1.x releases — shipped under animal codenames rather than versions — were incrementally widening operator control over child resources: owner references, per-cluster maintenance windows, inherited annotations, PDBs for bootstrap protection. v2 consolidates that into a breaking release and picks up the platform work the 1.x line kept deferring: ARM images, EKS-native identity, spread constraints. The recurring pattern of releases shipping incomplete — missing UI and logical-backup images in one, a pipeline-breaking CRD in another — suggests release engineering is the weak point rather than the code itself.
◆ Prediction
Expect a 2.0.x patch stream shaking out migration problems from the v2 CRD changes before any new features land. Postgres 18 support arriving here also implies Spilo image updates will keep pacing upstream Postgres releases.
Alternatives to SchemaHero and Postgres Operator
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either SchemaHero or Postgres Operator.
GitUI
A terminal Git client that ships release candidates roughly once a year.
Vitest
A major version being built in the open, one breaking change at a time.
fish shell
Four minor versions in five months, and the shell's remaining work is almost all interaction detail.
Alacritty
Alacritty ships twice a year and spends it on config syntax, Wayland and IME.
Mamba
Mamba is adding the reproducibility controls conda users have been asking of the solver.
See all SchemaHero alternatives → · See all Postgres Operator alternatives →
Recent activity from SchemaHero and Postgres Operator
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9d agoPostgres Operatorv2 lands: Postgres 18, EKS IRSA, ARM pooler, spread constraints ⚡
- 10d agoPostgres Operatorv2.0.0 pulled over a GitOps-breaking CRD defect
- 25d agoSchemaHero0.26.0-beta.4: RBAC role rules updated
- 26d agoSchemaHero0.26.0-beta.3: status subresource fixed on Table and Function CRDs
- 27d agoSchemaHero0.26.0-beta.2: Slack app removed
- 27d agoSchemaHero0.26.0-beta.1: Doppler secrets support
- 7mo agoPostgres Operator1.15.1 bugfix release repairs the ghcr build pipeline
- 7mo agoPostgres Operator1.15.0 adds a bootstrap-phase PDB — but ships without images
- 1y agoPostgres OperatorPostgres 17 support and fleet-scale API rate controls
- 1y agoPostgres OperatorOwner references on child resources and per-cluster maintenance windows
Frequently asked questions
What is the difference between SchemaHero and Postgres Operator?
They serve adjacent needs but don't currently overlap on shipped themes. Postgres Operator is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is SchemaHero better than Postgres Operator?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Postgres Operator is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to SchemaHero?
Top SchemaHero alternatives in DevOps are ranked by recent ship velocity. Browse the "SchemaHero alternatives" section above for the current picks, or visit /alternatives/schemahero for the full list with editorial commentary on each.
What are the best alternatives to Postgres Operator?
Top Postgres Operator alternatives in DevOps are ranked by recent ship velocity. Browse the "Postgres Operator alternatives" section above for the current picks, or visit /alternatives/postgres-operator for the full list with editorial commentary on each.