Artillery
Half the release notes are a Playwright version bump; the other half is cloud-runner damage control.
Comparison · DevOps
SchemaHero vs Manticore Search
A side-by-side editorial comparison of SchemaHero and Manticore Search — release velocity, themes, recent moves, and the top alternatives to consider.
SchemaHero vs Manticore Search: 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 Manticore Search?
One real release hides inside a stream of per-commit tags: UUID document IDs arrive.
The feed carries two granularities at once — individual commit tags like a dependency bump or a revert, and a single curated release-notes post for 28.6.6 that gathers the actual user-facing work. That release is where the substance sits: UUID document IDs for real-time tables, including generated or explicit IDs and UUID-based filters, REPLACE, UPDATE, and DELETE, plus an ordered and limited GROUP_CONCAT() that keeps the top N values per group. Everything else in the window is version bumps to the Buddy sidecar and the backup tool, a revert, and compatibility repair.
SchemaHero vs Manticore Search: 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.
Manticore Search
5.0DEVOPS
One real release hides inside a stream of per-commit tags: UUID document IDs arrive.
◆ Current state
The feed carries two granularities at once — individual commit tags like a dependency bump or a revert, and a single curated release-notes post for 28.6.6 that gathers the actual user-facing work. That release is where the substance sits: UUID document IDs for real-time tables, including generated or explicit IDs and UUID-based filters, REPLACE, UPDATE, and DELETE, plus an ordered and limited GROUP_CONCAT() that keeps the top N values per group. Everything else in the window is version bumps to the Buddy sidecar and the backup tool, a revert, and compatibility repair.
◆ Where it's heading
New surface area keeps arriving through the Buddy sidecar rather than the core daemon — the latest bump brings Unix socket support — which makes Buddy the component to watch for capability changes. The second thread is fallout from the authentication work: making USER a syntax token broke MySQL client status commands, and 28.6.6 had to restore USER() parsing. The 28.8.1 revert of UTF-8 table and field names, undone because it was merged by mistake, is a reminder that the tag stream is a working branch and not a curated changelog.
◆ Prediction
UTF-8 table and field names were pulled as an accidental merge rather than rejected on their merits, so the likeliest next move is that support returning deliberately in a later tagged release. Expect further SQL-compatibility patches in the same vein as the USER() fix as more of the auth surface meets real MySQL clients.
Alternatives to SchemaHero and Manticore Search
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 Manticore Search.
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 Manticore Search alternatives →
Recent activity from SchemaHero and Manticore Search
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoManticore SearchBuddy 4.4.0 brings Unix socket support
- 2d agoManticore SearchUTF-8 table and field names reverted after an accidental merge
- 2d agoManticore SearchBuddy dependency bumped to 4.3.0
- 8d agoManticore SearchUUID document IDs and ordered GROUP_CONCAT land in 28.6.6
- 9d agoManticore SearchUSER() parsing restored after auth made USER a keyword
- 10d agoManticore Searchmanticore-backup bumped to 1.10.2
- 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
Frequently asked questions
What is the difference between SchemaHero and Manticore Search?
They serve adjacent needs but don't currently overlap on shipped themes. SchemaHero and Manticore Search are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is SchemaHero better than Manticore Search?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. SchemaHero and Manticore Search are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Manticore Search?
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.