Publisher-native content types, an event-driven workflow library, and a shared specialist roster (researcher, fact-checker, copy editor, SEO, translator, voice modeler) at the same monthly per-assistant price as Actium.
Blog post, newsletter issue, product update, event recap, photo essay, podcast episode, interview. Every type ships with the schema fields editors expect, the rendering hints the channel needs, and the workflow hooks that fit publisher process.
Draft saved, review requested, fact-check complete, scheduled, published, syndicated. Each workflow chains specialist roles to events; you build the pipeline once and it runs every issue.
Hire-an-assistant pricing. Studio surfaces content-facing specialists; ops teams can use the same platform for ops-facing roles. One bench, two surfaces.
A blog post draft is saved. Workflows fire on the content.draft.saved event, dispatch specialists, and gate the path to publish.
Published pages render once into R2 + KV + Cache API. Workers handle every request from the closest PoP. No origin hit on read; no DB query per visitor.
Cloudflare Workers serve every read. HTMLRewriter injects nav, meta tags, OpenGraph, schema.org JSON-LD at request time when needed; otherwise pure static.
Rendered HTML in R2; routing rules and per-tenant config in KV. Cache API absorbs steady-state load. Sub-50ms TTFB globally.
Drizzle on Cloud SQL Postgres for the editorial side. The edge serves readers; the origin serves authors.
Early access is open. Pricing is per content volume, with the specialist bench priced per assistant per month. Same as Actium.