Partner with Remote

Offer global employment and payroll to your customers, inside your own product, without building the compliance layer yourself.

Who this is for

You embed Remote's hiring and payroll product into your platform and offer it to your customers as your own. Your users hire, onboard, and pay people abroad without ever leaving your product.

This is a white-label partnership, not a self-serve integration. If you want to read data out of Remote or sync records into an existing HR stack, see "Not an embedded partner?" below.

What you get

• One integration, global coverage. Offer employment and payroll to your customers across the countries Remote operates in.
• Compliance handled. Remote is the employer of record and manages local contracts, tax, and payroll rules. You surface the product; Remote carries the legal and compliance weight.
• Your brand, our infrastructure. The hiring and payroll experience lives inside your product under your name.

There's more on the pitch, coverage, and commercial model on the Remote Embedded page.

How partnering is different

Embedded and white-label access is a commercial, white-glove motion. It does not start in the self-serve sandbox.

• You get OAuth client credentials provisioned for your partnership, not the public sandbox token.
• Provisioning happens through a discovery call with a partner solution consultant on the partnerships team. They scope your use case, the countries you need, and the commercial terms before issuing credentials.
• Once you're set up, the build guides on developer.remote.com apply. The surface you choose (API, MCP, SDK, CLI) is only how you fetch it; the underlying capabilities are the same.

Talk to partnerships

Start with a discovery call. The partnerships team will scope your use case and provision your credentials.

• Talk to partnerships to start a discovery call.
• See the Remote Embedded page for the full value proposition and coverage.

After the call, once you sign and return our NDA, you will receive two emails from Remote. The first grants access to this developer documentation hub. The second grants access to your CLIENT_ID and CLIENT_SECRET keys via 1Password.

⚠️ The 1Password access to your CLIENT_ID and CLIENT_SECRET keys is only valid for 7 days. Please be sure to save your credentials in a secure location.

Not an embedded partner?

If you're a data-sync or ecosystem partner (reading Remote data or syncing records into another system, rather than reselling Remote as your own product), you don't need this funnel. Head to Find Your Path to pick the build guide that fits your integration. Those flows use a lighter credential path and don't require a commercial partnership.