Developers
An Astro integration and a GitHub App. Typed content collections, schemas, pull requests, your CI. Nothing you would not have built yourself, if clients ever paid for it.
Optimised for content-driven Astro sites
SEO and AI on autopilot.
An agent moves into your Astro site and never leaves. It reads everything the site knows: Search Console, analytics, every page, every image. It proposes what to improve as pull requests, with the numbers behind each one. Once you trust it, it makes the safe ones itself.
> add alive to this site # your copy becomes content, your layout stays yours
> add alive to this site # the same Agent Skill, in Cursor's agent
> add alive to this site # the same Agent Skill, in Codex
- velo-muster.ch · health 86
- /pricing/ · title drafted · checks passed
- pr #37 · approved by the owner
- /blog/chain-care/ · answer added · measuring
- /impressum/ · held back · hands off
- after 28 days · clicks +55% · low confidence
- image descriptions · 3 live on autopilot
- /team/ · link added · undone by the owner
- next run · monday 06:00
- example
Who it is for
Built by coders.
Kept alive by an agent.
Vibecoders
You shipped the site in a weekend with Claude Code or Cursor. Launch day was the easy part. alive keeps it growing after you have moved on to the next one.
Web designers
Your layout stays yours. The agent works on words, images and links inside it, and never touches your code, styles or components without asking you.
Agencies
Every client site on one screen, a report each month, and a care plan you can re-bill. Clients edit what they want; the agent does the rest; you keep the receipts.
What it is made for
Optimised for content-driven Astro.
Sites where the content does the work: pages people find through search and AI answers, and read before they call, book or buy. On those, titles, answers, alt text and links move the numbers, and those are exactly what the agent works on.
It reads and writes
- Content collections
- Markdown
- MDX
- JSON
- YAML
- Zod schemas
- Marketing and service sites
- Local businesses: practices, trades, restaurants, hotels
- Blogs, magazines and guides
- Docs and help centres
- Portfolios and studios
- Agency client sites, one or a hundred
- Web apps and dashboards
- Shops whose products live in a shop system
- Pages that are mostly client-side code
Part app, part content? The agent works on the content pages and leaves the rest alone.
What the agent looks at
A site with a pulse.
Most websites are finished on launch day and slowly go stale. A site with alive listens, reads, remembers, and changes, one small, checked step at a time.
- Ears: Search ConsoleWhich searches find each page, how often, and at what position.
- Nerves: analyticsHow people move through the site, as totals per page. Never one visitor.
- The eye: every pageTitles, headings, links, images and structured data, read the way search engines read them.
- The brain: the knowledge pageWhat the business stands behind: prices, facts, voice, and the claims it never makes.
- The heart: the agentRules decide what to change and why. Each idea carries its evidence, or it is dropped.
- The tongue: the modelYour own AI key. It only writes the words, inside checks it cannot talk its way past.
- The spine: gitEvery change is a pull request, one commit, reviewed by your CI, undone with a click.
- The roll: receiptsWhat changed, who approved it, and what happened to the numbers after.
The loop, every week
Read. Find. Propose. Ship. Measure.
- 01Read
Search Console, analytics and the live pages, fresh each week.
- 02Find
Few clicks for a good position, a question the page never answers, a page no link reaches.
- 03Propose
A new title, one answer, a description, one link: small, and with its numbers.
- 04Check
No new numbers, prices or claims. Checked twice, before anyone sees it.
- 05Approve
You, your client, or autopilot for the small things it has earned.
- 06Ship
A pull request, merged, built by your host, like any change.
- 07Verify
It looks at the live page until the change is really there.
- 08Measure
Before and after at 28 and 56 days, with how sure the numbers are.
- 06:00:01reading search console · 56 days · 4,210 rows
- 06:00:03crawling velo-muster.ch · 23 pages
- 06:00:07/pricing/ · position 5.0 · 1.1% clicked · the site: 4.0%
- 06:00:08drafting a title and a description for /pricing/
- 06:00:11checks: numbers ✓ claims ✓ facts ✓ length ✓ language ✓
- 06:00:12held back: /impressum/ (hands off, legal page)
- 06:00:13pull request #37 opened · waiting for the owner
- 14:02:40approved by the owner
- 14:04:18live · measuring for 56 days
It holds back, too.
Most ideas never become changes. The agent leaves a page alone while its last change is still being measured, stays away from legal and contact pages, respects a "no" for a month, and never proposes more than five changes a week. Every idea it drops is written down with the reason.
"Held back: a change to this page went live on 12 September; it is measured for 56 days before the next one."
You decide how alive
Proposes. Or does it itself.
Every change waits for you.
The agent proposes; you or your client approve, edit or decline each one, on a phone if you like. This is where every site starts.
Small things, on their own.
Image descriptions, titles, one link: once a kind of change has been approved ten times on a site and never undone, it may ship on its own. One mistake and autopilot switches itself off for that kind.
The agent decides.
It chooses what to change and ships it, within the hard limits below, and undoes its own changes when the numbers fall. It runs on our own sites first, as an open experiment, before agencies can switch it on for clients.
Hard limits, in every mode
- No new facts, prices, numbers or claims: only what the site already stands behind.
- Legal, contact and protected pages are never touched.
- Your code, layout and styles only ever change with your approval.
- Every change is one commit you can undo, and the stop switch halts everything.
- Search data and visitors only as totals. No recordings, no individual people.
- Your own AI key: the agent never holds your GitHub credentials.
Receipts, not promises
We never promise rankings.
We show what changed, when, who approved it, and what happened after. With the confidence the numbers deserve, including "too early to say".
RECEIPT · VELO-MUSTER.CHEXAMPLE
New title for /pricing/
Prices
Bike service prices in Zürich, fixed and fair
Why: shown 2,000 times at position 5.0; 1.1% clicked, the site's pages at that position get 4.0%.
Checksnumbers ✓ claims ✓ facts ✓
ProposedMon 06:00 · agent
ApprovedMon 14:02 · owner
LiveMon 14:04 · 1 min 38 s
After 28 days: clicks 20 → 31 (+55%). Low confidence: numbers this small move by chance.
Measuring · 56 daysFor agencies
Every client site. One screen.
Sell care plans that actually do something. Your clients edit what they want, the agent improves the rest, and every month there is a report with receipts instead of promises.
| Site | Health | This week | Agent |
|---|---|---|---|
| velo-muster.ch | 86 | Title for /pricing/, waiting for the owner | Proposing |
| baeckerei-beispiel.ch | 92 | 3 image descriptions, live | Autopilot |
| yoga-beispiel.ch | 88 | A link to /kurse/, measuring | Proposing |
| kanzlei-beispiel.ch | 74 | Held back: legal pages are hands off | Hands off |
For developers
It is just Astro.
No new framework, no lock-in, no database of your content. The installer moves the copy your coding agent typed into the pages into typed content collections, and proves the site still looks exactly the same.
- Your components, layout and styles stay as they are.
- Content collections in Markdown, MDX, JSON or YAML, with Zod schemas; the CMS builds its forms from them.
- Every change is a pull request your CI reviews, one commit you can revert.
- An SEO seatbelt blocks a noindex or a broken link before it merges.
- Works with any host that builds from git: Vercel, Netlify, Cloudflare Pages.
// astro.config.mjs import alive from '@alive/astro'; export default defineConfig({ integrations: [alive()], // checks, seatbelt, build file });
# what the installer changed src/content/pages/index.json # your copy, now content src/alive/collections/index.ts # typed schemas src/content.config.ts # +2 lines .github/workflows/alive.yml # build, check, seatbelt
The installer and the Astro integration are MIT. The CMS and the agent are AGPL: host them yourself, or let us run them. Your content stays in your git, your keys stay yours.
Pricing we are testing
Cheaper than one hour a month.
Free
$0
One site, for good.
- The CMS for your client
- Every change a pull request, with its receipt
- The agent proposes
Site
$19
Per site, per month.
- The agent every week
- The health report and each page's numbers
- Before and after, at 28 and 56 days
- Autopilot for small things
Agency
$149
Per month, up to 15 sites.
- All client sites on one screen
- A monthly report for each client
- Re-bill it as a care plan
Waitlist members get the first months free. Model costs are on your own key.
Questions
Fair questions.
What kind of Astro site is it for?
Content-driven ones: marketing, service and local business sites, blogs, docs and portfolios, with the content in collections as Markdown, MDX, JSON or YAML. If your copy is still typed into the pages, the installer moves it into collections first. Web apps and dashboards are not the fit.
Will Google punish changes an AI wrote?
Google ranks helpful pages, however they were written. The agent changes little at a time: a title, an answer, a description, one link. Every change is a pull request you can read, and each page's change is measured before the next one. We never promise rankings.
What if the agent gets it wrong?
It cannot invent numbers, prices or claims: deterministic checks turn such drafts down before anyone sees them, twice. Protected facts and legal pages are locked. Whatever ships is one commit: undo it with a click, and the stop switch halts everything.
Who owns the code and the content?
You do, or your client. The content lives in your git repository as plain files. Remove alive and the site still builds.
Does it work with my host?
With any host that builds from git: Vercel, Netlify, Cloudflare Pages and others. The agent checks the live page after each change, wherever it runs.
What does the AI cost me?
The agent uses your own key, so the bill is yours and visible. A weekly run makes at most 30 calls to the model, and most weeks far fewer.
Does it watch my visitors?
No. It reads totals per page from your own Search Console and analytics. No recordings, no cookies of ours, no individual people.
Is it open source?
The installer and the Astro integration are MIT; the CMS and the agent are AGPL, so you can host them yourself. The code goes public in stages, each after its security review.
The waitlist
Make your sites alive.
Be one of the first agencies and builders to try it. We are looking for people with live Astro sites, and for twenty minutes of your time, if you are happy to talk.