Technology is a means, not a purpose
WordPress, Astro, Laravel, headless CMS. Each of them solves something well and something else badly. These pages explain which one applies when – including when the answer is: stay with what you have.
Trusted by businesses like
- united-domains
- etepetete-bio
- Vulkan Eifel Therme
- LG
- Peter Hahn
- YAYLA ARENA
- Seidenweberhaus Krefeld
- advantago
- Tekath Headhunting
- IGES Institut / F+B
- PetCrew
- Rheinplan
- Benevit
- Stadt Kassel
- Hörner Gruppe
- Hansestadt Greifswald
- Stadt Heilbronn
- Stadt Nordhorn
Four paths, one question
The question is never “which technology is best”, but “who maintains this in three years”. Almost everything else follows from that.
Laravel
For everything that is more than a website: portals, dashboards, interfaces, booking and billing logic. Structured cleanly, so it is still maintainable in five years.
- Web applications and customer portals
- API development and system integration
- Multi-tenancy and tenant separation
- Filament back office
Astro
When speed and search engines matter: static sites for marketing, multilingual presences and landing pages – with an editing interface where one is needed.
- Marketing and corporate sites
- Multilingual setups without plugin stacks
- Care package after launch
WordPress
The CMS most editorial teams can handle. We build corporate websites and shops with it – and say so when a project runs into its limits.
- Custom themes instead of page builders
- Plugin development for specific requirements
- WooCommerce for online shops
Headless CMS
Editing and output separated: content in Storyblok, Directus or WordPress, delivered through Astro. Useful when several channels need the same content.
- Storyblok, Directus, Hygraph, WordPress as backend
- EU hosting as a selection criterion
- Editorial preview before publishing
WordPress → Astro
The migration path for sites that want to leave WordPress without losing their rankings on the way. Including a redirect plan and content transfer.
- Carry over content, images and URL structure
- Redirects instead of lost rankings
- Settle the editing workflow after the move
AI-maintained Astro site
An Astro site maintained through an AI-assisted workflow rather than an editing back end. For teams that publish rarely and deliberately.
- Content through a text workflow instead of a CMS
- Versioned in Git, every change traceable
Not sure which direction fits? Then do not start with the technology, but with what the site has to achieve – that is what concept and planning is for. What we build with it is under services.
Frequently asked questions
Why do you give technology its own section?
Because choosing the technology is a decision of its own. Whether a site is built with WordPress, Astro or Laravel depends on who maintains it later, how often content changes and what it has to do. “Services” covers what we build. This section covers what we build it with.
Do you decide the technology up front?
No. We propose what fits your case and explain why. If your team has worked with WordPress for years, switching to Astro is rarely the right answer – even where Astro would be technically faster.
Can you work with a technology that is not listed here?
Usually yes, but we will say so honestly where we have less experience. These pages describe where we are confident from daily work. For anything else: ask, and you get a realistic assessment.
What if we want to change technology later?
It happens, most often from WordPress to Astro. We have written up that migration path separately – including what happens to existing URLs and rankings.
Unsure what fits your case?
Tell us briefly what you have in mind. You get an assessment of which technology fits – including when that means you should not change anything.
Prefer to talk? +49 9163 6791505 (Mon–Fri, 8 am–6 pm CET)