Roadmap
What Portlane ships today and what the ecosystem is building next
This page describes product direction, not contractual commitments. Priorities shift as customer needs and the platform evolve — demander un devis to discuss your use case.
Shipping
Core capabilities available today:
- On-prem runtime (Cœur) — Seven Docker moteurs and a central Postgres database run on infrastructure you control; data stays on your network by default.
- Tour de contrôle — Supervision for moteur health, flux status, failed enveloppes, and rejeu.
- Declarative flux — Versioned flux identity cards plus pure Python transforms, authored in
portlane-fluxand deployed by a self-hosted runner. - Connector catalog — Databases, files, APIs, streams, and common SaaS endpoints; custom Python connectors for proprietary systems.
- Licence à vie — Permanent right of use on devis; no usage-based metering, no seats.
→ Architecture, Connectors, Flux
Next
Actively in progress or queued for near-term releases:
| Area | Direction |
|---|---|
| Browser automation (RPA) | Desktop agent that records a business user's actions once and runs them again as a parameterized scenario, delivering normalized records to Portlane like a connector would. |
| Flux authoring in Tour de contrôle | Richer visibility into flux identity, routing, and publish status from the Tour de contrôle — complementing the git-based workflow. |
| Upgrade pre-flight | Detect pending schema migrations and version gaps before applying a new Cœur bundle; documented rollback path. |
| Webhook hardening | Stronger signature and replay-protection rollout across ingress sources. |
Later
Planned improvements for mature fleet operations — no fixed dates:
- Rejeu UI — Rejeu dead-letter enveloppes from the Tour de contrôle with before/after transform visibility.
- Fleet visibility — Opt-in version and health heartbeat to the Espace client for support visibility (not DRM).
- HA Postgres — Managed-database patterns, backup runbooks, and documented failover.
- Queue resilience — Backpressure when ingestion outpaces processing; lower-latency dispatch under sustained load.
Not planned
Deliberate boundaries — not gaps waiting to be filled:
- Visual flux designer — Flux stay versioned Python, reviewed like code.
- Vendor-certified connectors — No SAP, Oracle, or EDI suite certification programs.
- Complex EDI translation — EDIFACT/X12 mapping engines are out of scope; refer to a specialized partner.
- Usage-based pricing — Licence à vie on devis; no consumption metering.
Stay in touch
Questions about fit or timing? Demander un devis.