← Back to home
Comparison · Analytics

OpenCTI vs vellumverse

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

OpenCTI vs vellumverse: at a glance

FeatureOpenCTIvellumverse
SectorAnalyticsAnalytics
Velocity score6.35.0
Sparks · 30d00
Top themesthreat-intelligence, stix, data-model, ingestionr-graphics, meta-package, dependency-management, ecosystem
Last editorial update1d ago3d ago
WebsiteVisit →Visit →

What is OpenCTI?

OpenCTI spends a release unblocking queues and hardening upserts

7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.

Read the full OpenCTI trajectory →

What is vellumverse?

A meta-package whose entire changelog is a version pin, tracking an ecosystem moving faster than it is.

vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.

Read the full vellumverse trajectory →

OpenCTI vs vellumverse: editorial side-by-side

O
OpenCTI
ANALYTICS
6.3

OpenCTI spends a release unblocking queues and hardening upserts

◆ Current state

7.260817.0 is a fix release. The most consequential item is malformed STIX messages nacking forever and blocking worker queues indefinitely — a stall in the ingestion path rather than a display bug. Alongside it: upsert clearing an existing createdBy when incoming confidence is higher, draft upserts crashing on existing attack patterns, OTP handling in the stream middleware, and case template relation authorization. Score fields were added to threat actor groups, intrusion sets and malware.

◆ Where it's heading

The platform's feature energy went into the connector catalog and integrations rework in July, and the releases since have been consolidating: mass operations on relation times, shareable saved searches, and now a pass over ingestion robustness. Adding score to more entity types continues the slow enrichment of the data model that runs underneath the feature work.

◆ Prediction

Given score arriving on three entity types in one release, expect it to keep spreading across the data model, and the queue-blocking class of bug to draw more worker-side hardening.

V
vellumverse
ANALYTICS
5.0

A meta-package whose entire changelog is a version pin, tracking an ecosystem moving faster than it is.

◆ Current state

vellumverse attaches the vellum graphics ecosystem in one library() call, reports which versions loaded, lists the bundled packages and surfaces functions masked across them. It is deliberately dependency-light, having dropped rlang and declared only what the conflict reporter actually uses. Since 0.2.0 every release has been a version pin bump rather than new behaviour of its own.

◆ Where it's heading

The release record is an index of other packages' work: four of the last six entries do nothing but raise the floor on vellum, vellumplot and vellumwidget. The cadence tells the real story, with pins moving roughly weekly and each bump chasing a minor release somewhere downstream, so the meta-package is currently a distribution convenience rather than a component. The one genuinely structural release in the window was 0.2.1, which trimmed the dependency surface to keep an attach-only package cheap to install.

◆ Prediction

Expect the pin bumps to keep pace with the ecosystem's weekly releases rather than any feature of its own, and the pin on vellumplot to move again as the interaction grammar the widget now depends on continues to land. Whether vellumverse ever grows beyond attach-and-report is not visible in these entries.

Alternatives to OpenCTI and vellumverse

Other Analytics 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 OpenCTI or vellumverse.

See all OpenCTI alternatives → · See all vellumverse alternatives →

Recent activity from OpenCTI and vellumverse

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

  1. 2d agoOpenCTIMalformed STIX no longer blocks worker queues indefinitely
  2. 5d agoOpenCTILTS branch gets the security backport: access-scoped streams, dependency sweep
  3. 8d agoOpenCTIMass operations can now edit relation start and stop times
  4. 12d agoOpenCTISaved searches and dashboard filters become shareable and reusable
  5. 16d agoOpenCTIData sanity operations can be stopped mid-run
  6. 18d agovellumversePins raised to vellum 0.6.6, vellumplot 0.9.0, vellumwidget 0.8.0
  7. 20d agoOpenCTIIntegrations experience reworked around the new catalog, plus draft approval workflows
  8. 23d agovellumversePins raised to vellumplot 0.8.0 and vellumwidget 0.7.0
  9. 1mo agovellumversePins raised to vellum 0.5.0, vellumplot 0.6.0, vellumwidget 0.6.0
  10. 1mo agovellumversePins raised to vellum 0.4.0, vellumplot 0.5.0, vellumwidget 0.5.0
  11. 1mo agovellumverseDependency surface trimmed to keep the meta-package light
  12. 1mo agovellumverseAdopts vellum's renamed vl_* graphics primitives

Frequently asked questions

What is the difference between OpenCTI and vellumverse?

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

Is OpenCTI better than vellumverse?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to OpenCTI?

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

What are the best alternatives to vellumverse?

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