GitHub
Security and governance controls catch up to the Copilot build-out
A side-by-side editorial comparison of RDKit and Speakeasy — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | RDKit | Speakeasy |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 2.5 | 10.0 |
| Sparks · 30d | 0 | 1 |
| Top themes | cheminformatics, stereochemistry, quarterly-releases, substructure-search | ai-governance, shadow-mcp, policy-enforcement, agent-observability |
| Last editorial update | 9d ago | 2d ago |
| Website | Visit → | — |
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.
Speakeasy stopped inventorying MCP servers and started adjudicating them.
Speakeasy ships near-daily platform releases with unusually legible notes — each headline states what changed for a user, not a version number. The current one turns the Shadow MCP page into a single review surface where every server carries an approval state and an automatically gathered evidence dossier: publisher, requested scopes, declared capabilities, maintenance signals, and whether internal teams already talk to it. Decisions enforce on record. Around it, the assistant surfaces have been consolidating: one detail panel for configuration and observation, exact session totals, and canonical identities folding a person's work and personal AI accounts together.
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.
Speakeasy ships near-daily platform releases with unusually legible notes — each headline states what changed for a user, not a version number. The current one turns the Shadow MCP page into a single review surface where every server carries an approval state and an automatically gathered evidence dossier: publisher, requested scopes, declared capabilities, maintenance signals, and whether internal teams already talk to it. Decisions enforce on record. Around it, the assistant surfaces have been consolidating: one detail panel for configuration and observation, exact session totals, and canonical identities folding a person's work and personal AI accounts together.
The arc runs observe, then intercept, now adjudicate. Earlier releases catalogued spend and inventoried shadow MCP servers; the LiteLLM integration moved enforcement to the proxy so a violating prompt dies before inference; this release supplies the judgment layer, doing the research an approver would otherwise do by hand. The supporting work points the same way — prompt-injection scanning of captured skill manifests, risk policies that pause instead of being deleted, identity resolution that reports a whole person rather than an account. Each is a piece a control plane needs before its verdicts can be trusted.
Expect approval state to start gating traffic rather than only recording a decision, and the evidence dossier to extend from MCP servers to the skills and assistants already being captured. The rollout flag on the approval workflow suggests general availability is the next step rather than new capability.
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 Speakeasy.
Security and governance controls catch up to the Copilot build-out
The 29.0 line is stabilizing in public; 29.1 opens with load-tool work rather than engine work.
Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.
WeWeb is turning the apps it builds into AI products, and metering the AI as it goes.
Workato is dismantling the assumptions that tied a Genie to one chat window at a time.
Laravel's queue work has turned from correctness into operator controls, next to Cloud-named APIs.
See all RDKit alternatives → · See all Speakeasy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Speakeasy is currently shipping more aggressively (velocity 10.0 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Speakeasy is currently shipping more aggressively (velocity 10.0 vs 2.5), 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.
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 Speakeasy alternatives in DevOps are ranked by recent ship velocity. Browse the "Speakeasy alternatives" section above for the current picks, or visit /alternatives/speakeasy for the full list with editorial commentary on each.