Under the hood
What runs where, and how long it takes.
Before you let a client into your code, you want to know what touches it. Here is every part of Siteshare, where it runs, what it keeps, and the times we measured last.
The parts
Your client in the middle, your repository in charge.
Your client
Siteshare
Yours, as before
One change
From a question in the chat to the live site.
The times are the middle of our latest runs on Astro, a 255-page site on Cloudflare Pages. The last step depends on your host.
Where it lives
Your site lives in one place: your repository.
Everything else is around it, and you can take Siteshare away without your site noticing.
| Who | What runs there | What it keeps |
|---|---|---|
| Cloudflare | The editor, the sandboxes, the database and the files. | Names, addresses and the log for a year; photos for 7 days; pictures of a page for 30 days. |
| Anthropic | The AI model the assistant uses. | Each request as the assistant sends it, under Anthropic's terms for its API. The conversation itself stays in the site's sandbox. |
| GitHub | Your repository, reached through a GitHub App on the repositories you choose. | Your site, its draft and every published version. This is the only place your site lives. |
| Your host | Cloudflare, Netlify, Vercel, or wherever you host today. | The live site. Siteshare doesn't touch it. |
| Resend and Stripe | Mail, and payments for paid sites. | The addresses mail goes to. Card details stay with Stripe. |
Load times
Measured, per kind of site, including what's still slow.
From our latest runs on test sites of each kind, last on 5 November 2026: 42 starts in all, at night and during the day. Each cell is the fastest and the slowest run.
| Site | Editor readyafter a pause | Editor readythe very first time | Change in the preview | Publish until it's on main |
|---|---|---|---|---|
| Astroa 255-page site on Cloudflare Pages | 8.3–13 s | 29–32 s | 4.5–7.9 s | 4.1–7.2 s |
| Next.jsa landing page | 7.8–16 s | 24 s | 7.1–8.3 s | 14–36 s (above our goal) |
| Nuxta site with Nuxt Content | 11–13 s (above our goal) | 20 s | 12–14 s (above our goal) | 28–33 s (above our goal) |
| SvelteKita blog | 5.2–5.3 s | 7.7 s | 6.7–9.2 s | 4.8–6.4 s |
| Vite and Reacta landing page | 4–4.6 s | 7.4–7.8 s | 4.6–6.9 s | 4–6.6 s |
| Hugoa site with Tailwind | 4.2–4.6 s | 6.4 s | 5.2–9.6 s | 3.8–5.6 s |
| Our goal | 10 s | 45 s | 10 s | 10 s |
Back within an hour? A site keeps running for 60 minutes after it was last used, so the editor is ready in about 2.5 s.
Still above our goal: the cells in orange, with an arrow. Each waits on the site's own development server or build, which is heavier on Next.js and Nuxt. Larger machines help here; we decide on them with the numbers from the first months.
When something goes wrong
The live site is the last thing to break.
It doesn't build
Publish stops before main. The live site stays as it was, and the draft waits until it's fixed.
A change was a mistake
Restore brings back any of the last 10 versions, as a new commit on top. Main is never rewritten.
It's beyond what a client may change
It isn't refused. It waits in the draft for the site's owner, who approves it, finishes it or says no.
Siteshare is down
The editor is unavailable; your site isn't. Your host keeps serving main, with or without Siteshare.
How the sandbox, the assistant and sign-in are kept safe is on Security.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.