Solidus

Open-source eCommerce, honestly reviewed. Built for developers, priced at zero, priced in engineering time.

TL;DR

• What it is: Open-source (BSD) eCommerce framework built on Ruby on Rails — a fork of Spree Commerce, started in 2015. Not a SaaS, not a hosted platform. A code framework you own, deploy, and maintain [GitHub README][1].
• Who it’s for: Brands with in-house Rails developers or a budget to hire a Solidus agency. Explicitly not for non-technical founders who want to launch without writing code [website].
• Cost savings: Shopify Advanced runs $399/mo before 0.5% transaction fees that can add hundreds more at volume. Solidus software is free; a $20/mo VPS plus a developer is your actual cost. But that developer cost is real.
• Key strength: No platform constraints, no transaction fees, proven at scale (Wonderbly ships millions of personalized books on it), BSD license [website][1].
• Key weakness: Requires Ruby on Rails expertise. A non-technical founder touching this without a developer will not have a good time. Community is active but smaller than WooCommerce or Shopify’s ecosystem.

---

What is Solidus

Solidus is a complete eCommerce framework built on Ruby on Rails. It is a fork of Spree Commerce — the codebase diverged around 2015 when a group of agencies wanted a more stable, community-governed alternative to Spree’s vendor-controlled direction. The GitHub description says it plainly: ”🛒 Solidus, the open-source eCommerce framework for industry trailblazers.” [GitHub README].

The framework ships as a set of Ruby gems. When you add solidus to your Gemfile, you get [GitHub README]:

• solidus_core — the essential models, mailers, and business logic
• solidus_api — a RESTful API layer
• solidus_backend — the admin interface
• solidus_sample — seed data for development

You can use all of them, or just solidus_core and build your own frontend, admin, and API on top. That modularity is either a feature or a warning sign, depending on what you’re trying to do.

As of this review, the project sits at 5,273 GitHub stars [merged profile]. Nebulab, an Italian Rails consultancy, is the primary code contributor and project director [GitHub README]. It is community-governed and funded through Open Collective, with supporter, bronze, silver, and gold partner tiers. That governance model matters: Solidus has no single commercial owner who can pivot the license or raise prices overnight. The tradeoff is that the roadmap moves at community pace.

The project has a live demo at demo.solidus.io with admin access — useful for evaluating the UI before committing to anything.

---

Why people choose it over Shopify, WooCommerce, and Magento

The facts.dev profile [1] summarizes Solidus accurately but briefly. Third-party reviews are sparse compared to younger, better-marketed tools. What exists paints a consistent picture: Solidus is chosen by teams that have hit the ceiling on hosted platforms and need genuine code-level control.

Versus Shopify. Shopify’s core appeal is zero setup friction. Its core problem is that it monetizes your growth. Transaction fees (0.5–2% on Advanced and below if you’re not on Shopify Payments), monthly fees that scale with your tier, and app store costs that stack up — a mid-volume merchant can easily be paying $600–$900/mo in combined platform costs. Solidus charges none of that. You pay for hosting and for developer time. At sufficient volume ($500K+ GMV/year), the math tips heavily toward Solidus — but the prerequisite is that you have Rails engineering capacity.

Versus WooCommerce. WooCommerce is the obvious “free alternative” for most people, and for non-technical founders it’s the more realistic choice. It runs on WordPress, which lowers the barrier significantly. Solidus is a better choice when you need complex order logic, subscriptions, multi-currency, or high-performance catalog operations — use cases where WordPress starts showing its age. One Solidus website testimonial puts it directly: Wonderbly sells “millions of personalized books all over the world” and chose Solidus because it handles the complexity while giving them “the power to customize where needed” [website].

Versus Magento / Adobe Commerce. Magento Open Source is also free and PHP-based. The community has spent years complaining about its complexity, upgrade pain, and resource requirements. Solidus’s Rails codebase is generally considered cleaner and more developer-friendly. The downside is that the Rails talent pool is smaller than PHP — finding a Solidus developer is harder than finding a WooCommerce developer.

Versus Medusa.js. Medusa is the newer, TypeScript-first challenger that targets the same “you own your commerce layer” audience. Solidus has a decade-plus head start in maturity and a proven track record at real GMV scale. Medusa has a larger modern JavaScript ecosystem to draw from. If you’re starting fresh in 2026 and your team writes TypeScript, Medusa is worth comparing seriously. If your team writes Rails, Solidus is the mature choice.

The website cites brands including Goby and Wonderbly as customers — both are real DTC brands with non-trivial product complexity [website]. That’s more credible than the usual SaaS testimonials of logo farms with no details.

---

Features

From the GitHub README and website:

Core commerce:

• Product catalog with variants, properties, and option types
• Inventory and stock location management
• Order management with full state machine
• Multi-store support
• Promotions engine — described as “the most powerful promotion system ever found on an eCommerce platform” on the website, which is marketing but the underlying system is genuinely flexible [website]
• Native subscriptions support for curated box and recurring billing models [website]

