FEATURES · PUBLISHING
Publish to accounts you own
Typeroll publishes every site as static files. The source goes to a GitHub repository you own, the build runs on Cloudflare or GitHub, and Cloudflare serves the result from your account. A CMS update never replaces files that are already live.
How publishing works
01
Your accounts, connected once
Connect GitHub, Cloudflare and R2 media storage once per Organization. Every site uses them; each site keeps its own domain and publishes independently.
02
Edit, freeze, build, serve
Publishing freezes a saved version, writes Astro source to your repository, builds on Cloudflare or GitHub and uploads static files to Cloudflare Pages.
03
Checked before it goes live
Publication checks validate the actual static output before activation. If a technical check fails, the current live site stays as it is.
04
Small changes publish small
Partial builds re-render only the routes a change affects and reuse media that is already hosted.
05
Domains without downtime
Prepare a domain change, verify the new address, then switch traffic, with a journal that can restore the previous DNS.
06
Portable output
The generated repository contains buildable site source. You can build and host its static output yourself.
GOOD QUESTIONS
Questions and answers
Is Cloudflare Pages free?
Static asset requests on Cloudflare Pages are free. Builds, storage and dynamic services have their own pricing.
Can I use another host?
The generated source is portable. Typeroll's managed publishing targets Cloudflare.
START BUILDING
Try Typeroll Cloud for 30 days.
Free during the beta. No payment card. After the beta, USD 39 per month, or USD 29 per month billed annually.