Astro developer in Copenhagen

Independent Astro.js developer for Copenhagen fintechs, Medicon Valley life-sciences firms, and maritime businesses. Zero-JS static architecture, Datatilsynet/Cookiebekendtgørelsen compliance, and CVR disclosures.

Astro developer

Migrate from WordPress to Astro in Copenhagen

Many businesses in Copenhagen run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.

  • PageSpeed 95-100

    Static HTML with zero JavaScript. Faster than any WordPress solution.

  • SEO-safe migration

    URL mapping, 301 redirects, Google rankings preserved.

  • Cloudflare Pages hosting

    Global CDN, free SSL, instant deployments. Hosting costs near zero.

Copenhagen (København) anchors the Øresund technology and industrial corridor, uniting pharmaceutical and biotechnology leaders in Medicon Valley (across Ørestad, Ballerup, Bagsværd, and Hellerup), sustainable architecture and urban-tech companies around BLOXHUB on Slotsholmen/Christians Brygge, financial technology scale-ups at Copenhagen FinTech Lab, maritime shipping and clean-energy operators in Nordhavn and Indre By, and university spin-outs around DTU (Technical University of Denmark) and the IT University of Copenhagen (ITU). I build and migrate fast, low-carbon, compliant web platforms using Astro, working as a solo software developer in Gdynia, Poland, collaborating with your Copenhagen team entirely in writing.

#Why Copenhagen fintech, life sciences, and green-tech teams build with Astro

For Copenhagen enterprises and scale-ups, a public website, investor relations hub, or pan-Nordic product platform has to satisfy three strict engineering criteria: instant mobile responsiveness, verifiable security and privacy, and low data-transfer weight.

Running a content-focused website on a legacy monolithic CMS or a full React Single-Page Application (standard Next.js) creates unnecessary technical debt:

  • Client-side JavaScript bloat and CPU drain: A full React SPA ships hundreds of kilobytes of framework JavaScript plus a duplicate JSON copy of your page text (__NEXT_DATA__ or RSC payload) on every route. Every visitor’s phone or laptop must parse and hydrate that bundle just to read static articles or compliance tables.
  • Database and plugin attack surface: Monolithic CMS setups execute server-side database queries on every uncached request and expose login endpoints and third-party plugins that require constant security patching.

Astro solves both issues at compile time by rendering your pages to zero-JavaScript static HTML and scoped CSS by default, while mounting interactive React, Vue, or Svelte islands (client:visible or client:idle) only where genuine client-side state is needed.

#Content Security Policy (CSP) hardening and pan-Nordic currency/locale islands

For Copenhagen fintechs, pharmaceutical portals, and Nordic SaaS companies publishing across Danish (da-DK), Swedish (sv-SE), Norwegian (nb-NO), Finnish (fi-FI), German (de-DE), and English (en), Astro enables a clean architectural boundary between static regulatory prose and interactive calculators:

---
// src/pages/da/loesninger/[slug].astro
import BaseLayout from '../../../layouts/BaseLayout.astro';
import RegulatoryComplianceMatrix from '../../../components/RegulatoryComplianceMatrix.astro';
import NordicRoiIsland from '../../../components/react/NordicRoiIsland.tsx';
import { getSolutionBySlug } from '../../../lib/cms';

const { slug } = Astro.params;
const solution = await getSolutionBySlug(slug, 'da-DK');
---

<BaseLayout title={solution.seoTitle} description={solution.seoDescription} lang="da">
  <main class="solution-container">
    <h1>{solution.headline}</h1>
    <p class="lead">{solution.summary}</p>

    <!-- Static HTML: 0 KB client JS, strict CSP compatible -->
    <RegulatoryComplianceMatrix standards={solution.standards} />

    <!-- Isolated React Island: hydrates only when scrolled into the viewport -->
    <NordicRoiIsland
      client:visible
      defaultCurrency="DKK"
      currencies={['DKK', 'SEK', 'NOK', 'EUR']}
      tiers={solution.tiers}
    />
  </main>
</BaseLayout>

Because static sections ship zero inline hydration state, we can enforce strict HTTP Content Security Policy (CSP), Strict-Transport-Security, and Permissions-Policy headers at the edge while meeting Google’s official Core Web Vitals “Good” thresholds in real-user CrUX telemetry:

  • Largest Contentful Paint (LCP): up to 2.5 s
  • Interaction to Next Paint (INP): up to 200 ms
  • Cumulative Layout Shift (CLS): up to 0.1

#Danish statutory and regulatory compliance built into your Copenhagen Astro stack

A commercial website operated by a Danish Aktieselskab (A/S), Anpartsselskab (ApS), or Partnerselskab (P/S) headquartered in Copenhagen must comply with specific Danish statutory acts alongside European Union regulations.

#1. Datatilsynet (Databeskyttelsesloven) and Cookiebekendtgørelsen (BEK nr. 1148)

In Denmark, personal data processing is governed by the GDPR and the Danish Data Protection Act (Databeskyttelsesloven - Lov nr. 502 af 23. maj 2018), enforced by Datatilsynet. Storing or accessing information on a user’s terminal equipment (cookies, localStorage, and tracking pixels) is regulated under the Cookie Executive Order (Cookiebekendtgørelsen - Bekendtgørelse nr. 1148 af 9. december 2011), supervised by the Danish Business Authority (Erhvervsstyrelsen) in coordination with the Danish Consumer Ombudsman (Forbrugerombudsmanden under Markedsføringsloven).

