Skip to content
Cyan Orbit
Menu

Europe

Software Development Company in Germany

A remote development team for German buyers, working to GDPR and the BDSG, a signed AVV, EU hosting and the formal scoping process German procurement expects.

Get a project estimateTalk to a developer

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

Berlin skyline with the TV Tower above the Spree at blue hour
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

We build software for German companies as a remote team, with delivery scheduled inside CET or CEST business hours and specifications written up front rather than assumed. German buyers tend to run a more formal procurement process than we see elsewhere, and we plan for that from the first call rather than treating it as friction.

That starts with data protection: GDPR and Germany's BDSG govern how personal data is processed, a signed Auftragsverarbeitungsvertrag (AVV) is expected before any data changes hands, and EU hosting, often specifically a Frankfurt region, is frequently a hard requirement rather than a preference. It extends to legal obligations most markets don't have, like Impressum requirements on every website, and to a scoping process, Lastenheft and Pflichtenheft, that many German buyers expect a vendor to work within.

Services

Services for companies in Germany

Data processing runs on a signed AVV, not a verbal agreement

Under GDPR Article 28, a controller and processor need a data processing agreement in place before personal data is processed on the controller's behalf. German buyers treat the Auftragsverarbeitungsvertrag as a standard part of onboarding a vendor, not an optional extra, and often ask about hosting region and sub-processors as part of that agreement. We prepare AVV terms and hosting details before a project starts collecting real data.

Formal specifications come before the estimate

Many German buyers scope a project through a Lastenheft, the client's statement of requirements, followed by a Pflichtenheft, the vendor's detailed technical response describing how those requirements will be met. We work within that structure when a client expects it: a Lastenheft shapes our discovery questions, and our Pflichtenheft becomes the reference document for acceptance criteria and change control.

Accessibility and legal notices are not optional add-ons

Every commercial website operating in Germany needs an Impressum under the Digitale-Dienste-Gesetz, which replaced the TMG, and cookie consent handling that meets the TDDDG (formerly TTDSG). From June 2025, the European Accessibility Act, implemented in Germany as the BFSG, extends accessibility requirements to e-commerce, banking and other digital services. We build these into the site or app rather than adding them after a client flags a gap.

Compliance

Regulations we design for in Germany

  • GDPR and the BDSG

    GDPR sets the EU-wide baseline for personal data processing; the Bundesdatenschutzgesetz adds Germany-specific provisions, including on employee data. We design consent, data minimization and retention around both from the first data model.

  • Auftragsverarbeitungsvertrag (AVV)

    A signed data processing agreement is expected before we process personal data on a client's behalf. We prepare AVV terms, including sub-processor disclosure and hosting region, as part of onboarding.

  • EU hosting, often Frankfurt-region

    Many German buyers require personal data to stay in the EU, and specifically request a Frankfurt hosting region. We plan hosting as an architecture decision at discovery rather than defaulting to a US region.

  • Impressum under the Digitale-Dienste-Gesetz

    Every commercial website needs a legally compliant Impressum, now governed by the DDG after it replaced the TMG. We build the required disclosures into the site structure from the start.

  • Cookie consent under the TDDDG

    Formerly the TTDSG, this law requires explicit consent before setting non-essential cookies or similar tracking technology. We build consent banners and tracking logic to meet its requirements rather than relying on a generic cookie-notice plugin.

  • European Accessibility Act / BFSG

    Applying from June 2025, it extends accessibility requirements to e-commerce, banking and other digital services operating in the EU, implemented in Germany as the Barrierefreiheitsstärkungsgesetz. We build to WCAG-based standards so a covered product is compliant from launch.

Working together

Contracts, invoicing and working hours

  • EUR invoicing

    Contracts and invoices are issued in euros against agreed delivery milestones, with DATEV-compatible exports available where a client's accounting team requires them.

  • CET/CEST overlap

    We schedule standing ceremonies inside Central European time, adjusting for German public holidays and the summer time change, so daily collaboration doesn't depend on someone joining a call at an odd hour.

  • German-language delivery

    Specifications, UI copy and support can run in German where a client's team or end users need it, alongside English documentation for cross-border stakeholders.

  • Payment methods for commerce builds

    For checkout and billing systems we integrate SEPA direct debit, PayPal, Klarna and giropay's successor schemes, which German customers expect alongside card payments.

  • Contracts and IP

    We sign an NDA before reviewing your Lastenheft, code lives in a repository you control from the first commit, and IP assigns to you on payment.

Industries

Industries we build for

FAQ

Frequently asked questions

Do you sign an Auftragsverarbeitungsvertrag before starting a project?

Yes. We prepare AVV terms, including hosting region and sub-processor disclosure, as part of onboarding for any project that involves processing personal data on your behalf, in line with GDPR Article 28.

Can you host our application in a Frankfurt data center?

Yes. EU hosting, including Frankfurt-region infrastructure, is something we plan as an architecture decision at discovery rather than defaulting to a different region and revisiting it later.

Do you work from a Lastenheft or expect us to write a Pflichtenheft ourselves?

Either. If you provide a Lastenheft describing your requirements, we write the Pflichtenheft that details how we'll meet them and use it as the reference for acceptance criteria. If you'd rather we draft both documents from discovery, we do that instead.

Does the Impressum requirement apply to an internal tool or only public websites?

The Digitale-Dienste-Gesetz's Impressum requirement applies to commercial websites and services offered to the public, not to internal tools with no external audience. We confirm which parts of your system count as public-facing during discovery so the disclosure ends up in the right place.

What changes for us because of the European Accessibility Act from June 2025?

If your product is e-commerce, banking or another covered digital service offered in the EU, it needs to meet accessibility requirements implemented in Germany as the BFSG. We build to WCAG-based standards during development, covering things like keyboard navigation and screen-reader labeling, rather than retrofitting them after a compliance review.

Start a project with a team that plans around your working hours

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 project estimateTalk to a developer
Get a free project estimate