Payments and fulfillment:

• Payment gateway abstraction (Stripe, Braintree, and others via extensions)
• Multi-currency support
• Shipping calculator framework with custom logic
• Fulfillment provider integrations

Internationalization:

• Full i18n for content, fulfillment, and payment methods [website]
• Multi-language storefront support

Merchandising:

• First-party and zero-party data hooks for personalization [website]
• Upsell and cross-sell primitives
• Content and commerce blending

Developer tooling:

• Full REST API via solidus_api gem [GitHub README]
• Extension system via Ruby gems — hundreds of community extensions available
• Starter frontend theme for quick launch [website]
• PostgreSQL, MySQL, and SQLite support [merged profile]
• Docker and Docker Compose for local development [merged profile]

Admin:

• Built-in admin backend (solidus_backend)
• Order processing, customer management, promotions configuration, inventory [GitHub README]

Not included out of the box:

• A modern headless/Jamstack frontend — you build this yourself or use the starter theme
• Real-time search (Elasticsearch integration via extension)
• Analytics — you connect your own

---

Pricing: SaaS vs self-hosted math

Solidus itself is free software under the BSD license. No per-transaction fees, no monthly license, no usage caps. The costs are infrastructure and engineering.

Shopify for comparison:

• Basic: $39/mo + 2% transaction fees (if not using Shopify Payments)
• Shopify: $105/mo + 1% fees
• Advanced: $399/mo + 0.5% fees
• Plus: starts at $2,300/mo

For a merchant doing $50K/mo GMV on Shopify Advanced with a payment processor that isn’t Shopify Payments: $399 platform + $250 in transaction fees + $100–200 in apps = $750–850/mo. That’s $9,000+/year before the app costs keep growing.

Solidus self-hosted:

• Software: $0
• VPS (sufficient for moderate traffic, e.g., Hetzner or DigitalOcean): $20–80/mo depending on load
• Payment processing: Stripe’s 2.9% + $0.30 applies regardless of platform
• Initial developer setup: one-time cost, varies widely
• Ongoing Rails developer for maintenance and features: the real variable

Concrete math: If you’re paying a freelance Rails developer $500/month for 5 hours of maintenance and your VPS costs $40/mo, you’re at $540/mo. That breaks even against Shopify Advanced at roughly the same GMV — and you keep more as volume scales because there’s no platform percentage taking a cut. At $200K/mo GMV the Shopify Advanced transaction fee alone (if you’re not on their payments) is $1,000/mo.

The savings aren’t automatic. They depend on your developer costs. For a non-technical founder with no Rails developer, Solidus costs more in real terms because you’d need to hire one. Data not available on Solidus’s enterprise pricing (their managed hosting tier) — contact sales.

---

Deployment reality check

This is where honest assessment matters most for the target audience.

Solidus is a Ruby on Rails application. Deploying it is not the same as running docker-compose up on a pre-packaged tool. The minimal stack you need [GitHub README]:

• Ruby (specific version managed via rbenv or asdf)
• Rails
• PostgreSQL or MySQL
• ImageMagick (required for product image processing)
• A Rails application server (Puma)
• A background job processor (Sidekiq, which requires Redis)
• A reverse proxy (nginx or Caddy) for HTTPS
• A domain and SSL certificate

The website says “get started in hours” — that’s true for a developer who’s deployed Rails apps before. For someone who has never done it, budget a full day to a full week depending on familiarity.

Hosting options:

• Render or Fly.io: Modern Rails-friendly PaaS, reduces ops burden significantly, costs $15–50/mo for starter loads
• Heroku: Still works, more expensive than Render for equivalent resources
• Hetzner/DigitalOcean VPS: Cheapest, most control, requires you to manage the server yourself
• Heroku-style platforms (Railway, Render): Good middle ground

What can go sideways:

• Gem version conflicts during upgrades are a Rails rite of passage — not Solidus-specific but worth naming
• ImageMagick installation fails silently on some Linux configurations
• Asset pipeline configuration can trip up developers newer to Rails
• The default backend UI (solidus_backend) is functional but dated-looking — many production stores invest in a custom admin or a modern frontend from scratch

A Solidus-experienced Rails developer (or a Solidus agency like Nebulab, Super Good Software, or similar) can have a store in production in one to two days. Without that experience, the timeline is unpredictable.

---

Pros and cons

Pros

• BSD license with no commercial restrictions. You can fork it, embed it in your SaaS, resell stores built on it, white-label it — no commercial agreement needed. This is rarer than it sounds: WooCommerce is GPLv2, Magento has dual-licensing complications [GitHub README].
• No transaction fees, ever. Platform takes zero percentage of your revenue. At any meaningful GMV this matters more than monthly software costs.
• Proven at real scale. Wonderbly and Goby are named publicly as customers. These aren’t toy stores [website].
• Complete REST API included. solidus_api ships with the framework — you can build a fully headless storefront from day one [GitHub README].
• Native subscriptions engine. Built in, not bolted on. Many platforms charge extra for subscription functionality or require third-party apps [website].
• Mature promotions system. The flexibility here is genuine — custom promotion logic is possible without monkey-patching [website][1].
• Rails extension ecosystem. Hundreds of gems extend the platform. If someone has needed it for a Rails commerce store in the last decade, there’s probably a gem.
• Community-governed. No single vendor controls the roadmap. Nebulab directs but doesn’t own [GitHub README].

