Self-hosting your store: owning the database, the binaries, and the log

Self-hosting a store is a trade, not a religion. You take on operations you used to rent, and in exchange you get three things a hosted platform can never fully give you: the database, the binaries, and the audit log — all on hardware you control.

What “self-hosted” really means here

It means the commerce engine runs as a process you deploy, against a database you administer, on a server you can SSH into. No per-seat billing meter, no “contact sales to export your data,” no feature held hostage behind a plan tier. When the vendor has a bad quarter, your store doesn’t change.

That’s the upside stated fairly. Now the honest cost: you run the backups, you patch the OS, you get paged when the disk fills. A hosted platform absorbs all of that for a monthly fee, and for many businesses that fee is cheaper than the engineer-hours self-hosting eats. Anyone who tells you self-hosting is strictly better is selling something.

The three things you own

1. The database

Your catalog, your customers, your orders — as rows you can query, dump, and move. This is the one that matters most when a relationship ends. Migrating off a SaaS platform can mean reverse-engineering an export format; migrating a database you already own is a pg_dump away. If you ever do need to move, our notes on migrating a catalog with bulk import and ERP feeds apply in both directions.

2. The binaries

You hold the actual artifact that runs your store, and — when the license allows it — the source behind it. That means you can pin a version through your busy season, patch a bug yourself the afternoon you find it instead of filing a ticket, and audit exactly what the code does with a customer’s card. Whether you’re allowed to read and modify that source depends entirely on the license, which is why source-available versus open source is worth understanding before you commit.

3. The audit log

Every price change, every refund, every admin action — recorded, on your infrastructure, retained as long as you decide. When an agent or a staff member does something surprising, the log is how you find out what and reverse it. Hosted platforms keep logs too, but you see the slice they choose to expose, for the window they choose to keep.

When you should not self-host

Skip it if any of these are true and you can’t change them:

• You have no one who’s comfortable operating a database in production.
• Your order volume is low enough that a managed plan costs less than a day of engineering a month.
• You need a dozen turnkey marketing integrations today and don’t want to wire any yourself.

Those are real constraints, and a hosted platform is the right answer when they apply. Self-hosting pays off when data ownership, cost at scale, or the ability to modify behavior matters more than offloading operations.

How Wardenclyffe fits

The Wardenclyffe AI Engine is self-host-first by design: a .NET 10 process, three databases you administer, and a full audit log — all on your hardware. It’s source-available under BSL 1.1 and free to run in production under $1M in annual GMV, so a small store owns everything above without paying for the privilege. There is deliberately no multi-tenant hosted plan; the engine is the product, not a service we rent back to you.

If you’d rather not run it alone, the same team that builds the engine also takes on paid implementations — see the studio that maintains the engine for how commercial support and above-the-grant licensing work. Self-hosting doesn’t have to mean self-supporting; it just means the choice is yours.