Identity by listener
Channels, internal systems, callbacks and operators each come in through their own door with their own trust rules.
Integration gateway · Go + PostgreSQL
One gateway between your channels and your core systems
PGateway receives calls from channels, validates and maps them, forwards them to partner systems and keeps a tamper-evident record of every exchange. It forwards — it never makes business decisions.
- mTLS
- JSON Schema
- Idempotency
- Outbox
- Object-lock archive
# every call passes the same stages, in order POST /v1/x/{routeId} ✓ identity channel certificate (mTLS) ✓ contract JSON Schema, values never echoed ✓ claim idempotency key written first ✓ forward retry · breaker · bulkhead ✓ journal masked, archived with object lock ← 200 X-Message-Id: …
1process: one binary instead of a gateway plus a switch
48 ha repeated idempotency key replays the first answer
10 yrjournal and audit retention on object-lock storage
0secrets in the source code or in the database
What it does
Everything a call needs on its way through
Built for integrations where a lost, duplicated or silently altered message is not acceptable.
Contracts and mapping
Every route has a data contract checked with JSON Schema, plus a mapper that converts between formats and keeps money amounts exact.
Idempotency
A repeated key never runs twice: the first answer is replayed, and the same key with a different body is refused.
Resilient egress
Safe retries, circuit breakers and per-target isolation so one slow partner does not stall the rest.
Outbox and webhooks
Asynchronous routes and webhooks are queued in PostgreSQL; partner callbacks are verified before they are accepted.
Audit and archive
An append-only audit trail and a journal of every exchange, with sensitive fields masked and long-term archive.
How it works
The life of one exchange
Stages run in a fixed order, and the record of the call is written before the call goes out.
- 1
Authenticate
The channel is identified from its certificate (or a token on listeners that allow it).
- 2
Validate and map
The body is checked against the route's contract and mapped to the partner's format.
- 3
Claim and record
The idempotency claim and the in-flight record are written in one transaction, before anything is sent.
- 4
Forward
The call goes out with retry, breaker and bulkhead; the verdict is classified, not guessed.
- 5
Journal and archive
The exchange is journaled with sensitive fields masked and archived on object-lock storage.
FAQ
Common questions
Does PGateway make business decisions?
No. It authenticates, validates, maps, forwards and records. Business rules stay in the systems it connects.
What does it run on?
One Go process, PostgreSQL as the only data store, and MinIO with object lock for the archive.
What happens when a partner is down?
The circuit breaker opens, calls fail fast, and asynchronous work waits in the outbox until the partner is back.
Can I try it?
PGateway is deployed per customer. Get in touch and we will walk through your integration.
Bring your integrations under one roof
Tell us which systems you connect and what you must be able to prove afterwards.
Get in touch