evaluate
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
A side-by-side editorial comparison of crane and Rootly — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | crane | Rootly |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | clinical-tables, mmrm, survival-analysis, gtsummary | incident-response, agent-native, meeting-transcription, on-call |
| Last editorial update | 1h ago | 4h ago |
| Website | Visit → | — |
Crane is turning into the table-and-plot layer for Roche's clinical output stack.
Crane publishes release candidates rather than finals, and the whole of 0.3.2 is carried by a single rc2 body — its two sibling tags are one-line styling commits, one of them tagged with an unsubstituted vX.Y.Z placeholder. The rc2 notes run to dozens of additions across regression tables, line plots and hierarchical rate tables.
Rootly keeps widening what its AI observes — now the incident call itself, in any language.
The AI work runs along two lines: evidence gathering across the observability stack, and the incident call itself. Meeting Scribe now detects the language spoken on a call and transcribes it with no configuration, removing the setup step that made the feature single-language in practice. Around it sits the routine platform work — catalog sync, alert-storm muting, on-call widgets, retrospective templates.
Crane publishes release candidates rather than finals, and the whole of 0.3.2 is carried by a single rc2 body — its two sibling tags are one-line styling commits, one of them tagged with an unsubstituted vX.Y.Z placeholder. The rc2 notes run to dozens of additions across regression tables, line plots and hierarchical rate tables.
The package is moving from plotting helpers to a full analysis-output layer: mixed models for repeated measures, pairwise Cox results, risk-management-plan tables and adverse-event incidence rates all arrive in one cycle, and the annotation machinery underneath was rebuilt for reliable table-to-axis alignment. Defaults are being pulled toward SAS and rtables output — the log-rank test now uses survival::survdiff instead of coin, and survfit confidence intervals default to plain rather than log.
Expect a 0.3.2 final close behind rc2, and the deprecated g_lineplot() family to be removed once gg_lineplot() and annotate_gg() have settled.
The AI work runs along two lines: evidence gathering across the observability stack, and the incident call itself. Meeting Scribe now detects the language spoken on a call and transcribes it with no configuration, removing the setup step that made the feature single-language in practice. Around it sits the routine platform work — catalog sync, alert-storm muting, on-call widgets, retrospective templates.
The pattern is consistent: every artifact an incident produces — telemetry, chat, the call — becomes something Rootly's AI reads and turns into retrospective material. Language detection is a small change with a specific consequence: distributed teams whose incident calls are not held in English now get the same automated record as everyone else. The catalog and alerting work underneath keeps making that record attributable to a service and an owner.
Expect Scribe output to feed the retrospective AI-blocks directly, closing the loop from call to written retrospective without a manual step.
Other Infra & APIs 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 crane or Rootly.
The engine under every knitted R document reached 1.0 by making evaluation behave like the console.
carrier's 0.3.0 quietly rewrites how crated functions see each other — and breaks code that relied on the old rules.
watcher is a thin filesystem-events binding whose releases are mostly build work.
gh spent its last two releases making failures and interruptions recoverable.
checkhelper grew from a check wrapper into a CRAN pre-submission auditor.
dockerfiler's 1.0.0 changes what its generated Dockerfiles actually contain.
See all crane alternatives → · See all Rootly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rootly is currently shipping more aggressively (velocity 6.3 vs 0.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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rootly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top crane alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "crane alternatives" section above for the current picks, or visit /alternatives/crane for the full list with editorial commentary on each.
Top Rootly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rootly alternatives" section above for the current picks, or visit /alternatives/rootly for the full list with editorial commentary on each.