web · astro, typescript, seo, performance
Astro developer for fast websites, built like this one.
You're looking at an Astro site right now: more than 50 pages in three languages, and every one of them reaches your browser as plain HTML. I can build yours the same way, from the first commit to launch.
- Stack
- Astro, TypeScript, Tailwind CSS
- Output
- Static HTML, JavaScript only where needed
- Reference
- This site, 50+ pages in 3 languages
- Engagement
- As a project or as advisory
- Working hours
- Mon–Fri 04:00–18:00 Buenos Aires 09:00–23:00 Berlin 03:00–17:00 New York
- Available from
- Q4 '26
What I build with Astro
- Company and product websites that load fast on a phone with one bar of signal, not just on the office Wi-Fi.
- Landing pages for a launch or a campaign, where a new headline is a one-line commit.
- Multilingual sites with URLs that match what people actually search for in each language (/de/stack/astro-entwickler/, not /de/stack/astro-developer/), plus the hreflang tags search engines need.
- Documentation and content sites, with the content in Markdown next to the code.
The reference: this website
asisto.io runs on Astro 7 and Tailwind CSS. Every case study, service and technology page is a Markdown file, one per language, and the build checks each one against a schema. The sitemap, the hreflang tags and the breadcrumbs all come from one list of routes, so they can’t drift apart. The build also writes the structured data for every page and renders the share images.
The ASCII globe, the live clock and the command menu (⌘K or Ctrl+K) are a few small scripts without a framework, written straight into the HTML. Apart from analytics, the browser doesn’t load a single JavaScript file.
The transitions between pages are plain CSS view transitions, with no router script. The fonts are self-hosted, and the fallback font is scaled to the measurements of Fraunces, the headline font, so the headline stays put when the real font arrives. nginx serves the finished files, behind Traefik.
Astro next to the rest of the stack
Astro isn’t the right tool for everything. For a web app with logins, forms and a lot of state, I’d pick Angular, with a NestJS backend behind it. The split I’d suggest: the marketing site in Astro, the app in Angular, both in TypeScript. When a page needs something interactive, like a price calculator or a booking widget, Astro loads it as an island on that one page and leaves the rest as plain HTML.
How we can work together
Questions
Why Astro and not WordPress?
An Astro site is built into plain HTML files before it goes live. There is no database and no plugins on the server that need security updates, and pages load fast because there is little to load. The trade-off: content is edited in files, not in a WordPress admin panel, unless you connect a headless CMS.
Why Astro and not Next.js?
Next.js fits apps with a lot of interaction behind a login. For a website that is mostly content, Astro sends far less JavaScript to the browser: this site gets by with a few small inline scripts. And for a web app, I'd use Angular with a NestJS backend instead.
Is Astro good for SEO?
Yes. Search engines get finished HTML, pages load fast, and you control every tag in the head. On this site that means a sitemap with the language versions of every page, structured data on every page, and a share image generated for each case study, service and technology page.
Can we edit the content ourselves?
The content lives in Markdown files that are checked against a schema when the site is built: a missing title or date stops the build instead of going live. If your team would rather edit in a browser, Astro can pull the content from a headless CMS.
What does it cost?
Pricing is on request: a fixed price or time and materials for projects, by the hour or as a monthly retainer for advisory. You get a written quote within 48 hours.