Skip to main content
Experimental. All 101 entries currently publish as Experimental with no recorded evidence. Being in this catalog says nothing about whether a Module works. See maturity levels.
Your Store does what the Modules you enabled make it do. Everything below is first-party, MIT-licensed, and already sitting in the repository you cloned. Nothing is on until you turn it on, and a Module you never enable adds no routes, no tables, and no attack surface. Pick from the groups below, read the page for anything you plan to keep, then list it in config.json and regenerate. The machine-readable list, with pinned commits and integrity hashes, is the registry manifest.

​
Installing one

Use the CLI:
The CLI downloads the Module, installs its dependencies, and enables it in your active Template. Editing config.json by hand does the same thing. Either way, run 86d generate or its endpoints and Storefront components will not exist. Every entry needs its exact package name in modules, plus the versioned Experimental opt-in. A "*" wildcard, or no modules field at all, admits nothing. See turning on an Experimental Module. Managed provisioning admits a curated default set without promoting those Modules past Experimental. Maturity still comes from registry evidence, not from being included at provision.

​
The catalog

Everything about what you sell.
From browsing to a placed Order.
Accounts, preferences, and the things that bring people back.
Getting it to the buyer, and taking it back.
Finding customers and keeping them.
Pages, posts, and everything you write.
Money inside your Store. Your 86d Cloud bill is separate from all of it.
Connect merchant-owned provider accounts to the Store Runtime. These modules are distinct from 86d Payments.
Selling somewhere other than your own Storefront.
The back office.