For the technical evaluator
Most people never need this page. But if you're the CTO, the technical co-founder, or the developer friend being asked to sign off — here's the whole thing, honestly.
Every BlinkPages site is a standard, open-source Astro project — pre-built static HTML, served from Cloudflare's global edge network. You edit it by describing changes in plain language to Claude; you preview and approve before anything goes live. Your domain stays yours, the source is yours to export at any time, and underneath it's a normal git repository. That's the whole model. The rest of this page is the honest detail.
Your site is served from Cloudflare's global edge network — the same infrastructure behind a large share of the web. Because the site is pre-built static HTML, there's no application server spinning up per request and no database query in the path. The pages are cached and delivered from a location near each visitor, which is why static sites feel fast.
We manage that Cloudflare setup for you. You don't provision servers, configure a CDN, or renew certificates — and we're not pretending to own data centers. Cloudflare handles HTTPS/TLS and DDoS protection at the edge. What you get is the performance and uptime characteristics of that network, without the operational work of running it.
And your domain stays yours. You keep your registrar and your DNS, and you point a record at us — a CNAME, or a Cloudflare-proxied ("orange-cloud") setup for an apex/root domain. The free default is a blinkpages subdomain. We never take over your nameservers. If you ever want to leave, you change one DNS record back and you're gone.
No live server, no database, no plugins means a deliberately tiny attack surface. There are no plugin CVEs to track, no database to breach, and nothing to wake up and patch at 2 a.m. The most common ways a typical WordPress or page-builder site gets compromised simply aren't present.
Here's the full path a change takes, start to finish. It's human-in-the-loop by default — nothing publishes behind your back.
In Claude, in Slack, in an email, . Plain language — no ticket format, no markup.
BlinkPages makes the change to your site's code — real edits to the Astro project, not a content field bolted on top.
The change lands as a Draft you can look at before it ever touches what's Live. Nothing is published yet.
Only your approval promotes a Draft to Live. Trivial fixes can go straight live on command if you want that — your call.
The approved change publishes to your domain. You can save Versions and roll back, and a full history of every change is kept — nothing is ever lost.
That Live / Draft / Version surface is what you interact with day to day. Underneath, it's a normal git repository — so any developer can clone it and see every change as a commit, with a complete history. The friendly version model on top and the git repo underneath are the same thing, described at two altitudes.
No black boxes
Static Astro, a git repo underneath, and your domain on your own DNS. Nothing here is a format you can't get back out of.
see it on a real siteThe reason plain-language editing works is that your site is AI-ready by construction. It ships with a maintained, first-class connection to Claude (Anthropic) that can read and edit your site's code directly. This isn't a brittle integration you wire up and babysit — it's part of how the site is built and kept working.
Because the site is standard Astro — clean, readable code rather than an opaque CMS export — Claude has something coherent to work with. That's the difference between an AI guessing at a page and edits that actually fit the project.
By default the Claude usage is included and there's nothing to set up. If you'd rather run it on your own account, you can bring your own Anthropic (Claude) API key and keep the usage on your own bill. Same platform either way — see pricing for the two options.
This is usually the question that matters most to the person signing off, so here it is plainly: you own your site, and you can leave at any time.
Export the full source whenever you want. Because it's a standard Astro project, any developer can read it, run it locally, and extend it — you can host it yourself, hand it to another developer, or have us help you self-host. There are no exit fees and no hostage data. Your domain was always yours; leaving is a DNS change, not a negotiation.
If you already have a site, migration is done-for-you and takes about seven days. Same content, same domain, same URLs — so your search rankings carry over — now served as a fast, static, AI-ready Astro site. When it's ready, you cut over the DNS and you're live.
While you're here
The other half of the story: what you get for letting us manage it.
Your pre-built HTML is served from Cloudflare's global network — the same infrastructure behind a large share of the web. Fast and low-latency everywhere, with HTTPS and DDoS protection included. We manage that infrastructure for you; you don't run servers, and we don't pretend to own data centers.
Because the site is static — no live server, no database, no plugins — there's very little to attack. No plugin CVEs, no database to breach, nothing to patch at 2 a.m. It's about the calmest thing you can put on the internet.
You describe a change in plain language — in Claude, in Slack, in an email, or out loud on a call. We build it. It lands as a Draft you preview before it ever touches Live. You approve; it publishes to your domain in seconds. Nothing goes out behind your back. Trivial fixes can go straight live on command if you want them to.
Every site ships with a maintained, first-class connection to Claude (Anthropic) that can read and edit your code — not a brittle bolt-on you wire up yourself. Prefer to run the AI on your own account? Bring your own Anthropic API key.
Static, secure, and edited in plain language — and we run the Cloudflare side so you never touch a server. Pricing is one flat rate, all-in; details on the pricing page.
The ones a technical evaluator actually asks.
No. Your site is a standard, open-source Astro project — the same framework any front-end developer can pick up and run locally. There's no proprietary format, no database schema to reverse-engineer, no plugin ecosystem to depend on. Under the hood it's a normal git repository, so every change is a commit you can read.
On Cloudflare's global edge network — the same CDN that fronts a large share of the web. Because your site is pre-built static HTML, it's cached and served from a location near each visitor, with HTTPS/TLS and DDoS protection included. We manage that Cloudflare setup for you; you don't run any servers.
No. You keep your domain, your registrar, and your DNS. You point a record at us — a CNAME for a subdomain, or a Cloudflare-proxied ("orange-cloud") setup for an apex/root domain. We never take over your nameservers. If you ever leave, you change one record back.
Yes, at any time. Export the full source and host it yourself, hand it to another developer, or have us help you self-host. It's standard Astro, so any developer can clone it, run it, and extend it. No exit fees, no hostage data.
There's very little to patch. A static site has no live server, no database, and no plugins — so no plugin CVEs, no database to breach, nothing to wake up and patch at 2 a.m. Cloudflare handles TLS and DDoS at the edge. The attack surface is deliberately tiny.
The maintained Claude connection is included and works out of the box. If you'd rather run the AI usage on your own account, you can bring your own Anthropic (Claude) API key — see pricing.
Bring your hardest questions
Book a demo and we'll open the hood: the git history, the export, the DNS setup — and ship a real change on a real site while you watch.
book a demo