Web Development Company in Berlin

Commerce depth and country count set a Berlin web budget, while the front-end framework barely registers. Builds run as a focused marketing or content site at Berlin rates over six to twelve weeks, covering a Next.js or Nuxt front end, a headless CMS, BFSG-aligned accessibility, a TTDSG-compliant CMP, and an Impressum and Datenschutzerklaerung tuned to the current Telemediengesetz requirements, a mid-complexity commerce or SaaS web platform with Shopify Plus or commercetools, internationalisation, SEPA and Klarna checkout, and Trusted Shops integration, or a Zalando-scale or Idealo-scale platform with custom commerce, headless personalisation, multi-country logistics, and BaFin or Bundesnetzagentur supervised content. Berlin rates sit slightly below Munich on senior engineering supply and considerably below London or Zurich. We give fixed-fee proposals rather than open time and materials estimates.

The Barrierefreiheitsstaerkungsgesetz (BFSG) implements the EU Accessibility Act in Germany and applies to private sector B2C web platforms above the small enterprise threshold (broadly more than 10 employees and more than EUR 2M annual turnover) operating in scope sectors including e-commerce, banking, e-books, transport, telecoms, and audiovisual media services. From June 28, 2025, in-scope sites must meet WCAG 2.1 AA in practice, publish an accessibility statement, offer a feedback channel, and be prepared for Marktueberwachungsbehoerden inspections. Fines reach EUR 100,000 per violation, and German consumer associations have telegraphed test cases for the first wave of enforcement. We ship sites with semantic HTML, full keyboard navigation, ARIA used only where native semantics fall short, contrast audits, dynamic type, screen reader testing in NVDA and VoiceOver, and a published BFSG conformance statement before launch.

TTDSG (Telekommunikations-Telemedien-Datenschutz-Gesetz) requires explicit, granular, opt-in consent before any non-essential storage or access on a user device, which covers nearly all analytics, advertising, and many functional cookies and SDKs. Germany is one of the strictest enforcers in Europe, with all 16 Land DPAs plus the federal BfDI actively investigating consent patterns. The Berlin Beauftragte fuer Datenschutz und Informationsfreiheit has issued public guidance rejecting consent walls, pre-ticked boxes, dark patterns, and consent banners that do not present a 'reject all' option at parity with 'accept all'. Our standard implementation uses Usercentrics, Cookiebot, or a self-hosted CMP with per-purpose consent, no tag firing before user choice, a consent ledger documenting what was collected when, granular withdrawal, and a Datenschutzerklaerung that lists every processor by name, purpose, legal basis, and retention period.

Yes. BITV 2.0 (Barrierefreie-Informationstechnik-Verordnung) is the German federal accessibility regulation that requires WCAG 2.1 AA conformance for Bundesverwaltung websites, mobile apps, and intranets, and it has been in force since 2019 with regular updates. Most Land governments mirror BITV 2.0 in their state-level regulations. Our public sector engagements produce a BITV 2.0 conformance report, a published Erklaerung zur Barrierefreiheit (accessibility statement) with the required content elements, a Schlichtungsstelle des Bundes contact path, and an Article 30 record of processing activities. We coordinate with the Ueberwachungsstelle des Bundes fuer Barrierefreiheit von Informationstechnik (BFIT-Bund) testing patterns and align with the Online-Zugangsgesetz (OZG) Service-Standard where the project sits inside the federal digital service catalogue.

For most German DTC brands shipping under EUR 50M annual GMV, Shopify Plus with a Next.js headless storefront is the right default, paired with Klarna, SEPA Lastschrift, PayPal, Apple Pay and Google Pay, Trusted Shops integration, and a Hermes, DHL, DPD, or GLS shipping orchestration layer. For Mittelstand B2B, Spryker or commercetools (Munich-headquartered, deployed at Zalando, Lufthansa, and others) handle complex pricing, account hierarchies, and ERP integration cleanly. For Zalando-scale custom commerce we build on commercetools or a bespoke stack on AWS eu-central-1. Every implementation includes Verpackungsgesetz reporting touchpoints, German invoice formatting compliant with Section 14 of the Umsatzsteuergesetz, Widerrufsbelehrung text aligned with current case law, and a Datenschutzerklaerung covering payment processors, fulfilment partners, and marketing tools by name.

Default hosting is AWS eu-central-1 in Frankfurt as the primary region, eu-central-2 in Zurich for disaster recovery, Azure Germany West Central for Microsoft-aligned enterprises, and GCP europe-west3 in Frankfurt for analytics and Firebase. For consumer marketing sites we use Vercel and Netlify with Frankfurt edge configured explicitly. For sovereign or sensitive workloads we evaluate Hetzner Cloud in Falkenstein or Nuremberg, IONOS in Karlsruhe, and T-Systems Open Telekom Cloud for govt-adjacent projects requiring BSI C5 attestation. CDN defaults to Cloudflare with EU-only routing or Fastly with the EU enclave. All data flows are documented in a Verzeichnis von Verarbeitungstaetigkeiten under Article 30 of the GDPR, and any cross-border transfers are covered by Standard Contractual Clauses plus a transfer impact assessment your DPO can sign.

The EU Digital Services Act (DSA) applies in full to platforms hosting user-generated content, marketplaces, and very large online platforms (VLOPs), with German enforcement coordinated through the Bundesnetzagentur as the Digital Services Coordinator. Our DSA-relevant builds include a published notice and action mechanism, a clear point of contact for authorities, transparency reporting endpoints, and an internal complaint handling system. The EU Cyber Resilience Act, adopted in 2024 and entering full enforcement progressively, applies to products with digital elements and adds vulnerability handling and software bill of materials obligations. For SaaS web platforms in scope we ship an SBOM in CycloneDX or SPDX, a coordinated vulnerability disclosure policy, and a security.txt at the standard well-known path. BSI Grundschutz mapping is added when the client sits inside or adjacent to critical infrastructure (KRITIS).

A focused marketing or content site ships in six to twelve weeks. A mid-complexity commerce or SaaS web platform with Shopify Plus or commercetools, internationalisation, German payment localisation, and Trusted Shops typically takes twelve to twenty-four weeks. Idealo or Check24 scale price-comparison platforms with regulated content, BaFin or Bundesnetzagentur supervision, and large catalog ingestion pipelines range from twenty-four to forty weeks. Add four to eight weeks for a full BFSG conformance audit and remediation if accessibility was not scoped from the start, two to four weeks for BITV 2.0 public sector documentation, and two weeks for DSA notice-and-action implementation where user-generated content is in scope. We ship to these durations with fixed scope, a published critical path, and German-language stakeholder communication on demand.