Entities as the content layer
Model articles, navigation, catalog copy, and help text as governed multilingual entities rather than through a parallel content API.
Product / Deliver content
Documents
Manage documents, PDFs, messages, files, and multilingual content as governed backend capabilities.
Functions and workflows can render localized templates to PDF, store the generated file, and pass it to email delivery as an attachment.Verified 2026-08-20 · owner GSB Core · evidence ↗
One language context
The selected language is carried on tenant requests and reused for content, template bodies, translated subjects, and workflow output.
Templates bound to data
Reusable HTML templates render from entity, workflow, contact, and parameter data instead of documents assembled in application code.
Your sender identity
The platform provides template storage, rendering, PDF generation, attachment assembly, and delivery logs; the tenant registers and controls its own SMTP or SES credentials.
Operations
Each entry links to its reference page, generated from the same documentation the CLI and the MCP server return.
Keep reading
The guide covers the working shape of this capability, including request payloads, limits, and failure handling.
Rest of the platform
Database ↗
Give AI-assisted teams a governed data model, query layer, and transactional save path instead of a hand-built backend.
Auth ↗
Keep identity, tenancy, and deep permission policies enforced in the backend, not the interface.
Functions ↗
Run business logic inside the tenant runtime without deploying an application server or server farm.
Workflows ↗
Compose durable, inspectable business processes instead of asking generated glue code to hold state.
Assistant ↗
Let coding agents work through CLI and MCP against the same governed backend contract your team controls.