Cons

• Requires Ruby on Rails expertise. This is the central limitation. Non-technical founders cannot self-deploy and self-maintain this. You will need a developer. Period.
• Smaller community than WooCommerce or Shopify. 5,273 GitHub stars is modest. Finding freelance Solidus developers is harder than finding WooCommerce or even Shopify app developers.
• No managed hosting. The enterprise tier on solidus.io mentions a fully hosted solution, but pricing is contact-sales. For small merchants there is no simple $X/month plan that takes away the ops burden.
• The admin UI hasn’t aged gracefully. solidus_backend is functional and battle-tested, but the visual design lags behind modern standards. Stores that care about admin experience often build custom or invest in a third-party theme.
• Setup complexity is high. ImageMagick, Redis, PostgreSQL, asset pipeline — each is a failure point for teams without Rails experience.
• Thin third-party review coverage. Finding honest, detailed third-party reviews of Solidus is harder than for Shopify or WooCommerce. The community is real but smaller and quieter online.
• Nebulab dependency risk. One agency is the primary code contributor and director. If Nebulab’s priorities shifted, the project’s velocity would feel it. Open Collective funding and the ambassador program partially mitigate this, but it’s not a multi-hundred-contributor project.

---

Who should use this / who shouldn’t

Use Solidus if:

• You have a Rails developer (in-house or contracted) or budget to hire a Solidus agency.
• You’re selling at a volume where Shopify’s transaction fees or app stack is costing you $500+/mo.
• You need commerce logic complex enough that hosted platforms keep saying “that’s not possible without a workaround.”
• You’re building subscriptions, multi-store, complex fulfillment rules, or a marketplace — and you want it all in one Rails codebase.
• You care about the BSD license and want zero platform dependency risk.

Skip it (use WooCommerce) if:

• You’re a non-technical founder who wants to manage everything yourself without a developer.
• Your store is WordPress-native and the WordPress ecosystem meets your needs.
• You want the largest plugin/extension marketplace possible.

Skip it (stay on Shopify) if:

• You’re under $500K GMV/year and the monthly fees are manageable.
• Your team has zero Rails experience and no budget to hire.
• You prioritize zero ops burden over cost savings.
• You need a rich app store where any integration you can imagine already exists.

Skip it (look at Medusa.js) if:

• You’re a TypeScript/Node.js team starting fresh.
• You want a headless-first architecture from day one without the Rails overhead.
• Your engineering team is more comfortable in the JavaScript ecosystem.

---

Alternatives worth considering

• Spree Commerce — the project Solidus forked from. Still active. Has diverged significantly; Solidus has generally been considered more stable for production use. Worth comparing if you’re evaluating Rails options.
• WooCommerce — the realistic choice for non-technical founders. PHP/WordPress, massive plugin ecosystem, much lower barrier to entry. Less performant for complex catalog logic.
• Magento Open Source — PHP, free, powerful, famously complex to operate. Has a larger agency ecosystem than Solidus globally.
• Medusa.js — TypeScript-first, modern API design, growing fast. The challenger to watch for teams that don’t want Rails.
• Shopify — closes the “I don’t have a developer” gap entirely. Costs more at scale. Zero ops risk.
• PrestaShop — PHP, open source, European market focus. Smaller than WooCommerce.
• Bagisto — Laravel-based, newer, lighter. Growing option if your team writes PHP/Laravel.

---

Bottom line

Solidus is the right choice for a narrow but specific buyer: a brand with real eCommerce complexity, Rails engineering capacity, and enough volume that platform fees matter. It is not the tool for a non-technical founder who saw “free and open source” and wants to escape a Shopify bill without hiring a developer — that path ends in a half-deployed Rails app and a support ticket to nobody. For the right team, though, the BSD license, zero transaction fees, proven scalability, and complete code ownership are a genuinely compelling package that no hosted SaaS can match. The math at $500K+ GMV is hard to argue with. The prerequisite is being honest about what it takes to get there.

If you need Solidus deployed and don’t have a Rails developer, that’s exactly the kind of one-time setup work upready.dev handles for clients.

---

Sources

1. Facts.dev — Solidus profile (aggregated project data). https://www.facts.dev/p/solidus/

Primary sources:

• GitHub repository and README: https://github.com/solidusio/solidus (5,273 stars, BSD license, Nebulab as primary contributor)
• Official website: https://solidus.io/
• Live demo: http://demo.solidus.io/
• Guides: https://guides.solidus.io/
• Open Collective: https://opencollective.com/solidus