Lifetime license · self-hosted · not SaaS
Buy the platform once.
Run it forever.
Portlane is a self-hosted integration runtime: lifetime license, Python flows versioned in your repository, seven Docker engines on your servers. Your APIs, CRM, and ERP exchange through your Postgres — no subscription, no usage billing, no vendor cloud.
Lifetime license · your flows as source · installed on your servers
What is Portlane?
Portlane is a data integration runtime you install and operate yourself. You buy a lifetime license, deploy seven Docker engines on your infrastructure, and write versioned Python transforms. It is neither a SaaS iPaaS nor a full ESB: receive, route, transform, deliver, and supervise — inside your perimeter.
- Who it's for
- IT leaders and integrators who want to run their flows without a vendor control plane between them and their data.
- What it does
- Immediate or scheduled intake, routing, Python transforms, HTTP/JSON delivery, replay and supervision via the Tour de contrôle.
- What it is not
- No visual designer, no certified connector catalog, no pricing that climbs with volume.
Infrastructure you install, not access you rent.
You own it
One payment. Lifetime license. The software runs on your side, with no external control plane. You operate it for as long as you need it.
Real-time and scheduled intake
Webhooks received in seconds or scheduled calls to your APIs — your choice. Envelope contract, idempotency, and journal stay the same either way.
Versioned flows, not drawn ones
Your transforms are Python you can review like code, in your repository. No visual editor whose export is unreadable in review.
Reliable execution
Idempotency and traceability are built in from the start. When a flow breaks, you see where and you can resume it.
You stay in control. The vendor runs nothing in your estate.
Most integration platforms (iPaaS, cloud ETL) rent you access. Portlane sells you the software. You install it, operate it, and extend it in your environment. Your APIs, CRM, and ERP talk through your Postgres, with no SaaS control plane between you and your data.
Pay once. Use forever. No annual renewal tied to flow availability.
Transforms and flow configuration live in your Git repository. You review, change, and deploy on your schedule.
On your servers, in your data center or private cloud, inside your compliance perimeter.
Your flows, your data, your infrastructure. Nothing routes through a vendor cloud.
Portlane vs SaaS iPaaS: what changes
| Subscription iPaaS / ETL | Portlane |
|---|---|
| Monthly or annual fees | One-time lifetime license |
| Hosted by the vendor | Self-hosted on your servers |
| Flows drawn in a proprietary studio | Python flows, versioned in your repo |
| Pricing that follows usage | Unlimited flows, fixed cost |
| Leaving means rebuilding everything | Leaving means you keep the software |
Five commitments. No hidden subscription.
Built for engineers
Code you can test, split, and extend like the rest of your stack. Designed by people who run production flows — not sales demos.
A deliberate scope
Receive, transform, and deliver HTTP/JSON between your APIs, CRM, and ERP. No BPM, no MDM, no catalog to certify.
Reliable under real conditions
Idempotency, traceability, recovery after failure — the cases you already know on a bus or ETL.
Modular and extensible
Seven independent Docker engines, restartable one by one. Your Python transforms plug in without touching the core.
Ownership and control
One purchase, your flows, your Postgres, your infrastructure. The rules stay yours.
Tour de contrôle: supervision on your instance
The Tour de contrôle shows engine health, each envelope’s path, and what failed — on your instance, not ours. A failed flow can be replayed from the Tour de contrôle, and the action stays in the audit trail.
| Flow | Status | Last run | Duration |
|---|---|---|---|
| crm.contact.updated | Success | 2 min ago | 1.2s |
| erp.article.sync | Success | 4 min ago | 3.4s |
| gpo.price.inbound | Running | just now | 1.2s |
| facturation.egress | Failed | 8 min ago | — |
| stock.pull.horaire | Success | 11 min ago | 12.7s |
| commande.rejeu | Paused | 1 hr ago | — |
Your server. Your engines. Your data.
Not a service bus to wire by hand. A chain of engines on your side: data enters, is received, routed, transformed, delivered. If something breaks, you replay it.
See how it is set upFrom source system to target
Three zones, one direction. Engines in the middle do the work. Central memory carries the trail of every envelope.
- 01Sources
Where data is born: a partner that sends, a system you poll, a business event. APIM holds the door. The listener creates the envelope (direct push or handed off by pooling).
- 02Engines
Routing, transform, delivery. Each step resumes work already started. If a link restarts, the envelope is not lost.
- 03Targets
Where your organisation consumes the result: business tool, partner, reference store. The data stays with you.
An envelope does not vanish into the void. It waits in a queue until processed.
Reprocessing the same envelope does not corrupt the target. The contract is designed for that.
A failure is relaunched from the Tour de contrôle, on your instance, with an audit trail.
How much does Portlane cost?
Portlane is sold on quote, not self-serve. You license once for lifetime use in your infrastructure: a fixed invoice, with no volume meters and no annual SaaS renewal holding your flows hostage.
Acquisition model: software you own and operate. Maintenance, updates, and professional services are scoped in your quote.
How many active engines you deploy — the classic lever of on-prem ESBs.
The flows, transforms, and integrations in your perimeter, sized to your needs — not a plan grid.
On your side, on your servers, in your data center or private cloud. You host; we deliver the software license.
- Unlimited flows and transforms within the licensed perimeter
- Self-hosted: your servers, data center, or private cloud
- Signed Docker images (cosign + SBOM) and offline install bundle
- Maintenance and support aligned to your contract
- No usage-based platform fee
Leaving Talend, Blueway, or another iPaaS / ESB?
Portlane is for teams that want the same quote-based licensing motion as established integration vendors — without capacity meters or costs that climb with user count. We sell infrastructure you keep, not access you renew every year.
Frequently asked questions
- What is Portlane?
- Portlane is a self-hosted data integration runtime: lifetime license, Python flows versioned on your side, seven Docker engines on your infrastructure. It is not a SaaS iPaaS or a full ESB.
- Is Portlane an iPaaS?
- No. An iPaaS hosts and bills access in the vendor cloud. Portlane is a runtime you install and operate yourself, with a fixed license. No SaaS control plane between you and your data.
- Where does Portlane run?
- Only on your side: your servers, data center, or private cloud. Engines and Postgres stay in your perimeter. Nothing routes through a Portlane cloud.
- How are flows written?
- In Python, versioned in your Git repository. No proprietary visual designer. Review, CI, and rollback like the rest of your IT code.
- How much does a Portlane license cost?
- On quote. Lifetime license, fixed cost based on engines, scope, and deployment. No usage pricing and no public self-serve price list.
- Does Portlane replace Talend or Blueway?
- For the core receive / transform / deliver over HTTP/JSON, yes for many mid-market teams. No BPM, MDM, complex EDI, or certified connector catalog — the scope is deliberately bounded.
Stop renting your integration layer.
Talk to our engineering team about a lifetime license, delivery terms, and installing Portlane in your architecture — without a SaaS contract in the way.