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 two products that fit together. 86d.store is an MIT-licensed commerce runtime you can download and run today. 86d.app is an optional managed product that provisions and operates that runtime for you. Using the second one never costs you access to the first: your Store’s code and its commerce database stay yours either way.

​
The two products

86d Console is the interface you sign in to for 86d.app. The Control Plane is the authority behind it. The Control Plane can create, deploy, pause, and destroy a managed Store Runtime, and it never becomes a second copy of your catalog, Orders, or Customers. Managed services show up as 86d Cloud and 86d Payments, not the suppliers behind them. See what you see from 86d.

​
Feature, Integration, Module

Three words that sound interchangeable and are not:
  • Feature: something your Store does. Products, Checkout, Loyalty.
  • Integration: something your Store does with an outside company. Stripe, EasyPost, Meta.
  • Module: the package that delivers one of those. This is the word that matters when you are installing, upgrading, or writing code.
A Connection is the configured relationship an Integration uses: which provider, which account, which credentials, and whether it is currently healthy. The repository holds 101 first-party Modules. Being in the catalog says nothing about whether a Module is ready. Browse the Module catalog, then read the page for anything you plan to turn on.

​
What is inside a Store Runtime

Every 86d.store deployment contains the same five things:
  • a Storefront that Shoppers see
  • a Store Admin where you run the Business
  • an active Template that controls layout and content
  • the Modules you enabled
  • one PostgreSQL database holding your commerce data
All of it is in the public repository. You can read it, change it, and run a fork.

​
Two ways to run it

​
Standalone

You host the Store Runtime yourself: your server, your PostgreSQL, your storage bucket, your provider credentials. No 86d Account is involved, and nothing calls home. Start at the Quickstart, then Deployment and hosting.

​
Managed

86d.app provisions an isolated Store Runtime and operates it through 86d Cloud: deployment, domains, upgrades, and one bill. Same runtime, same database ownership, less work. The managed product is still being built. See 86d Cloud plans for the intended offer and what remains unfinished, and Public Beta status for what is open to try right now.

​
The rules 86d holds itself to

These are not aspirations. They are the constraints the code is written against, and they are why some things that look convenient are refused.
  • One authority per fact. Managed-service records live in the Control Plane. Commerce records live in your Store Runtime. Neither copies the other.
  • One Store, one database. Nothing is shared between Stores, so your data stays portable.
  • Named Connections, no silent fallback. A refund goes back through the same provider relationship that took the payment. If that Connection is revoked or unhealthy, the operation stops and asks for attention instead of rerouting.
  • The server decides the money. Checkout recalculates price, tax, Shipping, and availability on the server before it creates an Order. A browser or an agent can propose numbers; it cannot set them.
  • Maturity is earned per capability. Stable describes one tested capability, never a whole repository. See Versioning and maturity.
  • Agents are optional and bounded. Every human interface stays. An agent runs the same Commands you do, under the same rules, with an audit record.

​
Where to go next

Run it locally

A Store Runtime on your machine in a handful of commands.

Understand commerce records

How Cart, Checkout, Order, Payment, Fulfillment, and Shipping relate.

Browse Modules

What each first-party Module does and where its source lives.

Common questions

Hosting, licensing, maturity, agents, and cost.