Managed Service 24 / 26
Drupal → Astro
Drupal 10 reaches end of life on 9 December 2026. You are funding a project either way.
Drupal 10 reaches end of life on 9 December 2026, and on that date the security fixes stop. Moving to Drupal 11 is a real project — contributed-module compatibility, a PHP version, APIs that have been removed — so the work gets funded whichever direction you choose. We re-platform the front end to a static Astro build on Cloudflare: the same content, the same URLs, served from the edge. Editors can keep Drupal and author exactly as they do now, or the platform can be retired altogether.
What Drupal → Astro delivers
Editors can keep Drupal
Drupal's JSON:API module exposes nodes, fields, taxonomy and menus. Astro reads that and builds the pages, so the authoring experience your team already knows is untouched.
Faithful re-platform
Content, structure, URLs and redirects carried across, so rankings and inbound links survive the cutover.
Nothing left to patch
Edge-served on Cloudflare — no PHP process, no per-request database, and no module update sitting in the request path.
We name what is rebuilt
Views, Webform, Panels, Layout Builder and anything a contributed module renders at request time are rebuilt, not converted. You get that list before you commit, not after.
Representative stack
Drupal
Astro
Sanity
CloudflareResend
Sentry.ioVersion support — the published end-of-life dates
What is still supported, and what has already stopped.
Unsupported. No security fixes have been issued since end of life.
End of life: 5 January 2025
Released 19 November 2015. Unsupported.
End of life: 17 November 2021
Released 3 June 2020. Unsupported.
End of life: 1 November 2023
Released 15 December 2022. Supported today — this is the version with the deadline.
End of life: 9 December 2026
Released 2 August 2024. Supported.
End of life: Not yet published by Drupal
Scheduled for release the week of 7 December 2026.
End of life: Not yet published by Drupal
Every date above is published by Drupal on its core release schedule. Drupal 12 arrives the same week Drupal 10 support ends. Drupal has not published an end-of-life date for Drupal 11 or Drupal 12, so none is stated here.
Capability Maturity — we walk you up the five levels
Operated at Level 4 · Quantitatively Managed — measured, predictable and owned. We track this rank and raise it over time. See the five levels →
Why this matters
Functional value, value-stream value — and why it can't be ignored.
Re-platforms a Drupal site to a static Astro front end on Cloudflare — either headless, with Drupal kept as the editing system and read through its JSON:API module, or fully extracted so the platform is retired. Content, structure, URLs and redirects are carried across.
It creates a publishing path with no server in it: every page is built once and served from the edge. It enhances what the business already owns — the content model, the URLs and the search positions come across intact. And it protects the site on the day Drupal 10 support ends, because a static build has no PHP process, no database and no contributed modules facing the internet.
Nothing breaks on 9 December 2026, and that is the difficulty — the site keeps serving, so nobody raises it. What stops is the supply of security fixes: from that date Drupal issues no further security advisories or patches for Drupal 10. Every flaw found after that is published in the open, and on your site it stays open. The consequences then arrive from outside engineering — a penetration test that records unsupported software as a finding, a procurement questionnaire that asks which version you run, an insurer at renewal asking whether your software is still supported and patched. Waiting defers none of it, and there is no version of this where the project goes unfunded: Drupal 10 to Drupal 11 is contributed-module compatibility, a PHP version and removed APIs — the same discovery work as moving the front end to Astro. The only real choice is what you own at the end of it: another supported version with the next end-of-life date already in the diary, or a front end with nothing left to patch.
One data layer · measured & owned
Every service creates data — captured, measured, owned.
Drupal → Astro doesn’t just run — it generates signal. We land that data in one warehouse and turn it into live KPIs tied to a named owner, so performance is attributable and acted on, never trapped inside a single tool.
Data warehouse
Supabase
Snowflake
Keboola
BigQuery KPIs, dashboards & apps
Plotly
Retool
Apache Superset Platform-agnostic — we connect what you already use and add a warehouse only where it earns its place.
How we select technology
We choose technology last — for the outcomes it has to earn.
Never tech for its own sake. A tool joins the stack only where it measurably protects value, cuts cost or unlocks speed — fit to a designed system, owned where it counts, and measurable from day one. How we select technology →
Speed
Modern, edge-served stacks are sub-second. Slow surfaces cost conversion and SEO every single day.
Cost
Cut licence, hosting and per-task SaaS fees — pay for capability, not lock-in or idle enterprise tiers.
Security
Flat, edge architecture with almost nothing left to attack — fewer moving parts, smaller surface.
Ownership & no lock-in
Composable and self-hosted where it counts — you own the system, not rent someone else’s.
Measurability
Clean data and KPIs baked in — you cannot improve, automate or apply AI to what you cannot measure.
Fit to process
The right tool for a designed system — selected against process readiness, so it amplifies, not adds friction.
How we deliver · DMAIC
Every Drupal → Astro engagement runs on DMAIC.
Define the goal and its value, measure the baseline, analyse the real constraint, improve with a proven build, then control the gains — so results are predictable, repeatable and defensible, not down to luck.
Agree the goal, value, budget & timescale up front.
Baseline the KPIs above — current state, not guesswork.
Diagnose the real constraint and the solution needed.
Build the chosen solution; prove the uplift.
Lock in the gains; monitor and sustain them.
FAQ
Common questions
What is Drupal → Astro?
Drupal 10 reaches end of life on 9 December 2026, and on that date the security fixes stop. Moving to Drupal 11 is a real project — contributed-module compatibility, a PHP version, APIs that have been removed — so the work gets funded whichever direction you choose. We re-platform the front end to a static Astro build on Cloudflare: the same content, the same URLs, served from the edge. Editors can keep Drupal and author exactly as they do now, or the platform can be retired altogether.
Why does Drupal → Astro matter?
Nothing breaks on 9 December 2026, and that is the difficulty — the site keeps serving, so nobody raises it. What stops is the supply of security fixes: from that date Drupal issues no further security advisories or patches for Drupal 10. Every flaw found after that is published in the open, and on your site it stays open. The consequences then arrive from outside engineering — a penetration test that records unsupported software as a finding, a procurement questionnaire that asks which version you run, an insurer at renewal asking whether your software is still supported and patched. Waiting defers none of it, and there is no version of this where the project goes unfunded: Drupal 10 to Drupal 11 is contributed-module compatibility, a PHP version and removed APIs — the same discovery work as moving the front end to Astro. The only real choice is what you own at the end of it: another supported version with the next end-of-life date already in the diary, or a front end with nothing left to patch.
How does Sentry deliver Drupal → Astro?
Re-platforms a Drupal site to a static Astro front end on Cloudflare — either headless, with Drupal kept as the editing system and read through its JSON:API module, or fully extracted so the platform is retired. Content, structure, URLs and redirects are carried across.
What do I get with Drupal → Astro?
Editors can keep Drupal: Drupal's JSON:API module exposes nodes, fields, taxonomy and menus. Astro reads that and builds the pages, so the authoring experience your team already knows is untouched. Faithful re-platform: Content, structure, URLs and redirects carried across, so rankings and inbound links survive the cutover. Nothing left to patch: Edge-served on Cloudflare — no PHP process, no per-request database, and no module update sitting in the request path. We name what is rebuilt: Views, Webform, Panels, Layout Builder and anything a contributed module renders at request time are rebuilt, not converted. You get that list before you commit, not after.
Start here · the free first step
Drupal → Astro starts the same way every engagement does: with Discovery.
Two distinct moves — a free, no-obligation Discovery Session to find your value at stake, then the Discovery & Blueprint: 14 structured outputs — value model, roadmap and business case — before a pound of delivery is committed.
Engaged alone or as one engine