What is the Suite?
Apiome is two applications that share one account, one tenant and one set of projects:
| Application | Where | What you do there |
|---|---|---|
| Apiome — the main app | main.apiome.dev | Sign in, create projects, cut and publish versions, import specs into the catalog, lint, review, browse and export. Documented at docs.apiome.dev |
| The Suite — the studio | suite.apiome.dev | Model a version's schemas and paths on a canvas, write and generate its documentation, and publish it as a portal. Documented here |
The main app's top bar carries a Designer entry whose dropdown lists every Suite surface; its launcher shows Data Designer, Paths, Authoring, Scribe and Slate cards. Each opens the studio on the project and version you were looking at, and the studio's own top bar links back. You sign in once: the session is shared between the two origins (Sign in).
The surfaces
Design — the project version as a model. The workspace shows a version's
classes and paths in one domain-scoped canvas with three lenses (Schemas, Paths, Combined), an
adaptive inspector, a ⌘K palette, comments, try-it against a hosted mock, and an AI assistant. The
classic canvases — the Data Designer at /editor and the Paths editor at
/paths — are the surfaces it unifies, and Code and exports renders the version as
OpenAPI, AsyncAPI, Arazzo, JSON Schema, GraphQL SDL or SQL DDL and lets you edit the source.
Authoring — the project version as documentation. The Authoring Overview is the readiness home: a recommended next action, coverage and delivery signals, a setup checklist from catalog to portal, and a work queue. Scribe writes the reference content — summaries, descriptions, examples — with proposals grounded in the version's source and cited back to it. Guides hold the narrative pages (onboarding, authentication, migration) and the Changelog the reviewed release notes. Slate turns all of it into a portal: theme, navigation, landing-page blocks, preview, build, export, versions and a custom domain. The hosted plan adds the Release Center, edge cache, security, edge functions and insights.
What the Suite is not
The Suite does not own data. Projects, versions, classes, paths and primitives live in the Apiome installation and are read and written through its REST API; authoring content lives in Spire, the Suite's authoring service, in the same database. Cutting a version, publishing it, importing a spec into the catalog, linting and governance stay in the main app — the studio links you there when a task needs it (New project and Import spec on the Suite home open the main app's projects page).
Several surfaces are in preview: Scribe, Slate, Releases and Insights carry a Preview chip in the suite dropdown, and some controls inside them are present but not yet wired. Each page in this guide says so where it applies.