The Name
The Name is the identity and ownership anchor; domain and public Nameplate bind every room.
Built for accountable production
cerilo brings identity, site, mail, posts, assists, press kit, and deals behind a domain the creator owns, with scheduled publishing, receipts, and an MCP-first operating surface.
Repository-backed product facts · reviewed 26 August 2026
Replace a scattered creator stack with one inspectable record while keeping the Name, exports, approvals, and deal history under the creator’s authority.
The Name is the identity and ownership anchor; domain and public Nameplate bind every room.
Seven rooms share one workspace record: Nameplate, Site, Mail, Posts, Assists, Press kit, and Deals.
A durable scheduler and adapter boundary press approved content to channels and record receipts.
Expand the matrix. Choose by boundary and workflow, not slogans.
| This system | Alternative · Buffer | |
|---|---|---|
| Primary job | Creator identity, site, mail, posts, press kit, and deals under one Name | Social content planning, publishing, analytics, and engagement |
| Deployment boundary | Domain-first managed workspace with MCP and Firebase scheduler | Managed social media platform |
| Evidence model | Durable job state, adapter result, and publishing receipts | Published-post history and analytics; verify export details |
| Operator control | Creator domain ownership, approval, token budgets, and handback | Workspace roles and connected-channel permissions |
| Integration surface | Web rooms, API, scheduler, MCP, channel adapters | Web/mobile app, browser extension, APIs, channel integrations |
Solo
One Name and every room for the working creator.
Studio
Collaborators, approval, deal workflow, and priority support under one Name.
Label
Up to ten Names with cross-Name operations and a named contact.
Current status. cerilo is pre-launch. Local emulator journeys exercise registration, scheduling, rollback, lead capture, provider governance, and storage; there is no public user base or production performance claim.
Start with the architecture, reproduce the documented workflow, and verify the boundary against your own threat model.
No. Mutable vendor pricing is deliberately excluded. Verify current vendor terms before a purchase decision.
The status note, architecture page, and engineering articles state the current boundary and failure behaviour.