Multiple brands, one content platform.
You operate three brands with five websites. Each one has its own CMS instance, its own login, its own schema that's almost-but-not-quite the same as the others. Your team wastes hours duplicating content across systems and fixing inconsistencies that shouldn't exist.
The Problem
Sound familiar?
A CMS per brand is unsustainable
Each brand runs its own CMS instance. That means separate schemas to maintain, separate user lists to manage, separate bills to pay. When you need to update the blog layout, you do it five times.
Content doesn't travel between sites
Your company publishes a press release. It needs to appear on three brand sites. Someone copies it into three CMS dashboards, reformats it to match each schema, and prays nothing was lost in translation.
Inconsistent content structures
Brand A's blog post has "author" and "publishDate." Brand B's has "writer" and "date." Brand C calls it "byline" and "posted_at." Same concept, three implementations. Your frontend team maintains three different integrations.
No centralized reporting
How many blog posts did your organization publish last month? Nobody knows without logging into five dashboards and counting manually. There's no single view of your content operations.
How Laizy Helps
Built for this.
All brands under one organization
Each brand gets its own project within your Laizy organization. Full isolation — separate content, separate tokens, separate access controls — but managed from a single dashboard. Switch between brands in the sidebar.
Shared content models
Define your blog post schema once in a .laizy file. Copy it to every brand's project. When you update the schema, update the file and sync. Every brand stays consistent because they share the same source of truth.
Per-site customization
Start with a shared base schema and extend it per brand. Brand A adds a "featured" boolean. Brand B adds a "region" field. The core model stays consistent while each brand customizes what it needs.
Centralized team management
Your content team lead has Owner access across all projects. Writers get Content Editor access to their specific brands. One invitation, one set of credentials, scoped access per project.
Cross-brand content via API
Each project has its own API token. Your corporate site can fetch content from multiple brand projects to build an aggregated newsroom or blog feed. The generated TypeScript client makes this type-safe.
See It In Action
From zero to published content.
Define your schema in code, sync it with one command, and start creating content. The generated TypeScript client gives you full type safety in your frontend.
laizy init— set up your project in secondslaizy sync— push schema changes to the databaselaizy generate— get a typed client for your frontend
# Set up projects for each brand
$ laizy init --project brand-alpha
✓ Created project "brand-alpha"
$ laizy init --project brand-beta
✓ Created project "brand-beta"
# Use the same schema for both
$ cp shared-schemas/blog.laizy laizy/schema.laizy
# Sync both brands
$ laizy sync --project brand-alpha
✓ 3 models synced to brand-alpha
$ laizy sync --project brand-beta
✓ 3 models synced to brand-beta
# Generate clients for both
$ laizy generate --project brand-alpha
✓ TypeScript client ready
$ laizy generate --project brand-beta
✓ TypeScript client readyFive brands. One dashboard. Zero duplication.
Shared schemas keep your content structure consistent. Per-project isolation keeps your content separate. Manage everything from one organization.