COMPARISON
OpenLinker vs BaseLinker
Updated 2026. Open-source, self-hosted channel orchestration vs the SaaS that dominates the Polish e-commerce stack.
THE SHORT VERSION
The short version
| BaseLinker | OpenLinker | |
|---|---|---|
| Pricing model | Per-order + monthly base | Your hosting costs only |
| Source code | Closed | Open (Apache 2.0) |
| Data location | Their servers | Your servers |
| New marketplace | Their backlog or a paid module | Your team writes an adapter |
| Maturity today | Mature, battle-tested | Alpha, pre-1.0 |
| Self-hostable | — | ✓ |
OpenLinker makes sense when: BaseLinker bills are outpacing margin, customer data has to stay with you, or you need custom logic without waiting on someone else's backlog.
PRICING
Pay once for hosting. Not for every order.
BaseLinker prices per order (with a monthly base on most plans). Your cost scales linearly with sales — and that's before you add modules for shipping, invoicing, additional marketplaces.
OpenLinker is self-hosted. You pay exactly what your VPS or cloud costs. 3,000 or 30,000 orders per month costs almost the same in hosting — the bottleneck isn't order volume.
Illustrative math (3 years, 3,000 orders/mo)
| BaseLinker | OpenLinker | |
|---|---|---|
| Setup (one-time) | €0 | ~€1,200–3,500 (dev + hosting) |
| Year 1 (operational) | ~€2,800 | ~€420 |
| Year 2 | ~€2,800 | ~€420 |
| Year 3 | ~€2,800 | ~€420 |
| Total after 3 years | ~€8,400 | ~€2,400 (+setup) |
Numbers illustrative. BaseLinker: based on the public Standard plan (~€0.07/order) + base fee. OpenLinker: typical VPS ~€35/mo + one-time setup. Does not include BaseLinker add-on modules or developer hours configuring OpenLinker.
DATA OWNERSHIP
Your customer data stays with you.
BaseLinker stores order history, customer records, and integration config on their infrastructure. Convenient — until you ask "what happens if BaseLinker raises prices, gets acquired, or decides we're not a fit anymore?" OpenLinker runs on your hosting. PostgreSQL database, Redis queues, customer records — all yours. Backups too. What happens to that data is your decision.
CUSTOM LOGIC
When you need something BaseLinker won't build.
BaseLinker is SaaS with an open API and a module marketplace. Most scenarios are covered. When they're not, you have two options: ask support for a feature that lands in someone's backlog, or build your own integration against their API and maintain it yourself.
In OpenLinker there's a third option: write the adapter inside the same repo. The adapter compiles against `@openlinker/plugin-sdk`, inherits the core's plumbing (queues, retry, identifier mapping), and ships as part of your deploy. A custom carrier for one client? An adapter. A specific ERP webhook? An adapter. Per-channel pricing logic? A pluggable strategy.
WHERE BASELINKER STILL WINS
Honest: BaseLinker does things today that OpenLinker doesn't.
OpenLinker is in alpha. Pre-1.0. Our own ADRs say so explicitly. If you're considering switching, factor in:
- → Integration breadth. BaseLinker covers dozens of marketplaces, many shipping providers, multiple ERP integrations. OpenLinker today: Allegro + PrestaShop live, Subiekt nexo and InPost in progress, the rest planned.
- → Support & SLA. BaseLinker has paid support, Polish-language docs, a status page. OpenLinker has a solo maintainer and GitHub Issues. If a critical integration breaks at 11 PM, BaseLinker responds faster.
- → Edge-case maturity. Years of production use mean BaseLinker has already solved Allegro's weird API edge cases. A fresh OpenLinker adapter hits those for the first time.
- → Zero-code workflow. BaseLinker lets you customize flow through the admin panel. OpenLinker assumes customization means writing code (though the core ships ready).
Migrating from BaseLinker today makes sense if: you can live with fewer ready-made integrations, you have a developer (or agency partner) who'll write the missing adapters, and you see long-term value in ownership.
MIGRATION
What switching looks like.
- 01
Install OpenLinker
git clone,pnpm install,pnpm dev:stack:up. PostgreSQL, Redis, and a pre-configured PrestaShop come up in Docker. - 02
Configure live integrations
Allegro OAuth, PrestaShop API key. Cursor-based order ingestion starts from the moment of setup.
- 03
Sync products and mapping
OpenLinker builds a unified ID space (
ol_product_*,ol_order_*). Run alongside BaseLinker during the transition. - 04
Rewrite missing integrations
What do you use BaseLinker for that OpenLinker doesn't cover? Those adapters get written as plugins. Subiekt, InPost — in progress. The rest — on the roadmap or written by you.
- 05
Switch over
Disable the BaseLinker integration. Webhooks, OAuth tokens, callback URLs — all yours now.
FAQ
Frequently asked questions
How is OpenLinker priced compared to BaseLinker?
BaseLinker charges per order with a monthly base — your cost scales linearly with sales. OpenLinker is self-hosted; your only cost is your VPS or cloud hosting (typically around €35/month). Order volume doesn't affect the cost — 3,000 or 30,000 orders cost about the same.
Where is my customer data stored with OpenLinker vs BaseLinker?
BaseLinker stores order history, customer records, and integration config on their infrastructure. OpenLinker runs on your hosting — the PostgreSQL database, Redis queues, and customer records are all on servers you control, along with their backups.
Can I add custom marketplace integrations in OpenLinker?
Yes. OpenLinker's plugin SDK lets you write adapters in TypeScript that compile against @openlinker/plugin-sdk. The adapter inherits the core's plumbing — order queues, retry classification, identifier mapping — and ships as part of your deploy. No fork of the core required.
Is OpenLinker as mature as BaseLinker?
No. OpenLinker is in alpha, pre-1.0. BaseLinker has years of production use covering dozens of marketplaces and edge cases. OpenLinker today has Allegro and PrestaShop live, with Subiekt nexo and InPost in progress. If you need broad integration coverage immediately, BaseLinker still wins.
When should I choose OpenLinker over BaseLinker?
When BaseLinker bills are outpacing your margin, when customer data has to stay on your servers (GDPR, regulatory), or when you need custom logic without waiting on someone else's product backlog. Also a good fit when you have an in-house developer or agency partner who can write adapters for platforms not yet supported.
How does migration from BaseLinker to OpenLinker work?
Install OpenLinker via Docker (PostgreSQL, Redis, and a pre-configured PrestaShop come up with one command). Configure your Allegro OAuth and PrestaShop API key — cursor-based order ingestion starts immediately. Run OpenLinker alongside BaseLinker during the transition. Rewrite any missing integrations as plugins. Disable the BaseLinker integration when you're ready.
Try the version you own.
The repo is public, Apache 2.0. The dev stack comes up with a single Docker command.