Why we're building a store platform you can self-host
The open-source commerce world has plenty of carts. What it doesn't ship is turnkey, multi-tenant 'be-your-own-store-platform' — self-signup, per-tenant domains, own-your-database — in the free core. That gap is the whole reason Bizdia exists.
The best commerce platforms were born inside real stores. Their founders couldn't find software they liked, so they built their own — and the platform underneath the shop turned out to be the real business. We're running the same playbook, on purpose.
Our founding store, Seifelden, sells computer memory and drives: thin margins, and a catalog where one physical part fits a thousand different machines. Every capability that store needs — order push to fulfillment, brandable themes, and (in development) a fitment catalog — we build once as a platform module. That inventory of modules is the product other merchants will buy.
The gap nobody fills
We ran a 2026 bake-off across the credible open-source stacks — Spree, Medusa, Bagisto, Saleor. The finding was blunt: none ship turnkey multi-tenant 'be-your-own-store-platform' in their free core. You get a cart, not a control plane. Self-signup, per-tenant domains and per-tenant billing are always a custom build or an enterprise SKU.
The mainstream hosted platform we'd been on got closed as too expensive and too rigid once the catalog crossed a thousand-plus listings mapping to a handful of SKUs. So the niche was clear: cheap, self-hosted, own-your-database multi-tenant commerce, tuned for fitment-scale catalogs.
Own your database
The line we won't cross is data lock-in. Bizdia runs on your PostgreSQL, on an open-source commerce core. On managed hosting you can export everything; self-hosted, the data never leaves your servers to begin with. 'Be your own platform' has to mean owning the box, not renting a slice of someone else's.
Build every feature once, configure it per store. There is no throwaway 'Seifelden codebase' — the storefront, the integrations, the themes and the (in-development) fitment engine are all Bizdia assets that a merchant configures.
That doctrine keeps us honest. If a feature only helps one store, it's content or a design choice. If it helps commerce broadly, it's a module — and it ships to everyone.