PRICING
OpenLinker is free.
Apache 2.0. No licence fee, no licence key, no per-order fee, no seat limits. You pay for the server you already run. Hosting, support, and an SLA are available commercially — from us, or from an implementation partner.
THE PLEDGE
The code stays free. Forever.
No OpenLinker feature will ever move behind a paywall. There is no Enterprise edition, no licence key in the codebase, no capability unlocked by a subscription. The whole codebase is Apache 2.0 — read it, run it, modify it, resell it, including commercially.
This is not open core. We sell human work — implementation, hosting, support — not access to the code. That distinction is the reason you can build a business on OpenLinker without wondering which feature gets rented back to you at 1.0.
WHAT YOU ACTUALLY PAY
A server cost that doesn’t meter your orders
OpenLinker is a Docker stack: API, worker, PostgreSQL, Redis, admin UI. It fits on a 4 GB VPS. The figures below are illustrative — yours depend on your provider, your backups, and how large your catalogue is.
On the left, a bill that grows with every order. On the right, a server that grows only when it genuinely runs out of headroom.
Base.com
Business plan
$589 / mo
$21,204 over 3 years
- Per-order fee
- $0.49
- Software
- SaaS licence
- Support
- 24/7 included
- Integration updates
- the vendor’s job
- Your data
- on their servers
Self-hosted
you run it, or a partner agency does
$40 / mo
you save $19,764 over 3 years
- Per-order fee
- $0
- Software
- Apache 2.0
- Support
- GitHub, the community — or a partner agency
- Integration updates
- you, or a partner agency
- Your data
- on your server
Up to 100 orders a month, Base.com is free and a server is not. They win that row. Above it, the curves separate — and never meet again.
From roughly 150 orders a month, having OpenLinker run for you — by an implementation agency or by us — costs less than Base.com’s self-service Business plan. The agency sells a service cheaper than the SaaS the client would have paid for anyway.
Don’t want to run it yourself? If you have an implementation agency, you buy it from them. If you don’t, we’ll run it. Details below.
In fairness: Base.com’s Business plan already includes 24/7 support and their Enterprise includes an SLA. Our advantage isn’t support hours — it’s the shape of the bill, the adapter-currency guarantee, and where the data sits.
Our figures: a server at ~$40/mo up to 1,000 orders, ~$80 to 5,000, ~$250 at 10,000 and ~$500 at 25,000 — the Docker stack (API, worker, PostgreSQL, Redis, admin UI) on a correspondingly larger machine. Hosted: from $125/mo plus the server; support and the integration-currency guarantee are optional, so the final figure depends on the SLA and scope. That $125 is an illustrative equivalent of our 500 zł floor, not a guaranteed FX conversion. Enterprise is scoped per engagement. Base.com pricing as published on 2026-07-08, Business plan: “$99 fixed + $0.49/order”, charged on every order rather than on overage. We verified the formula’s shape against Base.com’s own PL calculator, where 279 zł + 0.99 zł × 5,000 = 5,229 zł — exactly the figure it displays. Freemium covers 100 orders, but also caps products at 1,000 and syncs hourly rather than in real time. Above 5,000 orders — or above 1M PLN monthly GMV, even at lower order counts — Base.com moves you to Enterprise with an individual quote. Net prices. Illustrative numbers, not a quote. Check Base.com’s current pricing →
THREE WAYS TO RUN IT
Yourself, with a partner, or with us
- 1 Yourself. You have a developer or a sysadmin. One Docker command, walk through the setup wizard, done. You pay us nothing, and you owe us nothing.
- 2 With an implementation partner. An e-commerce agency deploys and hosts OpenLinker for you. You pay them, not us. They can buy support from us and put you under an SLA they couldn’t offer alone.
- 3 With us. No partner yet? We’ll run and maintain OpenLinker for you — and when you find a partner, we hand the implementation over to them.
SUPPORT & SLA
This is what you can buy from us
The software is free. If you have an implementation agency, you buy implementation, hosting and support from them — that is their work and their revenue. If you don’t have one, we run it. The same goes for larger deployments, where a contract and an SLA are a condition of starting at all.
- Critical incident (production down)
- 24/7 intake, 4h response target
- Developer support
- Mon–Fri, 09:00–17:00 CET/CEST · next business day
- Managed hosting (when you have no agency)
- from $125/mo + the server
- Implementation & migration
- scoped per engagement
We maintain OpenLinker daily, so we see Allegro’s and ERLI’s API changes before they break a production shop. None of which an agency couldn’t do itself — the code is Apache 2.0. No fixed price list, because the scope genuinely differs between a 500-SKU shop and a seller running three Allegro accounts against an ERP.
FOR AGENCIES
A client who came through you stays yours
Implementation, hosting, support and the client relationship are yours — and that is your revenue, not ours. We don’t build storefronts. We run a shop only where it has no agency at all, and we hand the client over the moment it has one.
Instead of a promise, a rule you can check: if a client has an agency, we sell them neither hosting nor support. Maintenance and the retainer are yours, including the SLA you sign yourself. The adapters are Apache 2.0, so nothing ties you to us — and we have nothing to tie you with.
FAQ
Common questions
Is OpenLinker really free?
Yes. The code is Apache 2.0 — no licence fee, no per-order fee, no seat limits, no licence key. You pay only for the server you run it on. The only paid things are human services: managed hosting, implementation, and support with an SLA — and only if you want them.
Will any feature ever move behind a paywall?
No. We do not run an open-core model: there is no Enterprise edition, no subscription-gated capability, no licence key in the code. The Apache 2.0 grant on code we have already published is irrevocable. And if we ever changed our minds, anyone could fork the last Apache 2.0 release and carry it on without us — that backstop doesn’t depend on us keeping our word.
What SLA do you offer?
Critical incidents — production down — are taken 24/7, with a 4h response target. Developer support runs Mon–Fri, 09:00–17:00 CET/CEST, with a response by the end of the next business day. An SLA is a commercial service and requires a contract; the software itself stays free.
What does Enterprise include?
Enterprise is the whole thing run by us: managed hosting, support, an SLA (critical incidents 24/7, 4h response target; developer support Mon–Fri, 09:00–17:00 CET/CEST), and a contractual guarantee that the integrations keep up with API changes — when Allegro or ERLI moves, the fix lands in the OpenLinker release your contract covers. The price is set per engagement, because a deployment with three Allegro accounts and an ERP has little in common with a 500-SKU shop. Enterprise is for merchants without an implementation agency, and for larger deployments where a contract and an SLA are a condition of starting.
What does the server cost?
Up to about 1,000 orders a month the stack (API, worker, PostgreSQL, Redis, admin UI) fits on a 4 GB VPS — roughly $40 a month, plus backups. Past that it steps up: ~$80 to 5,000 orders, ~$250 at 10,000 and ~$500 at 25,000. The structural difference from SaaS is that it steps with the work, not with every order you sell.
Can you host OpenLinker for me?
Yes. If you work with an implementation agency, they will usually host it — and we can back them with code-level support and an SLA. If you don’t have a partner yet, we’ll run and maintain OpenLinker for you directly.
Do you compete with implementation agencies?
No. If a client has an agency, we sell them neither hosting nor support — implementation, maintenance and the retainer are the agency’s. We serve merchants who have no agency, and larger deployments that need a contract and an SLA. Nothing we sell is exclusive to us: the code is Apache 2.0, so an agency can host it, support it and patch the adapters itself.
Clone it, run it, star it.
The repo is public, Apache 2.0. The dev stack comes up with a single Docker command. The support conversation can wait until you’ve seen whether it works for you.