diff --git a/AGENTS.md b/AGENTS.md index 5b098208..dac7e55f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -19,7 +19,7 @@ Assume every commit and every line of history will be public. - Do not add navigation to a section until that section has a real page or generated source. - Authored navigation comes from `content/**` and its `meta.ts` files. - `blume.config.ts` defines the Docs, CLI, API, Agents, and Platforms tabs. + `blume.config.ts` defines the Docs, CLI, API, Agents, and Spacefast for Platforms tabs. `bun run verify:routes` checks every authored route against the built output. - Route policy: one page per task, not one page per toggle; a page lives in one primary place and is cross-linked elsewhere. Authored URLs may move freely diff --git a/README.md b/README.md index 1e80237d..d4f68073 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ # Spacefast Docs The documentation site for [Spacefast](https://spacefast.com/docs/). Guides live -in `content/`, organized into Docs, CLI, API, Agents, and Platforms tabs. Everything under +in `content/`, organized into Docs, CLI, API, Agents, and Spacefast for Platforms tabs. Everything under `generated/` is a verified snapshot — don't edit it by hand. ## Development diff --git a/blume.config.ts b/blume.config.ts index c8403896..706e1557 100644 --- a/blume.config.ts +++ b/blume.config.ts @@ -126,7 +126,7 @@ export default defineConfig({ { label: "CLI", path: "/cli", icon: icons.terminal }, { label: "API", path: "/api", icon: icons.braces }, { label: "Agents", path: "/agents", icon: icons.robot }, - { label: "Platforms", path: "/platforms", icon: icons.handshake }, + { label: "Spacefast for Platforms", path: "/platforms", icon: icons.handshake }, ], }, reference: [ diff --git a/content/index.mdx b/content/index.mdx index ad28ebb5..c639e771 100644 --- a/content/index.mdx +++ b/content/index.mdx @@ -77,4 +77,4 @@ In a self-serve account, your team owns the Spaces you claim, even when you are ## Next steps -Have an exported page already? [Share a Claude artifact publicly](/agents/share-claude-artifact). Building publishing into another product? Start with [Platforms](/platforms). +Have an exported page already? [Share a Claude artifact publicly](/agents/share-claude-artifact). Building publishing into another product? Start with [Spacefast for Platforms](/platforms). diff --git a/content/platforms/index.mdx b/content/platforms/index.mdx index 0cd0fac2..de5138c7 100644 --- a/content/platforms/index.mdx +++ b/content/platforms/index.mdx @@ -1,52 +1,56 @@ --- -title: Platforms -description: Offer hosting under your own brand. Spacefast runs the infra, and your product keeps the customer, the pricing, and the relationship. +title: Spacefast for Platforms +description: Sell Spacefast infrastructure under your own brand. You keep the customer, the pricing, and the relationship. --- -Spacefast Platforms is for companies that sell hosting as part of their own product: hosting companies, domain registrars, agencies, and organizations that run many sites. Spacefast runs the infra. Your customers see your brand, your pricing, and your dashboard. +Spacefast for Platforms is for web hosts, domain registrars, agencies, and any organization that runs a lot of sites. You put Spacefast infrastructure inside your own product. Customers see your brand, your prices, and your dashboard, and you don't run any servers. -Platforms is part of WP Cloud, the platform hosting companies use to power their own WordPress hosting products. It runs on the same infra as Automattic, WP Cloud, Pressable, and WordPress.com. The [Partner API](/platforms/partner-api) extends it to the sites and apps your customers build with agents. +It's part of WP Cloud (the infrastructure that runs WordPress.com, Pressable, and more). Web hosts already use WP Cloud to sell WordPress under their own names. The [Partner API](/platforms/partner-api) adds the sites and apps your customers build with agents. + + + Tell us what you want to sell and who you sell it to. We'll set up your partner account. + ## Who it's for -| You are | What Platforms gives you | +| You are | What you get | | --- | --- | -| A hosting company | Managed publishing and hosting for your customers, without running servers or a control panel | -| A domain registrar | A live site at the point of registration, with no infrastructure to build | -| An agency or reseller | One integration for every client site, billed and branded as your own | -| An organization with many sites | Sites provisioned from code for each team, with one account over all of them | +| A web host | Sites and apps for your customers, without running servers or building a control panel | +| A domain registrar | A live site for each new domain, right at registration | +| An agency or reseller | One integration for every client site, billed and branded as yours | +| An organization with many sites | A site for each team, created from code, all under one account | ## What you control -- **Your brand.** Set your name, logo, support links, and error docs once. Claims and access handoffs land on your own portal. -- **Your customers.** Each customer is an ID from your own system. Spacefast creates them on first use, with no separate signup. -- **Your pricing.** Declare plans with their own features and quotas. Read usage records per customer and bill however you want. -- **Your domains.** Serve customer sites from your own hostname, and put the API behind your own origin. -- **Your UX.** Everything is API-first. Build your own interface, or give customers scoped tokens and let their apps call Spacefast directly. +- **Brand.** Set your name, logo, support links, and error docs once. When customers claim a site or get access to one, they land on your portal. +- **Customers.** Each customer is an ID from your own system. Spacefast creates the customer the first time you use that ID, so there's no separate signup. +- **Pricing.** Define plans with their own features and quotas. Read each customer's usage records and bill them however you like. +- **Domains.** Serve customer sites from your own hostname, and put the API behind your own origin. +- **Interface.** Everything is API-first. Build your own interface, or give customers scoped tokens so their apps call Spacefast directly. -## What Spacefast runs +## What Spacefast handles -Publishing, builds, versions and rollbacks, custom domains and certificates, and CDN and caching. Customer sites get the same serving path as every other Space. +Publishing, builds, versions and rollbacks, custom domains and certificates, and the CDN and cache. Spacefast serves your customers' sites the same way it serves every other Space. ## How integration works -1. **Get partner access.** Your account gets a live tenant and a linked test tenant. The test tenant simulates provisioning and is metered at zero. -2. **Create customer Spaces.** Publish for a customer with a tenant API key and their ID. See the [Partner API quickstart](/platforms/partner-api). -3. **Configure your account.** Branding, signing keys, plans, event subscriptions, and hostnames live in one [system Space](/platforms/partner-api/configuration). -4. **Hand customers access.** Issue [customer JWTs](/platforms/partner-api/tokens) scoped to one customer. -5. **Go live.** Exercise failures in test mode, then [promote your configuration](/platforms/partner-api/go-live) to the live tenant. +1. **Get partner access.** Your account gets a live tenant and a linked test tenant. Provisioning on the test tenant is simulated, and its usage costs nothing. +2. **Create customer Spaces.** Publish for a customer with a tenant API key and the customer's ID. See the [Partner API quickstart](/platforms/partner-api). +3. **Configure your account.** Branding, signing keys, plans, event subscriptions, and hostnames all live in one [system Space](/platforms/partner-api/configuration). +4. **Give customers access.** Issue [customer JWTs](/platforms/partner-api/tokens), each scoped to one customer. +5. **Go live.** Try the failure cases in test mode, then [promote your configuration](/platforms/partner-api/go-live) to the live tenant. Create your first customer Space with a tenant API key. - Every tenant, customer, and usage operation with its schemas. + Every tenant, customer, and usage operation, with schemas. Plans, suspension, and the usage records you bill from. - Test failure handling, then promote configuration to live. + Test failure handling, then promote your configuration to live. diff --git a/content/platforms/meta.ts b/content/platforms/meta.ts index d88c77b1..9b4e3e6b 100644 --- a/content/platforms/meta.ts +++ b/content/platforms/meta.ts @@ -1,6 +1,6 @@ import { defineMeta } from "blume"; export default defineMeta({ - title: "Platforms", + title: "Spacefast for Platforms", pages: ["index", "partner-api"], });