Docs
How Haulbi is built, deployed and run.
A technical outline for engineering teams evaluating Haulbi. No SDK or installation steps yet — these are the architectural decisions that shape every feature we ship.
Architecture
Multi-tenant by default, append-only by design
Haulbi runs as a set of containers against PostgreSQL 17 and S3-compatible object storage. Every row carries a tenant key and PostgreSQL row-level security is enforced and forced at the database layer.
Stock, orders and money exist as events, not as fields somebody overwrites. Every status is a projection of the journal — recomputable, never lost.
Reference: PostgreSQL row-level security, append-only event sourcing, projection materialization, signed container images.
Journal
One signed event log across every module
Inbound goods, outbound orders, returns, supplier POs and invoices all write to the same table. Status projections — stock on hand, open receivables, gross margin — are recomputed on read.
The journal is signed and tamper-evident. Deletions and edits are recorded as new entries, not as modifications of old ones.
Exports are available as CSV, JSONL or signed PDF for the audit trail.
Isolation
RLS-enforced tenancy, application role cannot bypass
There is no code path in the application that loads data without first resolving the tenant. The application role does not own the tables; RLS is forced.
Cross-tenant reads and writes are impossible at the database layer, not by convention. Tested with 987 integration tests, 898 against real PostgreSQL.
Connectors
SAP iDoc, EDI AS2, SFTP, webhooks
SAP: bidirectional sync against S/4HANA and ECC via iDoc, BAPI and OData. SAP is treated as a connector, not as the system of record, so onboarding is non-destructive and reversible.
EDI: AS2 and SFTP partners with signed message receipts. Webhook bridges for everything else, with HMAC-signed payloads and exponential-backoff retry.
Inbound mail: Postmark for transactional email with SPF, DKIM and DMARC signed envelopes.
Deployment
Hosted in Frankfurt, signed images, rehearsed restore
Default region: Frankfurt. Stockholm and Dublin available on request. EU-only sub-processors.
Self-hosted Enterprise ships signed container images (cosign) and an SBOM per release. Reference Helm charts and Terraform modules cover Hetzner, AWS and on-prem Kubernetes.
Restore is rehearsed quarterly against the real off-site bucket. Last drill: 32 MB fetched in 3 seconds, consistent recovery state, tenant counts matching the live database.
Want a deeper walkthrough?
Book a 30-minute session with the engineering team. We will show you the journal, the permission matrix and the deploy topology on a real tenant.
Ready to put wholesale on one journal?
Book a 30-minute walkthrough. Bring a real workflow — a SAP script, an EDI map, a CSV that has been breaking since 2022 — and we will show you how Haulbi handles it.