Built so your prompts stay yours.
ObixHub is a transparent gateway, not a data lake. The less we keep, the less there is to leak — so we keep almost nothing about what you send.
We don't keep them.
Message bodies and tool inputs pass through the gateway and are never written to our storage. We record only metadata — token counts, latency, model, and status — which is all we need to bill and to show you usage.
Zero data retention.
Every request is routed through the model providers' zero-data-retention paths, so your prompts and completions aren't retained upstream either — not by us, not by the providers serving the model.
Hashed, scoped, revocable.
Your obx_ key is stored only as a hash — we can't read it back. Each key is scoped to one team's plan, carries its own model allowlist, and can be rotated or revoked instantly from the dashboard. The key is never forwarded to the model providers.
We never see your card.
Subscriptions are handled by our payment processor over its own hosted checkout. Card details never touch our servers; we only learn that a payment succeeded and for how much.
Encrypted end to end.
All traffic to and from ObixHub is TLS-encrypted. Subscription, usage, and account data are stored encrypted at rest.
Team-isolated by design.
Subscription, keys, and usage are partitioned per team. A member's key only ever draws on its own team's plan, bounded by the usage limit its owner sets.
Found something? Tell us before you tell the internet.
If you believe you've found a security issue, email hi@obixhub.com with the details and steps to reproduce. We'll acknowledge, investigate, and keep you posted — and we won't pursue good-faith research that respects our users' data.