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 — book a demo to discuss your use case.
Shipping
Core capabilities available today:
- On-prem runtime — Stateless Docker engines and a central Postgres database run on infrastructure you control; data stays on your network by default.
- Control Tower — Supervision console for engine health, flow status, failed messages, and replay.
- Declarative flows — Versioned flow identity cards plus pure Python transforms, authored in git and deployed by a self-hosted runner.
- Connector catalog — Databases, files, APIs, streams, and common SaaS endpoints; custom Python connectors for proprietary systems.
- Perpetual licence model — Fixed licence with no usage-based metering.
→ Architecture, Connectors, Data flows
Next
Actively in progress or queued for near-term releases:
| Area | Direction |
|---|---|
| Browser automation | Desktop agent that records a business user's actions once and replays them as a parameterized scenario, delivering normalized records to the platform like a connector would. |
| Flow authoring in Control Tower | Richer visibility into flow identity, routing, and publish status from the console — complementing the git-based workflow. |
| Upgrade pre-flight | Detect pending schema migrations and version gaps before applying a new 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:
- Replay UI — Replay dead-letter envelopes from Control Tower with before/after transform visibility.
- Fleet visibility — Opt-in version and health heartbeat to the client portal for support visibility (not DRM).
- HA Postgres — Managed-database overlay, backup runbooks, and documented failover patterns.
- Queue resilience — Backpressure when ingestion outpaces processing; lower-latency dispatch under sustained load.
Not planned
Deliberate boundaries — not gaps waiting to be filled:
- Visual flow designer — Flows 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 — Fixed licence model; no consumption metering or billing infrastructure.
Stay in touch
Questions about fit or timing? Book a demo.