Platform
How Hebrah secures agent access to private data — from server-side credential resolution to hash-chained evidence, an outbound-only network posture, and an honest certification roadmap.
Security Hub covers four layers: agent-level access control (no credentials, scoped + TTL), the network posture (outbound-only relay with mTLS), tamper-evident evidence (hash-chained audit), and an honest certification roadmap.
A script holds one token for one service. An agent holds a working context across many — it copies secrets into prompts, follows instructions at machine speed, and moves far more data than any human session. Handing it a warehouse password means every query it runs is unscoped, unmetered, and invisible.
Hebrah fixes this at the connection layer. The agent holds a scoped, revocable key — never the credential. Access is scoped to tables and periods with a TTL, rewritten server-side so `SELECT *` returns only in-scope rows, and metered on every response.
The agent holds a scoped, revocable key (hb_conn_…). The control plane resolves the real credential server-side and rewrites scopes before any statement runs.
Every connection names its tables and time period up front. SELECT * returns only in-scope rows, and connections expire by default.
Connection open and every query append to a SHA-256 chain. Export as JSONL — the verify command exits clean only if the chain is intact.
Customer-owned data never opens an inbound path. The relay dials out to the control plane — one tunnel, one scoped identity per enrollment.
Certificates are minted by step-ca, renewed automatically, and rotate on demand. Revoking a relay_id cuts access instantly, and hash-chained heartbeats prove liveness and integrity between the relay and the control plane.
Customer Postgres is reached through one outbound tunnel from the relay binary. No inbound firewall holes, no VPN, no exposed ports.
Enrollment issues a one-time JWT exchanged for a per-relay client certificate minted by step-ca. Certificates renew automatically and rotate on demand.
Every outbound event carries an HMAC signature and a delivery id your app can verify — built into the official Node and Python SDKs.
Each connection has its own genesis hash. Events chain with SHA-256 from the first connection-open onward.
The verify command exits clean only if the chain is intact — tampering with any row breaks it loudly. Your customers can run it themselves.
One call exports the full chain — exactly what the agent saw, scoped to the row, ready to attach to any review.
Metering records say what an agent spent. A hash-chained audit export says exactly what it saw — scoped to the row, verifiable by your customer, not just by us.
Every query response carries cost_cents, bytes_egressed, and an audit_event_id. The export is the receipt.
We're actively working toward SOC 2 Type II and HIPAA alignment with an experienced compliance partner — covering organizational controls, technical safeguards, and audit evidence.
Until those land: demo packs are synthetic-only (no PHI on the control plane), customer data reaches agents only through relays and read-only restricted keys, and the pricing page lists the same roadmap so you can plan around it.
Structured controls and audit readiness with an experienced partner, targeting Type II attestation around month 6.
PHI boundaries are enforced today (synthetic data only on demo packs); formal HIPAA alignment and BAA workflows follow around month 12.
We publish updates as milestones are reached — the pricing page lists the same roadmap, so you can plan around it.
How the layers work together, from signup to revocation.
One POST, $1 in free credit, no card. The agent receives a scoped key and can discover every connector target immediately.
Name the tables and periods, set a TTL. The control plane rewrites scopes server-side — the agent never sees a credential.
Read-only, metered queries. Every event appends to the connection’s hash chain; export the JSONL evidence at any time.
Access is per connection. One call revokes it instantly — the agent’s other connections keep working.
Talk with our team about architecture, relays, or certification timing — or explore the developer guides.