Aerospike
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
A side-by-side editorial comparison of OpenMM and RDKit — release velocity, themes, recent moves, and the top alternatives to consider.
OpenMM keeps opening new simulation domains while pushing more of the run onto the GPU
OpenMM alternates substantial minor releases roughly every five months with quick patch releases that clean up the fallout. The 8.4 and 8.5 cycles added two genuinely new capabilities — constant-potential electrodes and a Python escape hatch for machine-learning potentials — alongside the force-field refreshes and new integrators that make up its normal cadence. Performance work continues in parallel, most recently by moving energy minimization entirely onto the GPU.
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.
OpenMM alternates substantial minor releases roughly every five months with quick patch releases that clean up the fallout. The 8.4 and 8.5 cycles added two genuinely new capabilities — constant-potential electrodes and a Python escape hatch for machine-learning potentials — alongside the force-field refreshes and new integrators that make up its normal cadence. Performance work continues in parallel, most recently by moving energy minimization entirely onto the GPU.
The engine is being repositioned as a host for physics it does not implement itself. PythonForce, the OpenFF internal changes, TinkerFiles and the constant-pH groundwork all point the same way: OpenMM supplies the integrator, the GPU kernels and the force-field plumbing, and lets external ecosystems supply the model. The second thread is unglamorous and consistent — every release moves more of the simulation loop off the CPU, from the HIP platform in 8.2 to the minimizer rewrite in 8.5.
Constant pH is described as living in a separate repository with only its prerequisites merged, so the obvious next step is folding that implementation into the main release. Expect the patch-release pattern to continue as well: 8.5.0 and 8.4.0 each drew fixes within weeks, most of them in barostats and force initialization.
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.
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 OpenMM or RDKit.
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
Psi4 is closing the gap with ORCA on the methods that decide which code a lab installs
libosmium is a stable OSM parsing library whose main work now is shedding old dependencies
See all OpenMM alternatives → · See all RDKit alternatives →
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 OpenMM alternatives in DevOps are ranked by recent ship velocity. Browse the "OpenMM alternatives" section above for the current picks, or visit /alternatives/openmm for the full list with editorial commentary on each.
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.