Your website

How it works, for IT and security.

What connects to what, who can change what, how a change is made, where data lives and what your IT team does. Each part links to the full documentation.

How a change reaches your website
  1. Claude, ChatGPT or CursorSigned in to Echo with OAuth
  2. EchoRights, changes, review. EU data
  3. GitHubA branch per change, merged on Publish
  4. CloudflareBuilds the preview, then the live site
  5. Your DNSwww points to the site

Access and rights

People sign in without passwords. AI acts only as the person, with their rights.

Sign-in
Google or a one-time email link. No passwords to leak.
Website rights
Per person: Content (text and CMS), SEO (pages, redirects, files), Design (layout and code, through AI), Publish (review the release, publish to staging and live) and Admin. A site always keeps two admins.
Claude, ChatGPT and Cursor
Connected through Echo's connector with OAuth. Within the person's rights, its tools read and write the site's files on a branch and return the preview link. After a change it asks whether to publish now (staging and live, staging only, or not yet) and publishes when you say so, so you don't have to open Echo. It can't delete, spend money or change Echo's settings.
Echo's GitHub App
Installed on the site's repository only, with access to its contents and build results. Nothing else in GitHub.

Edit your websiteEcho in ClaudeSet up Claude, ChatGPT or CursorTeam and rights

How a change is made

Every change is a preview on its own branch first. Publish merges it, with a name on it.

The job
A Cloudflare Workflows job runs the AI with a few tools: list files, read a file, search, write files. The repository's AGENTS.md gives it the site's rules.
What it may touch
Only src/** and public/**. Never .github, wrangler files, environment files, lock files or packages: those go to the studio as a request.
Branch
Each change is committed to its own branch, echo/<id>, through Echo's GitHub App.
Preview
The site's Cloudflare build makes a preview of the branch. If the build fails, the AI gets the log and tries twice more, then stops and says so.
Release and staging
Changes wait in the site's one release. Publish to staging builds the branch echo-next (live plus the picked changes and text edits) on staging.<your domain>, which Allsite sets up and only your team can open.
Deploy to live
Merges exactly what staging has into main, with the name of the person who clicked. The site's build deploys it. A site still on its demo address publishes straight to live.
Undo and history
Undo is a new commit that puts the old version back, never a rewrite. Each change is also recorded as a done task: who asked, what changed, before and after.

VersionsProtected stagingWebsite requests

AI and costs

Three ways to run the AI. Only one uses Echo's credits.

Your own Claude, ChatGPT or Cursor
Through Echo's connector. Your subscription pays for the AI; Echo adds no AI cost.
Your own API key
Add an Anthropic or OpenAI key in Echo, and Echo's AI runs on it. No credits used.
Echo's AI
Claude by default, in Echo and for changes asked in Slack or Teams. Uses the workspace's credits, with usage by day, feature and person.

Domain and DNS

No nameserver change and no account for your IT team. Two records at your DNS provider.

TXT _cf-custom-hostname.www
A one-time code that proves the domain is yours. We send the value.
CNAME www
Points www to the site on Cloudflare. We send the target address.
Domain without www
Forwards to www at your DNS provider.
HTTPS
Certificates are issued and renewed by Cloudflare by themselves.
Undo
Set the CNAME back to its old value. Email (MX) and other records are never touched.

Data and hosting

Echo keeps its data in Western Europe. The website is static files on Cloudflare's network.

Echo
Runs on Cloudflare, with its database and files in Cloudflare's Western Europe region. GDPR compliant, run from Berlin.
The website
Built into static files and served from Cloudflare's network. Forms, where the site has them, run as small Cloudflare functions.
Services
The providers that process data for Echo are listed on the security page, each under a data processing agreement.

SecurityData processing agreementPrivacy policyPrivacy and dataSystem status

Ownership and exit

Content and domain are yours. We run code and hosting, and hand them over when you leave.

Content
Yours. It lives in the site's repository as plain files, readable without Echo.
Domain
Stays registered to you, at your provider.
Code and hosting
In the studio's GitHub and Cloudflare accounts by default. If you leave, we transfer the repository and you get a copy of the site.
Your own accounts
If your policy requires it, the site can run in your own GitHub and Cloudflare, with the studio as a member. That's custom pricing: book a call.
If Echo stops
The site keeps running. Only changing it from Echo and your AI tools stops.

Security contact

Report a problem or ask for our security documents.

Questions about your website?