In my Astro builds for Copenhagen companies:

  • Zero non-technical scripts before prior opt-in: Analytical, statistical, and marketing scripts remain completely inert in the HTML until the visitor grants explicit, granular consent via your Consent Management Platform (such as Cookie Information or Usercentrics/Cookiebot, configured with symmetrical accept and reject buttons on the first layer).
  • Self-hosted .woff2 web fonts: Following Datatilsynet rulings on third-party US cloud transfers, I never load fonts from fonts.googleapis.com. All web fonts (with complete Nordic glyph coverage for æ, ø, å, ä, ö) are subsetted and served directly from your first-party European origin.

#2. Mandatory Danish corporate disclosures (Selskabsloven & E-handelsloven § 7)

Under the Danish Companies Act (Selskabsloven) and Section 7 of the Danish E-Commerce Act (E-handelsloven - Lov nr. 227 af 22. april 2002), every commercial website operating from Denmark must make core corporate identification data permanently and easily accessible.

I wire a schema-validated global footer and legal layout that renders server-side across all language versions (da, sv, nb, fi, de, en):

  • Full registered company name and legal form (A/S, ApS, P/S).
  • Registered physical address in Copenhagen (København K, V, Ø, N, S, SV, NV or Greater Copenhagen).
  • 8-digit CVR-nummer (Det Centrale Virksomhedsregister) registered with Erhvervsstyrelsen.
  • Direct electronic contact address and VAT registration (SE/Momsnummer: DK + 8 digits).
  • Competent supervisory authority details where applicable, such as Finanstilsynet (the Danish Financial Supervisory Authority) for regulated Copenhagen fintechs or Lægemiddelstyrelsen (the Danish Medicines Agency) and ENLI compliance boundaries for Medicon Valley pharmaceutical and medical-device portals.

#3. Danish Accessibility Act (Lov nr. 801) and Hybrid MitID / MobilePay Endpoints

Denmark transposed the European Accessibility Act through Lov om tilgængelighedskrav for produkter og tjenester (Lov nr. 801 af 7. juni 2022), in force since 28 June 2025 and supervised by Sikkerhedsstyrelsen and sector authorities, alongside public-sector accessibility rules (Lov nr. 692) overseen by Digitaliseringsstyrelsen.

When I engineer your Copenhagen Astro platform:

  • Every page uses semantic HTML5 landmarks (<header>, <nav>, <main>, <article>, <footer>), native <details>/<summary> accordions, and keyboard-verified Astro Islands meeting WCAG 2.1 Level AA / EN 301 549.
  • Where server-side execution is required, such as authenticated B2B/citizen portals using the Danish MitID broker (NemLog-in3 OIDC/SAML), automated company autofill against the Virk / CVR API, or checkout webhooks for MobilePay, Dankort / Nets Easy, and Stripe, I isolate those routes as hybrid Astro server endpoints (export const prerender = false) while keeping 95%+ of the site purely static.

#How a project with me runs

I am Mariusz Szatkowski, an independent software developer based across the Baltic Sea in Gdynia, Poland, operating in the exact same Central European Time zone (CET/CEST) as Copenhagen. When your Copenhagen team hires me, you work directly with the developer writing the Astro and TypeScript code, without agency middlemen.

  • Asynchronous written delivery for Copenhagen teams: I work without video calls, phone calls, or on-site meetings. All Copenhagen route tables, CMS schema contracts, and pull request notes are shared in writing via GitHub, GitLab, Linear, or email. Your Copenhagen developers and product leads get a clean, searchable written record they can review asynchronously.
  • Visual design boundary on Copenhagen builds: Your Copenhagen design team or studio provides all Figma layouts and brand assets. Your in-house designer or Copenhagen design studio supplies the Figma files (or I replicate your existing visual layout during a migration from Umbraco, WordPress, Webflow, or Next.js), and I implement them into clean, accessible Astro and Tailwind CSS code.
  • What your Copenhagen team sends to begin:
    1. Your current Copenhagen domain URL (if migrating) or a written scope brief (for a greenfield build).
    2. Access to your Copenhagen Figma workspace or current Git repository.
    3. Your preferred CMS setup (Markdown/MDX, Umbraco Heartcore, Sanity, Storyblok, Contentful, Strapi, or headless WordPress) and target Nordic/international locales.
    4. Any required MitID, CVR lookup, MobilePay/Stripe, or CRM integration endpoints.

I reply in writing on working days and deploy every milestone to a private staging URL so you can verify Core Web Vitals, SEO metadata, and Danish statutory disclosures before production cutover.

#Start your Astro project in Copenhagen

#Umbraco Heartcore, Sanity, and Storyblok Migrations in Greater Copenhagen

Many Copenhagen enterprises manage content in Umbraco (widely adopted across Denmark), Sanity, Storyblok, or Contentful, or maintain legacy Next.js and WordPress portals across .dk, .se, .no, and .com domains. Using Astro’s Content Layer API, I connect your existing headless CMS directly to typed .astro templates, cutting build times, removing client-side React hydration overhead, and preserving 100% of your Nordic SEO equity through automated 301 redirect verification.

If you want to launch a fast Astro website or migrate an existing Copenhagen platform away from a slow monolithic CMS or heavy SPA, send me your current URL, target languages, CMS setup, and timeline via my contact page. Your initial written Copenhagen technical estimate is free, and I reply in writing on working days.

See also in Denmark

Need this service: Astro developer in Copenhagen?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base