> ## Documentation Index > Fetch the complete documentation index at: https://86d.store/docs/llms.txt > Use this file to discover all available pages before exploring further. # What is 86d? > The two 86d products, the interfaces you will use, and which system owns which facts about your Store. **In development.** 86d is being built in the open. Every capability is Experimental until it earns evidence, so check [maturity levels](/docs/resources/versioning) 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 | Product | What it is | What it owns | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------- | | **86d.store** | The MIT-licensed [Store Runtime](/docs/concepts/architecture): a [Storefront](/docs/concepts/storefront), a [Store Admin](/docs/concepts/admin), your enabled [Modules](/docs/concepts/modules), and a PostgreSQL database | One Store's commerce state | | **86d.app** | The managed product for Store lifecycle, hosting, billing, provider onboarding, and agent access | Managed-service state | [86d Console](/docs/resources/glossary#86d-console) is the interface you sign in to for 86d.app. The [Control Plane](/docs/concepts/architecture) 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](/docs/concepts/commerce-model), or [Customers](/docs/modules/customers). Managed services show up as 86d Cloud and 86d Payments, not the suppliers behind them. See [what you see from 86d](/docs/concepts/architecture#what-you-see-from-86d). ## Feature, Integration, Module Three words that sound interchangeable and are not: * **[Feature](/docs/resources/glossary#feature)**: something your Store does. Products, Checkout, Loyalty. * **[Integration](/docs/concepts/connections)**: something your Store does with an outside company. Stripe, EasyPost, Meta. * **[Module](/docs/concepts/modules)**: the package that delivers one of those. This is the word that matters when you are installing, upgrading, or writing code. A [Connection](/docs/concepts/connections) 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](/docs/modules/overview), 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](/docs/concepts/storefront) that Shoppers see * a [Store Admin](/docs/concepts/admin) where you run the Business * an active [Template](/docs/concepts/templates) that controls layout and content * the Modules you enabled * one PostgreSQL database holding your commerce data All of it is in the [public repository](https://github.com/86d-store/86d). 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](/docs/resources/glossary#86d-account) is involved, and nothing calls home. Start at the [Quickstart](/docs/quickstart), then [Deployment and hosting](/docs/deployment). ### Managed 86d.app provisions an isolated Store Runtime and operates it through [86d Cloud](/docs/resources/glossary#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](/docs/resources/cloud-plans) for the intended offer and what remains unfinished, and [Public Beta status](/docs/resources/public-beta) 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](/docs/concepts/commerce-model) 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](/docs/resources/versioning). * **Agents are optional and bounded.** Every human interface stays. An agent runs the same [Commands](/docs/concepts/agentic-design) you do, under the same rules, with an audit record. ## Where to go next A Store Runtime on your machine in a handful of commands. How Cart, Checkout, Order, Payment, Fulfillment, and Shipping relate. What each first-party Module does and where its source lives. Hosting, licensing, maturity, agents, and cost. ## Related pages * [How 86d separates product authority](/docs/concepts/architecture) * [How commerce records relate](/docs/concepts/commerce-model) * [How Connections route provider work](/docs/concepts/connections) * [How agents work with 86d](/docs/concepts/agentic-design) * [Glossary](/docs/resources/glossary) * [Versioning and maturity](/docs/resources/versioning)