← Back to home
Comparison · E-comm

Hi.Events vs Solidus

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

Hi.Events vs Solidus: at a glance

FeatureHi.EventsSolidus
SectorE-commE-comm
Velocity score6.35.0
Sparks · 30d10
Top themesevent-ticketing, open-core, self-hosted, box-officeecommerce, admin-ui, rails, breaking-changes
Last editorial update3d ago15d ago
WebsiteVisit →Visit →

What is Hi.Events?

Hi.Events 2.0 rc.3 adds paid Enterprise features: reserved seating and a box office.

Hi.Events v2.0.0-rc.3 adds reserved seating with a visual seat-map designer and a browser-based box office with Stripe Terminal card readers, both marked Enterprise and requiring a licence in production. It also adds a per-product purchases view, refunds on manual orders and grouped ticket emails. On 1.x, v1.11.3 refuses to run while the example JWT_SECRET that earlier versions shipped is still configured, since anyone could forge sessions with it, and v1.11.2 rebuilt on patched PHP.

Read the full Hi.Events trajectory →

What is Solidus?

Solidus admin 0.5.0 fills in settings editors and swaps pagination for Kaminari.

solidus_admin, Solidus's newer admin interface, shipped 0.5.0, its first feature release since 0.4.0. It adds editors for tax rates, payment methods, stores, zones, stock locations and option types, taxon management on the product page, and faster order and product index pages. It also breaks compatibility: pagination moves from Geared Pagination to Kaminari, and the floor rises to Solidus 4.6 and Ruby 3.2.

Read the full Solidus trajectory →

Hi.Events vs Solidus: editorial side-by-side

H
Hi.Events
E-COMM
6.3

Hi.Events 2.0 rc.3 adds paid Enterprise features: reserved seating and a box office.

◆ Current state

Hi.Events v2.0.0-rc.3 adds reserved seating with a visual seat-map designer and a browser-based box office with Stripe Terminal card readers, both marked Enterprise and requiring a licence in production. It also adds a per-product purchases view, refunds on manual orders and grouped ticket emails. On 1.x, v1.11.3 refuses to run while the example JWT_SECRET that earlier versions shipped is still configured, since anyone could forge sessions with it, and v1.11.2 rebuilt on patched PHP.

◆ Where it's heading

The 2.0 cycle has gone from structural changes (recurring occurrences, embedded checkout, an API) to venue-grade features, and now to an open-core split between free self-hosting and licensed Enterprise features. The 1.x line is in security-only mode, with users pushed toward 2.0.

◆ Prediction

Expect a 2.0.0 final soon after rc.3, with the Enterprise licence terms spelled out, and 1.x limited to security fixes.

S
Solidus
E-COMM
5.0

Solidus admin 0.5.0 fills in settings editors and swaps pagination for Kaminari.

◆ Current state

solidus_admin, Solidus's newer admin interface, shipped 0.5.0, its first feature release since 0.4.0. It adds editors for tax rates, payment methods, stores, zones, stock locations and option types, taxon management on the product page, and faster order and product index pages. It also breaks compatibility: pagination moves from Geared Pagination to Kaminari, and the floor rises to Solidus 4.6 and Ruby 3.2.

◆ Where it's heading

The new admin is filling in the settings screens a store needs before it can replace the legacy backend, and it's taking breaking changes while still pre-1.0. The team is splitting large migrations into separate releases so stores can absorb them one at a time; the ViewComponent 4 upgrade was deliberately held back to its own release.

◆ Prediction

The release notes say solidus_admin 0.6.0 with ViewComponent 4 ships immediately after this one, and it will require stores to update their ViewComponent 3 storefront code.

Alternatives to Hi.Events and Solidus

Other E-comm 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 Hi.Events or Solidus.

See all Hi.Events alternatives → · See all Solidus alternatives →

Recent activity from Hi.Events and Solidus

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

  1. 5d agoHi.Eventsv1.11.3: blocks the forgeable example JWT secret
  2. 5d agoHi.Events2.0 rc.3: reserved seating and box office (Enterprise) ⚡
  3. 7d agoHi.Eventsv1.11.2: rebuild on patched PHP for two CVEs
  4. 15d agoSolidusSolidus admin 0.5.0 adds settings editors, moves to Kaminari
  5. 22d agoSolidussolidus_admin 0.4.1 fixes stored XSS on Items Purchased page
  6. 27d agoHi.Events2.0 rc.2: per-date tickets, tier sequencing, AI moderation
  7. 2mo agoHi.Events2.0 rc.1: recurring events, embedded checkout and a REST API ⚡
  8. 2mo agoHi.Events1.11.1: webhook SSRF and export injection fixes

Frequently asked questions

What is the difference between Hi.Events and Solidus?

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

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

What are the best alternatives to Hi.Events?

Top Hi.Events alternatives in E-comm are ranked by recent ship velocity. Browse the "Hi.Events alternatives" section above for the current picks, or visit /alternatives/hi-events for the full list with editorial commentary on each.

What are the best alternatives to Solidus?

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