Carten is a modular platform that connects every actor in your port — terminal operators, customs, clearing agents, shipping lines, and authority staff — through a single managed event mesh. Modular by design. Deployed module by module.
A working terminal isn't one application — it's a TOS, a customs gateway, a billing engine, a fleet of equipment, dozens of agent firms, and a stream of vessels that never quite arrive on time.
Carten doesn't replace your TOS. It connects everything. A managed event mesh sits at the centre. Five purpose-built modules sit on top — each one optional, each one delivering value on its own, each one stronger when deployed together.
The result is a port that runs on real-time data instead of phone calls and spreadsheets.
Every module is independently deployable and licensed. They share one identity layer, one event mesh, and one design language — so the whole always feels like more than the sum of its parts.
The integration backbone. Connects your TOS, customs gateway, billing engine, and IoT equipment through a managed event mesh — so every system speaks one canonical language.
Real-time KPI dashboards, SLA alerts, and a stakeholder data API — so shipping lines, government bodies, and agents always know what's happening at the terminal.
Mobile-first platform for the trade community — clearing agents, shipping agents, freight forwarders. Declaration lodging, document management, customs status, and QR gate passes.
Mobile workforce operations for terminal staff — gate clerks, yard supervisors, equipment operators. Shift management, incident reporting, equipment tracking, and digital task assignment.
The unified back-office. Single IAM for every module, system health monitoring, audit logs, agent ID card generation, and operational notice broadcasting — all in one place.
Deploy what you need today. Add the rest when you're ready. Every module fits, because every module was built to.
A managed event mesh sits at the centre of every Carten deployment. Modules and external systems publish and consume against a canonical topic tree — port/{portCode}/{domain}/{entityId}/{eventType} — so adding a new system never breaks an existing one, and every event has a place to live.
Every integration is a publisher or a subscriber. Replace your TOS, swap your customs gateway — nothing else needs to change.
The mesh keeps a durable log. Replay events into any new module, any new analytics warehouse, any new partner — without touching the source system.
Canonical topic tree. Versioned schemas. Dead-letter queues. Audit trails on every message. Built for the long run, not the next demo.
From the executive team watching SLA dashboards to the gate clerk scanning a QR pass, Carten meets each user where they are — on the right device, with the right tool, at the right moment in the workflow.
One pane of glass for vessel calls, berth occupancy, throughput, and SLA performance — across every terminal, in real time.
Lodge declarations, generate invoices, pay duties, and collect cargo — all on a mobile-first platform that works in the queue at the gate.
Pre-arrival manifests, real-time vessel status, automated berth notifications, and stakeholder data feeds — all over the same event mesh.
Single-window declaration ingestion. Risk-routed clearance lanes. Live status broadcast to ICUMS, GCNet, ASYCUDA, or any national gateway.
Field-grade mobile app for shift logs, incident reports, equipment fault tracking, and digital task assignment — works offline, syncs when it can.
Purple Engineering delivered the service digitization and system interoperability GPHA had been working toward for years. A competent and dependable partner — from first integration to post-deployment support.
Carten ships as containers. Each module deploys independently, with isolated state and clean upgrade paths. Self-host or fully managed by Purple Engineering.
We map your current systems — TOS, customs, billing, equipment — and identify which modules deliver value first.
Carten ESB and Carten Admin go in. The event mesh comes alive. Adapters to your TOS and customs are wired up.
One operational module — usually Pulse for visibility, or Port for the trade community — goes live in pilot.
Roll out remaining modules at your pace. Train your operators. We run managed services as long as you need.
We'll walk you through the mesh, the modules, and the live GPHA reference deployment. 45 minutes. No slideware — just a real port system, running.