FOR E-COMMERCE AGENCIES & INTEGRATION TEAMS
Cut your client's SaaS bill. Keep the revenue.
When a client is paying per order to BaseLinker or ChannelEngine, you can build them a self-hosted OpenLinker system they own instead. They stop renting; you bill the implementation, the hosting and the maintenance — recurring revenue that's yours.
Your client saves. You get paid. Nobody rents.
WHAT YOUR AGENCY SELLS
A whole service line, not a referral fee.
OpenLinker is Apache 2.0 and free. The value you sell around it is yours to price, brand and keep.
-
Implementation.
Deploy OpenLinker for the client, connect their shop, marketplaces, shipping and invoicing, and migrate them off the rented SaaS. Billed as a project.
-
Client-specific adapters.
Build the integrations each client actually needs against a stable SDK — without rebuilding order ingestion, retries or identifier mapping. Billable hours, not core maintenance.
-
Managed hosting.
Host it yourself, or resell OpenLinker-managed hosting under partner terms. Either way you set the client price and keep the margin.
-
Maintenance & support.
An ongoing retainer: updates, monitoring, new channels as the client grows. Recurring revenue while their software bill drops.
-
White-label delivery.
Deliver it under your own brand. The client sees your agency, not us.
-
Your pricing, your margin.
OpenLinker never publishes a resale price or approaches your client. What you charge is between you and them.
THREE WAYS TO RUN IT
Run it all yourself, or let us carry the parts you'd rather not.
Nothing here is mandatory. OpenLinker Core is free and self-hostable; the services below exist for when you want backup.
Run everything yourself.
You provision the infrastructure, deploy, monitor, back up, upgrade and support. OpenLinker earns nothing recurring — no subscription, no licence key, no mandatory contract. That's a feature, not a gap.
Keep the infra, add our backup.
You run the servers, but buy the parts you want contractual weight behind: an SLA, code-level escalation, adapter maintenance, architecture review.
Resell OpenLinker-managed hosting.
We operate a fixed-capacity hosted environment under partner terms; you package it into your service. Your client pays you, you pay us, and you stay the client-facing provider.
The services in detail — Managed hostingSLAIntegration assurance
Ready to go official? Partner programme →
NO CHANNEL CONFLICT
We back the agency. We don't compete with it.
OpenLinker does not use access to a client you brought us to pitch competing implementation, hosting or support. The client relationship and the retail price stay yours.
Your client. Your service. Your margin.
- You set your retail pricing — we never publish a resale price.
- Self-host, or buy our hosting — your choice, reversible either way.
- We don't undercut you on a client you registered with us.
- Support access is never turned into a sales channel.
- You stay partner of record unless the client asks otherwise.
- The code is Apache 2.0 — nothing locks you (or your client) to us.
FAQ
Straight answers
Will OpenLinker compete with us for our client?
No. We don't use access to a client you brought us to offer competing implementation, hosting or support. You control the implementation, the managed-service package, the retail price and the relationship. We can provide optional hosting, SLA and integration assurance behind your delivery — never in front of it. We serve merchants directly only where there's no agency at all.
Do we have to pay OpenLinker anything?
No. OpenLinker Core is Apache 2.0 and free — self-host it, support it, patch the adapters, and you owe us nothing. You only pay us if you choose to buy managed hosting, an SLA or integration assurance to put behind your service.
Can we resell your hosting and SLA with our own margin?
Yes. Managed hosting, SLA and integration assurance are available under confidential partner terms. You package them into your client offer, set the price, and keep the margin. OpenLinker invoices you; you invoice the client.
Can we white-label it?
Yes — deliver it under your own brand. Note that where OpenLinker issues an invoice, signs an SLA or operates infrastructure, its legal identity may still need to appear in contracts or subprocessor lists, depending on the arrangement.
How long does it take to add a marketplace we need?
You build the adapter against @openlinker/plugin-sdk — the order queues, retries and identifier mapping are already built, so you implement only the ports that marketplace needs. How long depends on the marketplace's API; we don't quote a fixed number we can't back.
It's alpha. Can we really put a client on it?
Honestly: it's pre-1.0. It's live across shops, marketplaces, shipping and invoicing, with real integration tests — but expect gaps and a fast-moving codebase. The agencies best served today are those comfortable running a parallel period and writing the odd missing adapter. Talk to us about a specific client stack before you commit one.
ASSESS A CLIENT STACK
Bring us one client's stack.
Tell us what the client runs today and what it's costing them. We'll tell you honestly whether OpenLinker fits — and what building it would take.
Or start with the code.
The repo is public, Apache 2.0. The dev stack comes up with a single Docker command.