Using Typeroll Cloud

Typeroll Cloud is the managed service for Typeroll CMS. You use the browser editor and API while Typeroll operates the CMS infrastructure. The shared Cloud and self-hosting guide explains which instructions apply to each option.

Typeroll Cloud is in beta with open registration. This guide describes the current workflows; it does not promise plan limits or general availability.

Create your account and workspace

In Core 0.2.77 or later, choose Sign up on the sign-in page and enter your name, email and a password of at least 12 characters. Your personal account is separate from an Organization. The next screen lets you name your Organization (your company, project or your own name) or join an existing one with an invitation. You do not need a separate company name field at signup. Invitation links remain attached while you sign in or create an account.

A link to /login?mode=signup, such as app.typeroll.com/login?mode=signup, opens account creation directly (Core 0.2.86 or later).

Sign in with email and password. If you previously used Google, choose Forgot password? with the same email address to set a password for that account. Do not create a second account. The reset message does not confirm whether an address is registered. If sign-in reports too many attempts, wait before retrying. Older portal releases may still show the Google button.

Confirm your email address

In Core releases after 0.2.84, every account confirms its email address before it can do anything else. After you sign up, Typeroll sends a confirmation link and shows Check your email. Open the link: the page checks with Typeroll and continues by itself once the address is confirmed, also when you open the link on another device. If the message does not arrive, check your spam folder and choose Resend confirmation email; resending is limited to a few messages every ten minutes.

Until your address is confirmed you cannot create or join an Organization, accept an invitation, open a Site, create or use API keys or connect an AI tool. An invitation or MCP connection link you opened is kept and continues after confirmation. Existing accounts with an unconfirmed address see the same page the next time they open the portal; their Organization memberships are kept and work again once the address is confirmed.

Continue with GitHub

When Continue with GitHub is shown, you can sign in with your GitHub account instead of a password. Typeroll asks GitHub only for your email address and public profile, never for repository access. GitHub addresses are not confirmed for Typeroll, so a new GitHub sign-in also confirms its email address on the Check your email page.

If your GitHub email address already has a Typeroll password account, the sign-in page asks for that password and then links GitHub to the same account. If you used Google before, choose Forgot password? first.

Signing in with GitHub does not connect GitHub for publishing. Publishing uses the Organization’s GitHub connection, which an owner or admin sets up under publishing accounts with their own GitHub permissions.

Open your Organization

Sign in at app.typeroll.com. Open the sidebar and select the Organization, then the Site you want to work on. On mobile, open the menu first. Your access can differ between Organizations and Sites; changing the selection does not grant additional permissions.

An Organization holds shared connections, media and build settings. A Site holds its content, versions and website settings. Hosting Groups let an Organization use additional Cloudflare hosting accounts without creating more Organizations.

Edit before you connect publishing

Follow Your first site to create a Site and edit its pages. You can save content and use expiring previews before connecting GitHub, Cloudflare or domains. Publishing remains locked until setup is ready.

Content editors can use the visual editor and save/review workflow. Organization owners or admins handle the shared publishing connections. Public deployment and domain changes require the relevant admin permission.

Ask the built-in AI assistant

Open your Site and choose AI Chat in the sidebar. Describe the content change you want: shorten an introduction, update a headline or improve a page’s meta description. The assistant can make changes within your access permissions. Review the affected pages and preview the result before publishing.

This is separate from connecting your own development agent. Editors can use the built-in assistant in the browser without installing an MCP client or a local development environment. AI edits still use the normal saving and publication workflow; a chat response is not evidence that a change has been deployed.

The assistant uses your Organization’s own Anthropic API key; Typeroll Cloud has no platform AI key. Starting with the Core release that introduces organization AI keys, AI Chat appears only after an Organization owner or admin adds a key and allows the Site, including for existing Organizations. See Set up the built-in AI assistant. Your own agent works over MCP on every Site either way.

Connect your AI agent

Use https://app.typeroll.com/api/mcp with an MCP-compatible client. Follow Connect your AI agent for OAuth or API-key setup and verification. A site-scoped key limits the agent to that site; creating sites and configuring shared publishing requires organization scope.

Reading public documentation does not authenticate an agent. Keep credentials in your client’s secret storage and confirm the Organization, Site and Version before requesting changes.

Publish with your own accounts

Open Account → Publishing and follow Connect your accounts. This covers personal or organization GitHub accounts, Cloudflare, R2, shared builds and domains. Connections are reused across Sites; additional Hosting Groups provide their own hosting accounts and site address bases.

Cloud operates the CMS. Your connected accounts supply generated source storage, build execution and static hosting. GitHub and Cloudflare usage is subject to those providers’ terms and allowances, separately from the Cloud service.

Saving a page or selecting Published does not deploy it. Select the intended Version, deploy and wait until the verified public link appears. The build guide explains branches and progress; domain settings explain preparing an address change. Existing redirects, including old file URLs such as /about.html, are included in the generated source and static output. If preparation or a build fails, its error must be resolved before the new deployment can replace the live site; do not remove redirects to work around a failed build.

Forms, Apps and Extensions

Use the shared Forms, core module and Extension guides. A static website can call separate runtime services. Cloud operates its core endpoints; external providers operate their own services. Accounts, subscriptions and permissions for connected services remain separate from having a Cloud login.

You do not need to deploy the self-hosted CMS container, configure Cloud’s internal queues or manage its infrastructure credentials. If a setup message requires an operator action, retain its error text and contact the service operator. Repeatedly disconnecting working accounts is not a substitute for that missing setup.

Trial and access

See Cloud trial and access for the planned 30-day trial without a payment card, its rollout status, Forms with your own SMTP, and post-trial read/export access.