TenantOS

The stack, from bottom to top:

• Platform: the shared application code. Next.js, components, layouts, the config authority pattern, the deployment pipeline.
• Tenant: the configuration boundary. Identity, brand, navigation, contact, voice. One versioned JSON authority per tenant.
• Site: the tenant's site structure: routes, information architecture, sitemap.
• Brand: design tokens. Re-skinning means changing token values, never component code.
• Content: pages, posts, documentation. Markdown-first, tenant-owned.
• Assets: media, with provenance and licensing per tenant.
• Domain: the tenant's canonical URL, assigned at the platform edge.
• Integrations: per-tenant connections (email, social, analytics), configured not coded.
• Agent capabilities: what agents may do on behalf of this tenant, as configuration.

Every architectural decision on this site is checked against one question: could Tenant B use this without forking the application? If the answer requires copying the repo and editing code, the decision is wrong for the platform, even if it works for this tenant.

The preferred path is always: tenant to configuration to content to branding to domain to integrations. The forbidden path is: copy repo, edit code, deploy. The second path is how every multi-tenant codebase rots into N unmaintainable forks.

This site, the first tenant, demonstrates the separable layers:

• PING identity lives in tenant.ping.v1.json, not in component code. Components read it through a typed loader.
• Brand is design tokens. The same components render a different brand when the token values change.
• Navigation, SEO defaults, contact info, and provenance all resolve from the tenant authority.
• The deployment path (git to preview to production) is tenant-independent.

What it does not yet prove: onboarding Tenant B end to end, per-tenant domains at the edge, and per-tenant integrations. Those are future work, and this page will say so until they exist.

To avoid confusion:

• It is not a product you can buy today. There is no signup, no pricing, no dashboard.
• It is not a website builder. Tenants are real codebases with real configuration, not templates with a theme picker.
• It is not finished. It is a direction with one working proof point, and the proof point is this site.