← Back to home
Comparison · Infra & APIs

campsis vs Volatility

A side-by-side editorial comparison of campsis and Volatility — release velocity, themes, recent moves, and the top alternatives to consider.

campsis vs Volatility: at a glance

FeaturecampsisVolatility
SectorInfra & APIsInfra & APIs
Velocity score3.80.0
Sparks · 30d10
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacememory-forensics, plugin-taxonomy, linux-coverage, structured-output
Last editorial update3h ago14d ago
WebsiteVisit →Visit →

What is campsis?

Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.

Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.

Read the full campsis trajectory →

What is Volatility?

Volatility 3 caught up with Volatility 2, then started reorganising itself.

The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.

Read the full Volatility trajectory →

campsis vs Volatility: editorial side-by-side

C
campsis
INFRA · APIS
3.8

Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.

◆ Current state

Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.

◆ Where it's heading

The 1.8 and 1.9 releases together describe a package being made drivable from outside R. JSON interfaces arrived first for models in Campsismod 1.3.0 and for datasets in Campsis 1.8.0, then extended to scenarios, settings and study replication; the output side has now been generalised the same way, from fixed result processing to a collection of output functions applied to simulated results. Renaming every function and cutting RxODE loose is the cost of that consolidation, paid in one deliberate breaking release rather than spread across several.

◆ Prediction

With the rename and the RxODE removal behind it, the next releases should restore the rxode2 engine to the test suite, which 1.9.0 removed temporarily, and continue filling out the output-function catalogue beyond NCA. The JSON surface looks like the intended entry point for driving Campsis from outside R, though the entries do not say what is meant to consume it.

V
Volatility
INFRA · APIS
0.0

Volatility 3 caught up with Volatility 2, then started reorganising itself.

◆ Current state

The 2.26.0 release was explicitly aimed at functional parity with the archived Volatility 2, landing around twenty plugins at once across Linux, macOS and Windows. Since then the work has shifted from filling gaps to structuring what exists: malware-specific plugins moved under a malware namespace with the old names deprecated, an arrow/parquet output renderer added, volshell given breakpoints, and per-release additions like sockscan, process_spoofing, pebmasquerade and etwpatch.

◆ Where it's heading

Two things are happening at once. The plugin catalogue keeps growing on the Linux side in particular — tracing, kallsyms, ftrace, VMA scanning, smearing protection — reflecting where memory forensics currently has the least coverage. And the framework is being made into something other tools consume: structured output formats, a shipped Windows executable, a namespaced plugin taxonomy with a year-long deprecation window. The project is treating plugin names as an interface it owes users stability on.

◆ Prediction

Expect the malware namespace migration to complete as the deprecated names age out, and the Linux plugin surface to keep taking the bulk of new additions, with output-format work continuing to open the framework to automated pipelines.

Alternatives to campsis and Volatility

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 campsis or Volatility.

See all campsis alternatives → · See all Volatility alternatives →

Recent activity from campsis and Volatility

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 15d agocampsissnake_case across the API; RxODE compatibility removed
  2. 3mo agoVolatility2.28.0 adds sockscan and process_spoofing, improves Intel scanning
  3. 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
  4. 6mo agoVolatility2.27.0 adds an arrow/parquet renderer and pebmasquerade
  5. 7mo agocampsisMaintenance release for future package warnings
  6. 7mo agocampsisJSON import for Campsis datasets
  7. 10mo agoVolatility2.26.2 moves malware plugins into their own namespace
  8. 1y agoVolatility2.26.0 reaches functional parity with Volatility 2
  9. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  10. 1y agocampsisParameter uncertainty from SIR and bootstrap output
  11. 1y agoVolatility2.11.0 adds fifteen plugins and raises the Python floor to 3.8
  12. 1y agoVolatility2.8.0 adds vmscan and a batch of Windows injection plugins

Frequently asked questions

What is the difference between campsis and Volatility?

They serve adjacent needs but don't currently overlap on shipped themes. campsis is currently shipping more aggressively (velocity 3.8 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.

Is campsis better than Volatility?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. campsis is currently shipping more aggressively (velocity 3.8 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.

What are the best alternatives to campsis?

Top campsis alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsis alternatives" section above for the current picks, or visit /alternatives/campsis for the full list with editorial commentary on each.

What are the best alternatives to Volatility?

Top Volatility alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Volatility alternatives" section above for the current picks, or visit /alternatives/volatility for the full list with editorial commentary on each.