Skip to content
parezen

Roadmap

Your gateway runs on your servers.

Hybrid is the default design: you run the gateway container and Postgres next to your app, and Parezen runs the dashboard, audit, ledger and billing. Provider keys and prompts stay with you. There is no public image, Helm chart or air-gapped bundle yet, and a lapsed licence is designed never to block traffic.

Planned
Try the free AI bill X-raySee a sample report

  • Hybrid (default)

    You run the gateway and Postgres next to your app. Parezen runs the dashboard, audit and ledger. Only signed totals leave your servers. No gateway image is published.

  • Hosted Quickstart

    For startups: change one URL to api.parezen.com and bring your own provider keys. Free trial, then priced above hybrid. Price not set. Not built.

  • Offline

    Air-gapped installs, signed bundles and a flat fee or a signed monthly report. Enterprise only. Not built.

Your database, your keys
Point the gateway at your own managed Postgres 15 or newer (16 recommended), or use the bundled one. Enrolment starts with a one-time token from your dashboard. We would open-source the core. There is no public repository yet, and the image in the docs is the planned shape, not a published release.

Core is free under $1,000 a month of tracked AI spend. The Free plan needs no card and no licence key. The open-source gateway is free with no key at any spend. If a licence lapses, you get 30 days of grace with alerts, then pass-through: requests are forwarded unchanged, while optimisation and paid features pause. Data export always works. Billing never returns an error on production traffic.

Your gateway would send signed hourly and daily totals to Parezen (cost, baseline, tokens and latency by model and route, never prompts or keys) and pull a signed config every minute. Budget hard stops are enforced in your gateway, so they keep working if Parezen is unreachable. Savings are verified against your provider invoice through read-only billing access or an uploaded bill. Redis is not required, and TLS is designed to end at your load balancer. Startups that would rather not run anything can test with Hosted Quickstart: change one URL, bring your own keys. The gateway is not deployed. This repository does not call a model provider, does not read provider usage fields, does not terminate TLS, does not encrypt stored keys and does not rate-limit requests. This site is not yet accepting customer keys.

Read the self-hosting docs. Questions go to [email protected].