> ## 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. # Common questions > Short answers about licensing, cost, hosting, maturity, Modules, payments, and what agents can and cannot do. **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. ## Can I run a real store on this? Not yet, and not as a general claim about the product. Every capability earns [Stable](/docs/resources/glossary#capability-maturity) on its own, through its contract, its failure behavior, its tests, its documentation, and production evidence. None has. See [Public Beta status](/docs/resources/public-beta) and [Versioning and maturity](/docs/resources/versioning). ## What is the difference between 86d.store and 86d.app? **86d.store** is the open-source [Store Runtime](/docs/concepts/architecture): a [Storefront](/docs/concepts/storefront), a [Store Admin](/docs/concepts/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](/docs/resources/glossary#86d-console) is the interface you sign in to. The [Control Plane](/docs/concepts/architecture) is the authority behind it. See [What is 86d?](/docs/introduction). ## What is the license? 86d.store, including all 101 first-party [Modules](/docs/concepts/modules), is [MIT-licensed](https://github.com/86d-store/86d/blob/main/LICENSE). 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](/docs/resources/cloud-plans) is the managed option: a planned 30-day trial with $5 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](/docs/resources/glossary#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](/docs/deployment). ## 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](/docs/concepts/architecture#one-store-one-database). ## Feature, Integration, Module, Connection: what is the difference? * A **[Feature](/docs/resources/glossary#feature)** is something your Store does. * An **[Integration](/docs/concepts/connections)** is something your Store does with an outside company. * A **[Module](/docs/concepts/modules)** is the package that delivers either one. * A **[Connection](/docs/concepts/connections)** 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](/docs/modules/overview). ## 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](/docs/concepts/modules) 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](/docs/resources/glossary#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](/docs/guides/payment-integrations). ## Can an agent run my Store? Not yet. The [Docs MCP server](/docs/resources/mcp) 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](/docs/concepts/agentic-design). ## 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](/docs/resources/versioning) and the [changelog](/docs/resources/changelog). ## Where do I report something broken? Ordinary bugs go to [GitHub Issues](https://github.com/86d-store/86d/issues). Anything security-relevant goes privately through [GitHub Security Advisories](https://github.com/86d-store/86d/security/advisories), not a public issue. ## How do I contribute? [Contributing](/docs/resources/contributing) covers the workflow, the health gates, and the bar for a pull request. ## Related pages * [Glossary](/docs/resources/glossary) * [Versioning and maturity](/docs/resources/versioning) * [Deployment and hosting](/docs/deployment) * [How 86d separates product authority](/docs/concepts/architecture) * [What is 86d?](/docs/introduction) * [How agents work with 86d](/docs/concepts/agentic-design)