Web Development · Germany

Web Development Company in Germany

Web projects built for German audiences, with the legal notices, cookie consent and accessibility requirements German visitors and regulators expect on every page.

NDA on request · Free, no-obligation estimate · Reply within one business day

Berlin skyline with the TV Tower above the Spree at blue hour
Wide monitor showing a website on a bright desk with an ergonomic chair
NDA before discovery
You own the code and IP on payment
Code in your repository from day one
A working demo every two weeks
Senior engineers do the work
How we work

A website operating in Germany carries legal obligations most markets don't: a compliant Impressum on every commercial site, consent handling for cookies and tracking that meets the TDDDG, and, from June 2025, accessibility requirements under the BFSG for covered digital services like e-commerce and banking.

We build those into the site structure from the first sprint rather than adding them as a compliance patch before launch, and deliver the German-language content alongside English where cross-border stakeholders need it, with review cycles scheduled inside CET/CEST hours.

Market

What buyers in Germany need from this work

  • Every commercial site needs a compliant Impressum

    The Digitale-Dienste-Gesetz, which replaced the TMG, requires a legally compliant Impressum disclosing who operates the site and how to contact them. We build the required fields into the site's footer and legal pages as a standard part of the build, not an afterthought template copied from another site.

  • Cookie consent under the TDDDG needs to actually block tracking before consent

    The TDDDG, formerly the TTDSG, requires consent before setting non-essential cookies or similar tracking technology. We build the consent layer to prevent tracking scripts from firing until consent is given, rather than a banner that displays while analytics loads regardless.

  • The BFSG extends accessibility requirements from June 2025

    Germany's implementation of the European Accessibility Act reaches e-commerce, banking and other covered digital services. We build to WCAG-based standards during development for any site that falls under BFSG's scope, so accessibility isn't a remediation project once enforcement begins.

  • BFSG picks up where BITV already left off for public bodies

    Public-sector sites have answered to BITV 2.0's WCAG-based requirements since 2011, so a council, ministry or public broadcaster site should already meet a similar bar. The BFSG extends comparable obligations to private-sector sites offering a covered digital service from June 2025, which is the newer and often overlooked half of the picture for a commercial client. We confirm which framework, or both, applies to a given site during discovery.

  • Consumer-facing prices need to show the VAT-inclusive total, not add it at checkout

    The Preisangabenverordnung expects a price shown to a consumer to already include VAT, with the exclusive figure reserved for clearly labelled B2B pricing. We build pricing and package pages to display the correct total for the intended audience rather than a headline number that changes once someone reaches checkout or a quote request.

Compliance we plan for

  • Impressum requirements under the Digitale-Dienste-Gesetz
  • GDPR and BDSG for personal data collected through forms and analytics
  • Cookie and tracking consent under the TDDDG
  • European Accessibility Act / BFSG for covered digital services from June 2025

How the engagement runs

Discovery confirms whether the site falls under BFSG's or BITV's accessibility scope and what legal disclosures the Impressum needs to cover. Design and build run in sprints with staging environments shared early, and review sessions are scheduled inside CET/CEST hours.

Invoicing is in EUR against delivery milestones, settled by SEPA transfer. The codebase and CMS stay under your control, and content can be delivered in German, English or both depending on your audience.

FAQ

Frequently asked questions

What does our website's Impressum need to include under German law?

The Digitale-Dienste-Gesetz, which replaced the TMG, requires disclosure of who operates the site, a contact address, and other identifying details depending on the business form. We build the correct Impressum content into the site's footer and legal pages as a standard part of the build.

Does our cookie banner need to block analytics before a visitor consents?

Yes. The TDDDG requires consent before setting non-essential cookies or similar tracking technologies, which means analytics and marketing scripts shouldn't fire until the visitor has given consent. We build the consent layer to enforce that rather than relying on a banner that's cosmetic.

Does the European Accessibility Act apply to our website from June 2025?

If your site is e-commerce, banking or another digital service the BFSG covers, yes. We build to WCAG-based accessibility standards for covered sites so the requirement is met from launch rather than through a remediation project once enforcement starts.

Can you build our site in German with an English version for other markets?

Yes. We structure content around a language field so German and English versions stay in sync as pages are added, rather than maintaining two separate sites that drift apart.

Can our hosting stay inside a German or EU region for GDPR reasons?

Yes. We select a Frankfurt or other EU hosting region during setup for clients with a data-residency preference, which is common among German enterprise and public-sector buyers, without it affecting performance for German visitors.

Do you build websites for German public-sector or enterprise organizations?

We've built sites that meet the Impressum, GDPR and accessibility expectations German enterprise and public-sector buyers require. Specific requirements vary by organization and procurement process, so we confirm them during discovery.

Is our public-sector site already covered by an accessibility law before BFSG applies?

Likely yes. BITV 2.0 has required WCAG-based accessibility from public bodies since 2011, ahead of the BFSG, which extends a similar bar to private-sector sites offering a covered digital service from June 2025. We confirm which framework applies to a given site during discovery rather than assuming BFSG is the only relevant standard.

Do we need to show VAT-inclusive prices on our website?

For consumer-facing pricing, yes, the Preisangabenverordnung expects the displayed price to already include VAT, while B2B pricing can be shown exclusive of VAT if it's clearly labelled. We build pricing and package pages to show the correct total for the intended audience rather than a figure that changes at checkout.

Get an estimate for web development in Germany

Share a few details about your project. A senior engineer reviews every request and replies with next steps, questions, and a rough budget range.

Get a free project estimate