SettingsSandbox

Settings

Your workspace, how your brand should sound, and who signs off on what.

Workspace

Injected into every AI node through the Product Context node.

Approval policy

Require human approval before publishinglocked

Not configurable. Chronomial has no auto-publish path.

Require a second approver on claims about customers

Case-study quotes route to a second reviewer.

Notify Slack when a run parks for review

#marketing

Email a daily digest of pending approvals

Gmail is not connected yet.

Team

4
MR
Maya Restrepo
Founder & CEO
member
PN
Priya Nandakumar
Head of Growth
member
DP
Devon Pryce
Content Lead
member
CA
Chronomial AI
Automated
service account

Sandbox vs local app

Registered node types22
Channel adapters built5 of 8
ExecutionIn-browser engine, simulated latency
ServerNone. Everything runs in your browser
Outbound requestsNone beyond this origin
PersistenceIn-memory; a refresh resets the sandbox
PublishingMocked, idempotency enforced
Research + modelsMocked behind provider-neutral seams

You are looking at the hosted sandbox. It has no backend and no stored credentials, makes no third-party requests, and runs every broadcast in your own browser against demo data. Clipboard, per-channel previews and opening a platform composer are fully real; research, model calls and publishing are simulated.

The real Chronomial is installed and run locally, so your research, model keys and channel account access never leave it. Same steps, same canvas, same everything you see here. The only difference is that the research and the posting are real.