One workspace for every brand you run
No charge until the trial ends. Cancel any time before then.
What running four brands actually costs
Not the licence fee. The overhead that shows up once the second property is live.
A separate CMS subscription per brand
Each new property arrives with its own plan, its own invoice, and its own renewal date. Nobody can answer what content management costs in total without opening four billing portals.
Editors who need a developer to change anything
A headline, a price, a landing page for next week. Each one becomes a ticket, and the people who own the words wait on the people who own the deploy.
No single view of who published what
Every property has its own login and its own history, so there is no one place to see what went live this week across the brands you are responsible for.
Workspace, Projects, Buckets
Three levels, each holding the one below it. This is the whole model, and it is why adding a brand does not mean adding a subscription.
Marketing site
www.brand.com
Newsroom
news.brand.com
Japan
brand.jp
Three brands, five Buckets, one invoice. Add the fourth brand as another Project inside the same Workspace rather than another subscription.
- 1
Workspace
The account everything else lives inside.
- One bill
- One team roster
- Pooled usage and limits
- 2
Project
One per brand, property, or client.
- Its own Buckets
- Its own agents
- Per-project access
- 3
Bucket
Where the content and media actually sit.
- Object types and Objects
- Media library
- Usually one per environment
Buckets, agents and workflows are pooled across the Workspace rather than fixed per Project, so you hand more of the allowance to the brand that needs it. One team roster spans every Project. See how teams run multiple sites
One team, scoped per brand
Select a person to see what they can reach in the Workspace above. A Workspace Admin inherits every Project. A freelancer can be limited to a single Object type.
| Team member | Workspace | Marketing site | Newsroom | Japan |
|---|---|---|---|---|
 Maya ChenVP of Content | Admin | Adminvia Workspace | Adminvia Workspace | Adminvia Workspace |
 James OkonkwoMarketing lead | User | Admin | - | - |
 Priya ShahStaff editor | User | EditorProduction | EditorProduction | - |
 Alex RiveraFreelance writer | User | ContributorBlog on Production | - | - |
Maya is a Workspace Admin, so she has Admin access to every Project and Bucket without being added to each one. She is the only person here who can change billing.
Small or Large
Both plans start with a 30-day free trial, and nothing is charged until it ends. The difference is how much of everything you get.
Small Workspace
30-day free trialSeveral projects, one team, one bill.
Includes
- 10 team members
- 5 Projects
- 10 Buckets
- 25 agents
- 50 workflows
Large Workspace
30-day free trialFor larger teams running many projects.
Everything in Small Workspace, plus
- 30 team members
- 10 Projects
- 30 Buckets
- 75 agents
- 150 workflows
- SAML single sign-on
| Pooled across the Workspace | Small Workspace | Large Workspace |
|---|---|---|
| Projects | 5 | 10 |
| Buckets | 10 | 30 |
| Comments | Included | Included |
| Extensions | Unlimited | Unlimited |
| AI agents | 25 | 75 |
| AI workflows | 50 | 150 |
| Team members | 10 | 30 |
| Roles and permissions | All 4 roles | All 4 roles |
| Audit log | Included | Included |
| Audit log retention | 365 days | 365 days |
| Single sign-on (SAML) | — | Included |
| SCIM provisioning | — | Coming soon |
| Free trial | 30 days | 30 days |
Objects, API requests, media and AI tokens are metered on top of these. See every limit and rate on the pricing page
Built for the people doing the publishing
What a content ops lead needs when twenty editors share a calendar across four brands.
- Access that matches your org chart
- Admins, Managers and Users at the Workspace level decide who sees which brands. Inside a Bucket, four roles go finer, and a contributor can be scoped to specific Object types, so a freelancer sees the blog and nothing else.Roles and permissions
- A record of who did what
- Every Project in the Workspace writes to one audit log: sign-ins, role changes, key rotations, billing changes and deletions, filterable by person, action or date. Entries are append-only, so nobody can tidy up after themselves, including us. Agent actions are recorded under the agent name.Audit log
- Drafts and revision history
- Editors work on a draft without touching what is live, and every save is a revision you can read and restore. Useful when a campaign page gets edited by four people the morning it ships.Revisions
- Comments where the content is
- Review happens on the Object itself instead of in a thread in another tool, so the feedback and the paragraph it refers to stay together.Comments
- Scheduled publishing and unpublishing
- Set a publish time and an expiry on any Object. Embargoed announcements go live on their own, and a promotion comes down without anyone remembering to take it down.publish_at and unpublish_at
- Every locale in the same model
- Translations live on the same Object as the source, so a Japanese page is a locale of the article rather than a second CMS. All locale versions of an Object count as one against your limit.Localization
One agent per brand, plus shared workflows
A Large Workspace carries 75 agents and 150 workflows, pooled across every Project. That is enough to give each brand its own agent that knows its voice and its content, and still have workflows that run across all of them.
An agent that belongs to one brand
Agents live at the Project level, so an agent only reaches the content in its own brand. Reachable from Slack, WhatsApp or Telegram, where the team already is.
Workflows that span all of them
Chain steps across brands on a schedule: audit which properties are missing this week's post, translate what shipped, then report once. Steps inside a workflow do not count against your agent allowance.
A ceiling on automated spend
Agents draw on the Workspace token allowance and cannot spend past it without a top-up you buy deliberately.
Add-ons apply Workspace-wide
Bought once on the Workspace, each of these applies across every Project in it rather than per Project, so you are not adding Localization four times for four brands.
Webhooks
Automated notifications when content is published, updated or deleted.
Localization
Create and manage content in multiple languages.
Revision History
Track and restore previous versions of your content.
Automatic Backups
Automatically back up your content to prevent data loss.
Webhooks, Localization, Revision History, Automatic Backups, across every Project in the Workspace. Compare with per-Project pricing
Frequently asked questions
Put every brand in one Workspace
Start the trial and move your first Project in, or walk us through what you are running today and we will tell you which plan fits.
Still deciding? Compare every plan or read about Enterprise.