Astro support and maintenance for websites in production.
Astro support and maintenance keeps your project inside the version window that still receives security fixes. We maintain dependencies and adapters and add features, including on sites somebody else built.
Two majors in one year
Astro 6 went stable in March 2026, Astro 7 in June 2026. Falling behind happens faster than planned.
One major of safety net
Security fixes exist for exactly one previous major version. That makes maintenance predictable.
Takeover after an audit
We read inherited Astro code first. We decline when a rebuild is the better answer.
See what we build.
Mini Marvin is our own progressive web app, designed, built and running live in the browser.
Swipe baby names instead of scrolling
Mini Marvin is our progressive web app for finding baby names: swipe through 10,000+ first names right in the browser, no app store needed.
What Astro maintenance covers.
-
Version inside the security window
We keep your project on the current Astro 7 line or document why an upgrade is waiting.
More on this
Astro follows semantic versioning, and extended maintenance with security fixes covers exactly one previous major version. Two majors behind means no security patches at all. Major jumps are planned, tested in a branch and only then shipped. The procedure is on Astro upgrade.
-
Dependencies, adapters and pipeline
Build toolchain, UI integrations and CMS SDKs arrive bundled and with a build to prove it.
More on this
Where routes render on the server we maintain the adapter for your runtime, along with environment variables, caching rules and redirects. Node versions reach end of life and platforms change their runtimes; left alone, the build breaks eventually, usually when time is short. On operations see Astro hosting.
-
The content model grows with you
New fields, new collections, an extended Zod schema and queries adjusted through getCollection().
More on this
Content collections validate every entry against their schema. When an editor needs a field that does not exist, workarounds creep into body text or the build fails. For the editing side see Astro CMS and edit your website by chat.
-
New features without a rebuild
An extra landing page, a careers section, a calculator as an island: Astro grows in steps.
More on this
A relaunch is rarely the cheapest answer to a new request. Outside the retainer and therefore quoted separately: new page types, design work, editorial content, migrations and an accessibility review. Which category a request falls into, we say up front.
Is your Astro site running unmaintained?
Send us the URL and, if possible, a look into the repository. You get an assessment of version status and risk.
When a maintenance retainer pays off.
A retainer pays off when …
Your website is part of the operation.
- Routes render on the server, so adapter, runtime and environment variables need care.
- A CMS, CRM or payment service is connected whose SDKs follow their own release cycles.
- An outage costs revenue: shop, lead generation, bookings, appointment funnels.
- You have no development team of your own that schedules major upgrades reliably.
You need none when …
An update window on request is enough.
- Your site is a small static website with no server rendering. One update window a year covers it.
- Content barely changes and no external systems are connected.
- A relaunch is already coming. Then the budget belongs in the new build.
- Your requirements have outgrown a website. Then we talk about custom software development.
Taking over an inherited Astro project.
Review access
Repository, hosting, domain, DNS, CMS: we list what exists and who can reach it.
Audit the code
Astro version, rendering mode, adapter, collections, integrations, build time, known gaps.
Verdict and recommendation
Take it on, take it on after stabilisation, or decline. In writing, with reasons.
Stabilisation
A defined version level, a reproducible build, documented environment variables.
Operations and roadmap
Planned update windows, changes through pull requests, quarterly prioritisation.
Common questions on Astro maintenance.
How often does an Astro website need updating?
Minor updates continuously and one planned major upgrade per cycle. Astro follows semantic versioning and ships majors at short intervals, with security fixes for exactly one previous major. That way you never sit two majors behind.
What does Astro maintenance cost per month?
It depends on scope. A static marketing site sits well below a site with server rendering, a CMS connection and continuous development. We quote after the inventory, split into base care and further development, see Astro development cost.
Can you take over an Astro project somebody else built?
Yes, after an audit of three to five working days. With server-rendered routes and a connected CMS that becomes one to two weeks. You get a written verdict, and one of the possible answers is that we decline.
How fast do you respond to an incident?
Same working day, usually within a few hours. A failed deploy is rolled back in minutes, an outage at your hosting provider sits outside our hands. Round-the-clock on-call duty is something we do not offer.
What happens if we end the engagement?
You keep everything. Repository, hosting account, domain, CMS and documentation run in your name from day one. At the end there is a handover with version status, open items and the deployment procedure. Astro is MIT-licensed.
Could AI handle the maintenance for us?
It helps with routine work, and we use it ourselves. Every change still passes review, type checking and a build in continuous integration. Credentials and personal data stay out of such tools, see GDPR-compliant websites.
More from the Astro cluster.
The pages adjacent to operations and care:
Maintenance that starts before the outage.
Tell us where your Astro website stands: version, hosting, who built it. Answer usually within 24 hours.
Request Astro maintenance.
Briefly describe what you need: ongoing care, takeover of an existing project, or a single update window.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.
Related pages.
Astro Agency
The overview: how we build with Astro, what the stack does well and where its limits are.
Learn moreAstro Web Development
A new build instead of a takeover: concept, implementation and launch of an Astro site.
Learn moreAstro Performance Optimization
Existing Astro site feeling slow? Measure, find causes, fix them.
Learn moreAstro Migration
Moving from WordPress, Webflow, Framer or Next.js, with a redirect concept.
Learn moreWhat Is Astro?
Islands, server-first rendering, content collections: the basics without marketing fog.
Learn moreWebflow Agency
The sister service, when a visual platform fits your team better.
Learn more