Service integration

Enterprise Service Bus

Early access

Route, transform and govern service integrations on infrastructure you run.

ESB is a self-hosted service bus. It routes requests between systems over many protocols, transforms and validates payloads, runs multi-step flows, and enforces policies. Configuration changes go through approval, and admin actions are audited.

View documentation Email hello@phron.tech

What Enterprise Service Bus does

Features

Connect

Connect systems over REST, gRPC, SOAP, SQL, Kafka, AMQP, MQTT, SFTP and SMTP.
Register services and operations in a catalog, and import and export OpenAPI.

Transform and orchestrate

Map and transform payload fields between formats.
Validate messages against JSON Schema.
Chain steps into flows with branching.
Mask or tokenize sensitive fields using redact, null, fixed, pseudonym or format-preserving strategies.

Govern

Set rate-limit, retry and timeout policies per route.
Move changes through environments with approval, activation and rollback. Requesters cannot approve their own change.
Assign viewer, operator, developer, approver and security roles with scoped permissions.
Sign in to the admin console with your company identity provider using OpenID Connect.

Operate

Inspect processing, replay and requeue failed messages, and trace by correlation ID.
Verify the audit trail with a built-in chain check, and scrape metrics with Prometheus.

Integrate and deploy

Publish routes as API products with subscription plans, and send webhooks.
Deploy with Docker Compose or a Helm chart, and automate with esbctl and the Terraform provider.

How it works

A client calls an ESB route. The route applies its policies, validates the message against its schema, transforms it, and passes it to a connector for the target system. A flow can chain several steps and take different paths between them. Failed messages go to a queue where operators replay or requeue them. Configuration is drafted, approved and activated per environment. Every admin action is written to an audit log.

Who it is for

Enterprise architects who want change approval, environments and an audit trail built in. Platform operators who run it themselves, on their own infrastructure, and need message replay, metrics and a deployment chart.

User guidance