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.

​
Can I run a real store on this?

Not yet, and not as a general claim about the product. Every capability earns Stable on its own, through its contract, its failure behavior, its tests, its documentation, and production evidence. None has. See Public Beta status and Versioning and maturity.

​
What is the difference between 86d.store and 86d.app?

86d.store is the open-source Store Runtime: a Storefront, a Store Admin, your Features and Integrations, and one Store’s commerce data. You run it. 86d.app is the optional managed product that runs it for you, plus billing, provider onboarding, and agent access. 86d Console is the interface you sign in to. The Control Plane is the authority behind it. See What is 86d?.

​
What is the license?

86d.store, including all 101 first-party Modules, is MIT-licensed. Use it, change it, host it, sell what it sells, fork it. 86d.app is a separate proprietary service you can ignore entirely.

​
What does it cost?

Self-hosting costs you nothing in license fees. You pay for your own server, database, and providers, the same as any software you run. 86d Cloud is the managed option: a planned 30-day trial with 5credit,thenLaunchat5 credit, then Launch at 1 per Active Store per month for twelve months, or Premium at $20 per Active Store per month, plus metered infrastructure and services. Enterprise is negotiated. That offer is not activatable yet.

​
Can I run it without an 86d account?

Yes. A standalone Store Runtime reads local configuration, uses infrastructure and credentials you control, and never calls 86d. No 86d Account is involved.

​
Where can I host it?

Anywhere that runs a Next.js application and PostgreSQL. These docs cover Docker Compose, Railway, and Vercel with Neon. See Deployment and hosting.

​
Can two Stores share a deployment or a database?

No, and this is a hard boundary rather than a recommendation. One Store Runtime, one commerce database, per Store. That is what keeps your data portable and one Store’s problem from becoming another’s. See Store isolation.

​
Feature, Integration, Module, Connection: what is the difference?

  • A Feature is something your Store does.
  • An Integration is something your Store does with an outside company.
  • A Module is the package that delivers either one.
  • A Connection is the specific provider account an Integration is configured to use.

​
Does everything in the catalog work?

No. The catalog is a list of packages, not a list of promises. Every entry is currently Experimental with no recorded evidence. Read the Module’s page, its source, its tests, and how it behaves when a provider is down before you enable it. See the Module catalog.

​
Can I use something other than PostgreSQL?

Not with a supported adapter today. The Store Runtime uses Drizzle and PostgreSQL.

​
How do payments work right now?

You bring your own Stripe, PayPal, Square, or Braintree account, and the Module for it connects that account to your Store. 86d charges you nothing per Checkout on this model, and it is sandbox-only for now. 86d Payments, where 86d handles onboarding and settlement at one all-in rate, is a separate thing that does not exist yet. See Set up a payment provider.

​
Can an agent run my Store?

Not yet. The Docs MCP server is read-only: it searches and reads these pages and cannot see or change a Store. Authorized product operations through Remote OAuth MCP are still being built. See How agents work with 86d.

​
How do I update?

Read the release and migration notes first, then update dependencies, run migrations, regenerate, and run the health checks before you deploy anything. See Versioning and maturity and the changelog.

​
Where do I report something broken?

Ordinary bugs go to GitHub Issues. Anything security-relevant goes privately through GitHub Security Advisories, not a public issue.

​
How do I contribute?

Contributing covers the workflow, the health gates, and the bar for a pull request.