Principle
Spec-driven layout
Site specs decide page composition, variants, and theme presets without turning Payload into a design system.
Wenaro
Multi-tenant website platform
Combined renderer, CMS, and platform ops
Build structured client websites without rebuilding the stack every time.
Wenaro separates site composition from client-managed content so one platform can power many brochure sites and simple blogs.
One codebase for many sites.
Payload auth with tenant-scoped access.
Supabase-backed runtime and storage.
Brochure pages and simple blogs in the same model.
Platform view
One dashboard, many site behaviors
v1 baseline
Site spec
Theme preset: earth-warm
Page spec: hero / gallery / contact
Tenant host: coolblogs.wenaro.com
Content
Payload collections per section type
Site-scoped media uploads
Blog posts filtered by tenant
Runtime path
Host resolution · site spec · Payload content · cached render
no snapshots yet
Principle
Payload for content
Clients edit text, media, and posts in one scoped admin. Platform operators keep structural control.
Principle
Multi-tenant by host
Tenant subdomains and custom domains resolve through one app with site-level isolation and cache tags.
Operating model
Keep design, content, and host routing disciplined from the start.
The platform becomes maintainable when each responsibility is narrow: site specs for composition, Payload for content, and host-based resolution for tenancy.
Spec
Control composition without hardcoding every client site
Use site specs for structure, variants, and theme presets. Keep design decisions outside CMS content tables.
Content
Let clients edit content without touching structural logic
Payload collections stay fixed. Tenants only see their own content and media, tied to their site and sections.
Runtime
Serve different sites from one deployment
Hosts resolve to tenants, content loads through Payload Local API, and the renderer stays fast through cache tags.
Domain model
One product site, many tenant sites, one deployment surface.
`wenaro.com` stays the product site. Tenant traffic resolves from platform subdomains or explicit custom domains without forcing the product site through the tenant renderer.
Marketing
wenaro.com
Marketing
Custom Next.js landing page for the Wenaro product itself.
Tenant
coolblogs.wenaro.com
Tenant
Automatic platform subdomain based on site slug.
Custom domain
coolblogs.com
Custom domain
Explicit domain mapping for production client traffic.
Next