No JavaScript unless you ask
Astro prerenders pages by default, with on-demand rendering available when needed. UI framework components do not hydrate unless you use a client directive. Explicit scripts and integrations can still ship JavaScript.
Why Astro
The fastest page is the one that ships nothing extra
Astrology works with Astro projects. Astro prerenders pages to HTML by default and also supports on-demand rendering. Interactive islands and page scripts can add JavaScript. Plain source files make agent changes easier to inspect, not automatically safe: review the diff, permissions and deployment before shipping.
What it does differently
Six architectural decisions, all of them documented and all of them checkable in a project you already have.
Islands, not a whole application
Interactive parts are declared one at a time and hydrate on their own. A search field or a carousel does not put the rest of the page behind a bundle.
Keep the framework you already use
React, Preact, Vue, Svelte and Solid components run as islands inside the same project, so the component library a studio already maintains is not a reason to stay on another stack.
Content with a schema
Content collections give Markdown, MDX and external data a typed schema. A missing field stops the build instead of publishing a page with a hole in it.
One adapter away from any host
The same project ships as static files to any CDN, or runs on a server through an adapter for Node, Vercel, Netlify or Cloudflare. Rendering is a per-route decision, not a rewrite.
A project made of plain files
Routes, layouts, components and content are files in a folder. That is what makes a site legible to an agent — and what makes every change it proposes readable as a diff.
In practice
This site is the example
The site you are reading is an Astro build. Its production output contains no JavaScript framework bundle at all: its pages are built as HTML and CSS, with scripts only where a specific interaction needs them.
See the measurements and the method- Rendered to HTML at build time
- CSS split per route, not one global bundle
- No framework runtime in the browser
Adoption
Chosen by teams that could have picked anything
Astro is not a niche generator. Large engineering organisations run documentation and public sites on it, which is the kind of workload where build output and page weight are measured rather than assumed.
Cloudflare
Cloudflare's developer documentation is built with Astro.
Check CloudflarePorsche
Its public site is built with Astro and is listed in Astro's published showcase.
Find Porsche in the Astro showcaseFirebase
Google's Firebase team is among the published Astro case studies for its documentation and content sites.
Check Firebase
Astro publishes its case studies and a public showcase; the links above go to the case studies, showcase or live site, so each name can be checked rather than taken on trust.
Why it matters here
A project made of files is a project an agent can be trusted with
Coding agents can read and write text files, but cannot see what a hosted builder did to a page behind an API. An Astro project is routes, layouts, components and content — all of it readable, all of it reviewable.
- Every change the agent makes arrives as a diff
- The preview is the real page, from the project's dev server
- Diagnostics run on the same files before anything is deployed
Bring your next Astro project into one window
Astrology runs your agent on the project, then shows you the preview, the diagnostics and the diff before anything reaches the client.
Requires Node.js, npm and Git · AI features use your installed agent CLI