Skip to content
Contact
The whole journey

Enterprise self-hosted ecommerce

Ecommerce you host yourself, built on Saleor for the commerce engine and Hugo for the storefront. You own the code, the data and the infrastructure, and nobody takes a percentage of every order.

Saleor is an open-source commerce back end: products, variants, pricing, stock, carts, checkout, orders, customers, discounts, tax and payments, all behind a GraphQL API with Postgres underneath. It is written in Python, which is one of the two languages we build in anyway, and because it is open source the version you run is one you can read, patch and pin.

Hugo builds the storefront. Product and category pages are generated from the Saleor API and served as static files, so the pages shoppers spend most of their time on involve no application server at all. They come off a CDN in milliseconds and behave the same whether ten people or ten thousand are looking. The parts that genuinely must be live, stock, cart, checkout and anything tied to a signed-in account, talk to Saleor from the browser. This site runs on Hugo too, which is not a coincidence.

The case is usually arithmetic. A platform charging a percentage of revenue is good value at some volumes and poor at others, and the crossover arrives sooner than people expect once apps, transaction fees and plan upgrades are counted. The second reason is that hosted platforms are opinionated, which is fine until your business is not: B2B contract pricing, per-account catalogues, approval steps and an ERP that predates the web are all things you end up fighting a platform over.

We will say plainly when this is the wrong answer. Modest volume, a simple catalogue and no real integration means Shopify will serve you better than we will. This is worth doing when platform fees have become a real line item, when the catalogue or the pricing has outgrown what a hosted plan allows, or when the data has to stay somewhere specific.

Owning the store does not mean you have to run the servers. If you would rather not, our trusted hosting partners run the infrastructure, and our marketing partners can help get the word out at launch.

It rarely arrives alone. Getting the rules straight first is requirements gathering, and the integrations into your existing systems are bespoke software by another name. Running your own store means owning its security, which is security automation. If the marketing site around it needs the same treatment, that is website development, and if your team would rather run all of this themselves afterwards, that is training in the modern web.

SaleorHugoGraphQLPostgres

What you get

  • Saleor running on infrastructure you control, not a tenant on someone else's
  • A Hugo storefront that serves as static files and does not fall over on your biggest day
  • Catalogue, customers and orders in a database you can query, export and back up yourself
  • Payments, tax, shipping and fulfilment wired to the providers you already use
  • Integration with the ERP, accounting or warehouse system you already run
  • No per-transaction platform fee, and no plan tier deciding what you are allowed to build

How it works

  1. 01

    Scope

    Catalogue shape, pricing rules, tax, shipping, and every system the store has to talk to, agreed before anything is built.

  2. 02

    Build

    Saleor stood up and configured, the storefront built against it, payments and fulfilment connected and tested with real money.

  3. 03

    Cut over

    Data migrated, redirects mapped, launched behind monitoring, and handed over with a runbook your team can follow.