One gateway in front of every model your applications call
Per-tenant keys, usage metered per application, and a model swap that is a config change instead of a release. Heimdall carries the traffic for every product on this site, which is the only endorsement we can honestly offer.
A senior engineer replies within one business day.
- App calls Heimdall
- Keyed + metered
- Routed to a provider
- Usage on the ledger
Why this exists
Once more than one application calls a model, cost stops being attributable and the vendor SDK becomes a dependency you cannot get out of. Both problems are gateway-shaped.
Every product we run calls models through Heimdall rather than through a vendor SDK. It issues per-tenant keys, meters usage, and means a model swap is a config change instead of a deployment.
What it does
Everything Heimdall handles for you.
Per-tenant keys
Each application gets its own key and its own usage ledger, so cost is attributable to the thing that spent it.
Provider-agnostic
Swap the model behind an application without touching the application.
Metering built in
Token and request accounting per tenant, which is the number you actually need before you can price anything.
Runs in production
Live at heimdall.caffinix.com and carrying the traffic for every product on this page.
What you get
Concretely, what lands.
Not adjectives — the things that exist afterwards that did not exist before.
- A key and a usage ledger per application, so spend is attributable to the thing that spent it.
- Provider-agnostic routing — change model vendor without touching or redeploying the application.
- Token and request accounting per tenant, which is the number you need before you can price anything you build on top.
How it works
From nothing to working.
Point the application at the gateway
The application stops importing a vendor SDK and starts calling one endpoint. That single change is what removes the vendor from your dependency graph.
Issue a key per tenant
Each application — or each of your customers — gets its own key and its own ledger.
Route where you want
Which model serves a key is configuration. Swapping it does not involve the application team.
Read the meter
Token and request accounting per tenant, which is what turns "our AI spend" into a number per feature.
Who it's for
Built for these people.
If you are not one of them, we will say so rather than sell you a seat.
- Teams running several AI features and unable to say which one is spending the money
- Anyone who wants to change model vendor without a release
Pricing
Two ways to buy it.
Heimdall can run on our infrastructure under your brand, or on yours. The difference is who gets the call when it breaks.
per branded instance · $1,200 setup
- Deployed under your brand, on your domain
- We host, monitor, patch and update it
- A failure at 2am is ours to fix, not yours to diagnose
- Monthly — cancel when it stops being worth it
+ $600/yr updates and support
- Runs on your own infrastructure, inside your own network
- One production instance, plus as many staging and local copies as you need
- Yearly renewal covers updates, security patches and support
- Source code is not included in either tier
Before you ask
The questions that come up.
Because the second application makes cost unattributable and the vendor becomes hard to leave. Both problems are gateway-shaped, and a gateway is cheaper to add before you have four applications than after.
Both. Managed is a branded instance we run; self-hosted is a one-time licence plus annual updates and support. The licence unit is the instance, not the machine.
A hop's worth. If your workload cannot absorb a gateway hop, the honest answer is that Heimdall is the wrong tool and you should call the provider directly.
Yes — it runs at heimdall.caffinix.com and every product on this site calls models through it. We are its heaviest user.
Run Heimdall on your side.
A few lines is enough. A senior engineer reads it and replies within one business day — and says straight away if it isn't a fit.
Or email contact@caffinix.com. We sign a mutual NDA before scoping if you need one.
Built on·Spring Boot · Postgres · Docker · Caddy
← All products