DACH companies building engineering capacity in India usually compare two structures. With an Employer of Record (EOR), a local provider formally employs engineers whom the German company selects and manages. With a managed pod, a vendor employs and directs its own team and delivers work under a Werkvertrag or Dienstvertrag. Both can be legitimate. They allocate legal responsibilities very differently, and the choice should follow from which responsibilities your organisation wants to hold. This analysis compares the two from a German legal perspective.
Context: why this comparison is on the table
The question is driven by a persistent capacity gap. Bitkom counted 109,000 unfilled IT positions in Germany in 2025 and an average vacancy of 7.7 months per IT role. The 2026 survey shows 79,000 open positions, yet 78 percent of companies still report a shortage and 76 percent expect it to worsen. India offers depth: NASSCOM estimates that the Indian technology industry employed about 5.95 million people at the end of FY26, after 135,000 net additions during the year.
The German legal environment has not loosened. The Bundesagentur für Arbeit recorded around 622,000 temporary agency workers on 30 June 2025, all within a licence regime that becomes relevant as soon as a German company directs people employed by someone else. German customs reported that the Finanzkontrolle Schwarzarbeit checked 25,800 employers in 2025 and put the damage caused by undeclared work across all sectors at about EUR 675 million. Both models need to be read against that background.
The structural difference
In an EOR model, the EOR is the employer on paper and handles contracts, payroll, statutory contributions and local compliance. Day-to-day direction, task assignment, performance management and often hiring decisions remain with the German client. In legal terms, the client exercises the functions that §106 GewO associates with an employer, while another entity holds the employment contract.
In a managed pod, the vendor is employer and manager. The client defines requirements and accepts results, the vendor decides how its people do the work. The legal relationship between the companies is a service or work contract, not a provision of workers.
Comparison
| Dimension | Employer of Record | Managed pod |
|---|---|---|
| Who instructs the engineers | Client | Vendor (client steers via requirements and acceptance) |
| German contract type between companies | Typically a service agreement for employment administration, in substance close to provision of workers | Werkvertrag (§631 BGB) or Dienstvertrag (§611 BGB) |
| AÜG exposure | Structurally present, outcome depends on domestic link | Low if the operating model keeps direction with the vendor |
| Responsibility for results | Client | Vendor, with Abnahme in a Werkvertrag |
| IP chain | Engineer to EOR to client, requires explicit assignment by the EOR | Engineer to vendor to client, requires explicit assignment by the vendor |
| Data protection role of the provider | Often unclear, because engineers act on the client's instructions while employed elsewhere | Vendor as processor under Art. 28 DSGVO with SCCs |
| Tax presence risk in India | Needs review, because local staff work exclusively under the client's direction | Generally lower, because the vendor performs its own business |
| Management effort for the client | High, comparable to own employees | Lower, concentrated on requirements and acceptance |
AÜG: why the question does not go away
An EOR arrangement for a German client is structurally close to Arbeitnehmerüberlassung: one company employs, another directs and integrates. Whether the AÜG applies to engineers who work only from India depends on the domestic link. The Bundesagentur für Arbeit revised its Fachliche Weisungen in 2025 and now takes the view that purely online work from abroad lacks a sufficient domestic link for the licence requirement. Courts are not bound by this administrative view, there is no settled higher court case law, and business trips to Germany can create the domestic link. In addition, an Indian EOR could not obtain a German licence for activity from India under §3 Abs. 2 AÜG. The EOR model therefore relies on the territorial argument holding. A managed pod does not need that argument if the operating model is not Überlassung in the first place.
Intellectual property
Under Section 17 proviso (c) of the Indian Copyright Act 1957, the employer, here the EOR, is first owner of copyright in work created under a contract of service, absent agreement to the contrary. The German client receives rights only through an assignment by the EOR, which must comply with Section 19 (written form, and explicit duration and territory to avoid the default rules). EOR standard terms often address this, but it should be verified rather than assumed. The same requirement applies to a managed pod vendor. The difference is practical: a pod vendor's business is the delivery of work products, so the rights clause is a central part of its contract.
Data protection
In a managed pod, the roles are conventional: the client is controller, the vendor processor, with an AVV under Art. 28 DSGVO and SCCs (module 2) for the transfer. In an EOR model, the engineers act on the client's instructions but are employed by a third party in a third country. The client must ensure that its own technical and organisational measures, confidentiality commitments and transfer documentation cover these individuals, and must clarify in which role, if any, the EOR processes client data. This is solvable, but it is frequently overlooked.
Tax and Indian labour law
When local staff work exclusively for a foreign company and under its direction, tax authorities may examine whether that company has a taxable presence in the country. This depends on facts and on the Germany India double taxation agreement and requires advice from tax specialists in both countries. Indian labour law also continues to apply to the employment relationship, including the Labour Codes that took effect in November 2025. With an EOR, the EOR administers these obligations, but terminations, working conditions and disputes are driven by decisions of the client.
What both models have in common
Neither an EOR nor a pod replaces the client's own homework. In both cases, have the rights chain documented in writing, minimise access to personal data, plan visits to Germany deliberately and compare actual collaboration with the contract regularly. The difference lies in who directs the work day to day, and therefore who carries the risks typical of an employer.
Decision framework
- Do you want to manage individuals directly and build an in-house culture abroad? An EOR can fit, with careful review of AÜG exposure, IP assignment, data protection and tax presence.
- Do you want delivered results with limited management overhead? A managed pod under a Werkvertrag or Dienstvertrag fits better.
- Are visits to Germany planned regularly? That strengthens the domestic link and increases AÜG relevance for an EOR.
- Is a later transfer into your own entity planned? An EOR can be a bridge to an own subsidiary, a pod can be combined with a structured handover.
This article is general information and does not constitute legal or tax advice for your specific situation.
The choice between the two models is ultimately a choice about who directs the engineers and who carries the employer role. The niogod™ pod follows the managed model: engineers are employed in India by the vendor, directed by its own German-speaking Projektleiter and deliver under a Werkvertrag or Dienstvertrag, as described on the pod page. If you are weighing both options for next year, mapping them against the decision framework above before the first provider calls is time well spent.
Talk to niogod™
Planning engineering capacity in DACH? Book a 30-minute consultation with the niogod™ team.
Book consultation