--- title: "White-label EOR or build your own? How platforms choose" description: "Build your own EOR only if you already run employing entities where your customers hire and employment is your product. Otherwise partner. The three tests that decide it." canonical: https://www.teamed.global/insights/white-label-eor-vs-building-your-own-eor datePublished: 2026-10-15T12:00:00.000Z --- **Build your own EOR only if you already run employing entities where your customers hire and employment is your product. Otherwise partner: a white-label EOR gives you the service without the entities.** That is the whole decision in two sentences. The rest of this page is what each side involves. Test your own situation against it before you commit engineering time or a legal budget. This page is for platforms and agencies that want to offer employer of record to their own customers. It is for those who have not yet decided whether to build it or put a provider behind their product. If you have already chosen to partner, the next decision is which model. [White-label or API-embedded](/insights/offering-eor-through-your-own-platform) covers that. If you are an employer buying EOR directly, the [employer of record](/employer-of-record) pages are the ones you want. ## What does building your own EOR take? An employing entity in every country your customers hire in. And everything that entity has to do to employ someone lawfully there. In each of those countries you need a registered company that can act as the employer. You need employer registrations with the tax authority and the social-security system. You need employment contracts written under local law. You need payroll run on the local calendar, with the statutory filings that go with it. You need ongoing compliance as the law changes. And you need a person who can answer the hard questions when a hire, a leave or an exit does not fit the template. Two examples make the list concrete. In Germany, a worker cannot be placed with a client until the employing entity holds an AÜG permit. That permit sits under the Act on Temporary Agency Work. It is a condition of placing anyone at all, and it does not lift the Act's limits on each placement. (Teamed's German entity holds that permit.) In Mexico, the 2021 labour reform banned the subcontracting of personnel. A provider of specialised services has to be on the REPSE register, the national register of specialised service providers. (Teamed is registered on REPSE.) Every country has its own version of these conditions, and they change. What this page will not give you is a cost or a timeline for setting up an entity. Both vary by country and by what you are setting up. A single figure would be wrong for most readers. The [country hiring guides](/country-hiring-guides) carry the detail country by country. Teamed's employer of record service reaches 187+ countries. ## Who is the legal employer? If you build, you are. Your entity signs the employment contract. Your entity runs payroll and files with the authorities. Your entity answers for a dismissal that goes wrong. If you partner, the provider is the legal employer. With Teamed, that is Teamed, through its local employing entity. The [legal employer](/glossary/legal-employer) is the company named on the employment contract. This is why no provider can honestly promise that your customer will never see its name. Your customer's employee signs a contract that names the provider's entity. The screens can be yours. The relationship can be yours. The brand your customer sees can be yours. The name on the contract is the provider's. ## What does a white-label EOR partnership give you? The service without the entities. The provider runs the local employing entity, the employment contracts, payroll and compliance underneath your product. Your customers hire through your screens under your brand. [White-label EOR with Teamed](/partners/white-label-eor) sets out each part of that arrangement. Two other arrangements sit beside it, and it is worth knowing which one a provider means. A co-branded or "powered by" model keeps the provider's name visible beside yours, so your customer knows who is behind the service. A reseller model has you sell the provider's own product, under its brand, for a commission. The [glossary term](/glossary/white-label-eor) sets the three out side by side. ## How do you decide between building and partnering? Three tests settle it more reliably than a build estimate. They are different from the three questions in the [white-label or API-embedded](/insights/offering-eor-through-your-own-platform) article. Those choose between two partner models once you have decided to partner. These choose whether to partner at all. **How many countries do your customers hire in?** One or two, where you already have an entity, and building is at least possible. A long tail across continents is different. You would be setting up and maintaining employing entities in countries where you may never employ more than a handful of people each. The entity count is the cost that scales, not the software. **Is employment your proposition, or a feature beside it?** If your customers come to you to employ people, the employment relationship is the product. You may want to own it end to end, entities included. If they come to you for banking, accounting, legal work, HR or staffing, employment is one more thing they need. A partner lets you add it without becoming an employment company. **Can you staff the hard questions?** A probation period that ends badly. A maternity leave in a country whose rules you have never read. A termination that needs a settlement agreement. Building means employing or retaining the people who answer those in every country. With Teamed, the team speaks directly with your clients where needed to confirm requirements and get hires moving. Ask any provider whether its people will do the same. One more distinction, because it catches people out. Embedded payroll for a single country is not global employer of record. A payroll product that lets your customers pay their own employees in one country, through their own entity, solves a different problem. Employing someone on their behalf in a country where they have no entity at all is the other problem. If your customers need the second, a single-country payroll partner will not give it to them. ## What Teamed offers platforms Teamed offers white-label EOR: it runs the full employer of record service behind a partner's own platform, through an API, with Teamed as the legal employer running contracts, payroll and compliance. The [white-label EOR page](/partners/white-label-eor) sets out what the partner gets, what the client sees, who speaks to the client when a hire needs a person, and how the commercial side works. ## When is building the right answer? When you already hold employing entities, and the licences that go with them, in the countries where your customers hire. And when employment is the product you sell. In that position a partner adds a layer you do not need. The people who answer the hard questions already work for you. For everyone else, the entities are the part worth not building.