Aerospike
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
A side-by-side editorial comparison of RDKit and Psi4 — release velocity, themes, recent moves, and the top alternatives to consider.
Quarterly majors set the breaking changes; the patch train spends the rest of the year on stereochemistry
RDKit runs a strict quarterly cadence — a 2026_03 major followed by monthly patch releases through the quarter. The major carried the breaking changes: Dict keys moved to std::string_view, SMARTS AND-query merging, _CIPRank no longer set by default on molecules without chiral centers, altered hydride removal, and MolToSmarts no longer adding implicit hydrogens. Every patch since has been dominated by stereochemistry correctness and drawing options, with steady performance work on CIP labelling and synthon substructure search.
Psi4 is closing the gap with ORCA on the methods that decide which code a lab installs
Psi4 ships a major version roughly annually with a trail of conda-compatibility patch releases behind each one. The 1.11 cycle is the most competitively pointed in the window: DLPNO-CCSD and DLPNO-CCSD(T) become callable methods, with cutoffs deliberately tuned to match ORCA, and ZORA arrives for scalar-relativistic core Hamiltonians. Around the science, the project spends heavily on Python-ecosystem plumbing — QCSchema v2, Python 3.14 support, and the QCArchive dependency chain that most of its patch releases exist to unbreak.
RDKit runs a strict quarterly cadence — a 2026_03 major followed by monthly patch releases through the quarter. The major carried the breaking changes: Dict keys moved to std::string_view, SMARTS AND-query merging, _CIPRank no longer set by default on molecules without chiral centers, altered hydride removal, and MolToSmarts no longer adding implicit hydrogens. Every patch since has been dominated by stereochemistry correctness and drawing options, with steady performance work on CIP labelling and synthon substructure search.
Two threads run through the patch train. Stereochemistry is the persistent bug surface — atropisomers, E/Z retention through CDXML and fragment extraction, ring-bond consistency in the bounds matrix builder, aromaticity in polycyclic conjugated systems — which is what happens when a cheminformatics toolkit is the reference implementation everyone's edge cases land on. Separately, search and conformer generation keep getting faster: synthon substructure search doubled, CIP labelling stopped computing auxiliary descriptors unnecessarily, and ETKDG gained all-in-one coordinate refinement.
Expect the 2026_03 line to keep receiving stereochemistry fixes until the next quarterly major, which is where any further backwards-incompatible API changes will be batched.
Psi4 ships a major version roughly annually with a trail of conda-compatibility patch releases behind each one. The 1.11 cycle is the most competitively pointed in the window: DLPNO-CCSD and DLPNO-CCSD(T) become callable methods, with cutoffs deliberately tuned to match ORCA, and ZORA arrives for scalar-relativistic core Hamiltonians. Around the science, the project spends heavily on Python-ecosystem plumbing — QCSchema v2, Python 3.14 support, and the QCArchive dependency chain that most of its patch releases exist to unbreak.
Two things are being built at once. Scientifically, the code is filling in the local-correlation and relativistic methods that users otherwise leave for commercial packages, plus external-potential and embedding machinery that makes Psi4 usable as a QM engine inside larger workflows. Structurally, it is betting on the QCArchive stack — qcelemental, qcengine, qcmanybody, optking, qcfractal — which delivers interoperability but also means a Python packaging change downstream can force a release, as 1.10.1 and 1.10.2 both did.
The DLPNO work landed as energies only, so analytic gradients for DLPNO-CCSD are the natural next step. Expect at least one more 1.11.x patch driven by the QCFractal and pydantic constraints that the 1.11 notes flag as still unresolved for Python 3.14.
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 RDKit or Psi4.
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
Firebird maintains three release branches at once and ships the same fixes to all of them
GeoTools is migrating off dead Java imaging infrastructure that the whole GeoServer stack sits on
SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer
libosmium is a stable OSM parsing library whose main work now is shedding old dependencies
OpenMM keeps opening new simulation domains while pushing more of the run onto the GPU
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. RDKit is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. RDKit is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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.
Top RDKit alternatives in DevOps are ranked by recent ship velocity. Browse the "RDKit alternatives" section above for the current picks, or visit /alternatives/rdkit for the full list with editorial commentary on each.
Top Psi4 alternatives in DevOps are ranked by recent ship velocity. Browse the "Psi4 alternatives" section above for the current picks, or visit /alternatives/psi4 for the full list with editorial commentary on each.