Skip to main content
In development. 86d is being built in the open. Every capability is Experimental until it earns evidence, so check maturity levels before you rely on anything here.
86d is a commerce product you own. The Store Runtime is MIT-licensed and runs on your infrastructure with your database, so the code and the commerce data stay yours. 86d.app is the optional managed product that provisions and operates that same runtime for you when you would rather not. Creating a Store is the first hour. Operating one is every hour after, and that is the part 86d is built for: repricing, restocking, running a promotion, issuing a refund, reconciling a discrepancy. You can do that work yourself in Store Admin, or delegate it to an agent that has to show you a Change Set before anything lands. These pages are written for two readers. If you run a Store, start with what a capability does and what you have to decide. If you are an agent acting on a Store, the exact contract is under each of those sections: options, endpoints, request and response shapes, and what happens when something fails.

Quickstart

Get a Store Runtime on your machine with the CLI or Docker Compose.

Deploy it

Railway, Vercel with Neon, or your own Docker host.

Module catalog

101 first-party Modules, each with its own maturity.

CLI reference

Scaffold Modules, switch Templates, run code generation.

What is 86d?

The two products, the interfaces, and who owns which facts.

86d Cloud plans

What the managed offer costs and what is still in development.

​
How a Store fits together

A Store Runtime is a Bun and Next.js monorepo built from composable Modules. A Module can add API endpoints, Store Admin pages, and Storefront components. You enable the ones you want in your active Template, regenerate, and use the components in MDX.
1

Install and initialize

Install the 86d CLI, then run 86d init. It writes your environment file, installs dependencies, runs migrations, and seeds demo data with Store Admin credentials.
2

Choose your Modules

Edit the modules array in your active Template’s config.json. First-party Modules live in the same repository you cloned. Treat external code as an advanced opt-in and read it before you install it.
3

Regenerate

86d generate rewrites the Module imports and the API router. Every enabled Module’s components become available in MDX with no import statement.
4

Customize and deploy

Edit the Template’s MDX to control layout and content, then push to Railway, Vercel, or any Docker host.

​
What you get

Commerce as separate parts

Products, Cart, Checkout, and Loyalty are independent Modules. Turn off what you do not sell.

Storefront in MDX

Layout and content are MDX files. Module components drop in without imports.

Sell in more places

Marketplaces, product feeds, and social channels. Sync depth differs by Integration, and each page says which.

Take payments

Bring your own processor through an Integration, or wait for 86d Payments. Both are documented.

Your database, your data

One PostgreSQL database per Store. You can read it, back it up, and take it with you.

MIT licensed

Read the code, fork it, ship it. No key, no phone home, no account required.
If an AI assistant is doing the work, point it at the Docs MCP server so it searches these pages instead of guessing. Tell it to read the whole page before it changes anything in a Store.

​
Where to go next