Astro.
Content sites and marketing pages that send HTML first and add JavaScript only where a page needs it.
Talk to us about Astro
Key features
What Astro does well.
Islands architecture
Pages ship as HTML, and only the components marked as interactive load JavaScript in the browser.
Use any UI framework
React, Vue, Svelte and Solid components can sit on the same page, which helps when reusing parts of an existing product.
Server islands
A personalised or slow part of a page can render on the server after the rest, so the cached page still loads straight away.
Live content collections
Stable since Astro 6, these fetch content from a CMS or API at request time, with no rebuild after each edit.
What we build with it
Send the page, not the framework.
Astro renders each page to HTML and hydrates only the parts that need to run in the browser, such as a form or a filter. This website is built with it. We use Astro for marketing sites, documentation and content-heavy products, and bring in React components where a page needs real interactivity.
Company and marketing sites
Pages that stay quick on a slow phone connection, because most of each page arrives as plain HTML.
Documentation and articles
Content collections that check every article and guide against a schema when the site builds.
A public site beside an app
A fast front door for a React product, sharing its components and design tokens.
When it’s the right choice
Astro fits sites that people mostly read: marketing pages, blogs, documentation and product pages that need to rank in search.
When we’d pick something else
If every screen is interactive, like a dashboard behind a login, Next.js or a React single-page app is less work.
Our Astro services
How we can help.
New Astro sites
Marketing sites, documentation and blogs, designed and built with a typed content model.
Migration to Astro
Moving a WordPress, Gatsby or heavy single-page site to Astro, keeping URLs and redirects intact for search.
CMS integration
Connecting Astro to a headless CMS so editors can publish and preview without a developer.
Speed and accessibility audits
Reviewing an existing Astro site for script weight, image handling, Core Web Vitals and accessibility issues.
How we work
Starting a Astro project.
Review what exists
Code, data, hosting and the people who maintain it, before any Astro decision is made.
Agree the approach
A written scope: what changes, what stays, the risks and how we will know it worked.
Build in reviewable slices
Working increments your team can test, rather than one large delivery at the end.
Hand over or stay on
Documentation and access for your team, or a defined support scope if you want us to keep going.
Where AI fits
AI in web work.
Answers inside your app
Add a search or question box that answers from your own documents, streams the reply into the page and shows its sources.
Knowledge assistants ↗Review screens for AI output
Interfaces where staff check, correct or reject what a model drafted before it is saved.
AI workflow automation ↗
Where it stops: The browser should never hold model keys or decide what a user may see. That stays on the server.
What’s changing
Shifts to plan for.
Dates that affect Astro projects, checked against the official sources.
January 2026
Astro team joins Cloudflare
Cloudflare took on the Astro team. The framework stays MIT-licensed and can still be deployed to other hosts.
Where it fits
Related expertise.
- UX & UI design Interfaces designed around real tasks, with every state, error and edge case resolved before build.
- Design systems Shared components, tokens and rules that keep screens consistent as more people work on the product.
- Web application development Browser-based tools for customers and staff, built for the data, roles and permissions behind them.
Common questions
Astro questions.
Can our team edit content without a developer?
Yes. Astro works with headless CMSs such as Sanity, Contentful and Storyblok. Markdown files in the repository also work well if your team is comfortable with Git.
Where can an Astro site be hosted?
A static build runs on any CDN or static host. Server-rendered pages need an adapter, and there are official ones for Node, Netlify, Vercel and Cloudflare. Cloudflare took on the Astro team in January 2026; the framework is still MIT-licensed.
Further reading
- Awaab’s Law and the software landlords use for repairs What Awaab’s Law asks of the systems social landlords use to log, investigate and repair hazards, and the records they need to keep.
- Firebase, Supabase or a custom back end: how to choose How to choose between Firebase, Supabase and a custom back end by data shape, access rules, cost, exit paths and skills.
- One codebase, three platforms: iOS, Android and web with Expo Lessons on sharing code, drawing with Skia and handling phone, tablet and desktop layouts from one Expo codebase.
