Retail OS
The operating system for retail — POS, inventory, loyalty — owned and omnichannel.
Useful when replacing: a rack of per-terminal retail SaaS subscriptions
Pricing · USD
Own it
Foundation · $990
Run it yourself or use optional managed hosting.
Hosted by us · optional
$29/mo optional
Cancel any month — it keeps running, because you own it. Or self-host and pay $0 forever.
The $990 Foundation includes core modules, reference workflows, deployment assets, source access, and a starter configuration for this industry. Integrations, migration, security hardening, and production workflow changes are quoted as a fixed-price Build Sprint. Optional managed hosting starts at $29/mo.
Retail OS is a configuration of Industry OS Foundation, not a separate product. The $990 foundation is the starting system; production workflow changes, integrations, and migration are scoped separately.
See Industry OSInside Retail OS
The problem
Retail runs on a stack of rented tools — POS here, inventory there, loyalty somewhere else — each charging per terminal or per location, none owning the whole customer. Your sales and stock data, the lifeblood of the business, sit in vendors' clouds.
How Retail OS solves it
POS to loyalty, one owned platform
Point of sale, inventory, promotions, and loyalty in a single system across every store and channel — one catalog, one customer.
Omnichannel and offline-ready
Registers keep selling without signal and sync when they're back; online and in-store share the same stock and the same customer record.
Built in a sprint, owned outright
Assembled from our retail components and customised to your operation — unlimited terminals, no per-location tax, handed over to you.
Delivery terms — stated precisely
How Retail OS is delivered, what you control, and where the boundaries sit.
Source included · MIT
Run it yourself or use optional managed hosting.
Data and hosting
Deploy in your cloud or use the stated optional managed-hosting plan. Data location and operator access are agreed before production use.
Compliance boundary
Residency, controls, and regulatory requirements are implementation decisions documented in the selected plan or delivery scope.
Rented vs. owned
The rented way
a rack of per-terminal retail SaaS subscriptions
- Metered pricing that scales with your success, not the value
- Your data sits in their database, exportable only through their API
- Prices rise once you're integrated and can't leave
- Switching is a migration project nobody will approve
The Retail OS way
Foundation · $990 — and then it's yours
- One price, paid once — hosting is $29/mo optional and optional, or $0 if you run it
- Self-host in your infrastructure, or use the optional managed plan under its stated data terms
- Source included · MIT — the exit terms are stated on this product
- Stop paying and nothing switches off. Leave with a git clone, not a support ticket
Built on
More to run your business
Retail OS — the questions buyers ask
Who owns the code and IP?
For a Build Sprint, the repository, deployment assets, and work-product IP described in the SOW are handed over to you. Pre-existing products retain the licence shown on their product page; hosted services remain services. We state that boundary before work starts.
What happens if a sprint misses its scope?
We finish it. Fixed price means the risk of estimation is ours, not yours — a missed scope item is completed without a new invoice. Changes you request are re-scoped explicitly, so the line between 'our miss' and 'new ask' stays honest.
How do time zones work with a pod in India?
Every engagement includes 4+ hours of overlap with US or EU working hours. Async by default — written updates, weekly clickable demos — and meetings only when they earn the slot. You'll never chase a status report.
How is our data and code kept secure?
Work happens in your repos and your infrastructure wherever possible — we hold the minimum access needed, revoked at handover. NDAs are standard on request, and everything we self-host for you runs behind your keys, not ours.
How fast can you actually start?
Scoping takes a day; most sprints start within a week of sign-off. Pods are deliberately small and senior, so your start date is confirmed in the sprint plan — not left floating.
Do we need a retainer afterwards?
No — that's the point. A sprint ends with handover docs and training. If you want us to keep maintaining what we built, that's an optional flat monthly add-on you can cancel any month, because the software keeps working without us.
Own Retail OS, don't rent it.
See the price, deploy on your infrastructure, keep the code. Or scope a sprint and we'll customise it and hand it over.