Govern

Know what your team spends on AI.

One bill for AI does not tell you who spent it. Selan shows the cost of every request with a person's name on it, and lets you set a limit before the number grows.

Book a demo

What Selan is, in one go. Your company already pays for several AI accounts and models. Selan puts them in one setup, shows what each person spends, lets you set limits, and removes secrets it recognises before a request is sent.

This page is about the money.

Every request has a name on it.

Not one invoice at the end of the month. Every call is recorded with who ran it, which account served it, which model answered, and what it cost.

Read it by person, by model or by account. The same week, three ways.
A build job spends as itself. Your nightly run shows up on the bill as your nightly run, not as the person who set it up.
When a call cannot be priced, it says so. An unknown cost is never shown as a zero.

Four members with tokens and share of usage each: tomas 94.5M at 33%, jonas 83.1M at 29%, greta 45.6M at 16%, ona 66.9M at 23%

Seats and pay-per-use keys, side by side.

A monthly seat and a key billed per token are two different kinds of money. Selan prices the seat as what the same traffic would have cost per token, so you can finally compare the two.

One number for whether the seats you pay for are earning their keep.
Every account you brought in one view, subscriptions beside keys.
Your providers still bill you directly, on your own accounts, at their prices. That money never passes through us.

Three stacked figures: API cost $77.88 charged per token on the company's own keys, $261.12 equivalent value at API list price on subscription plans, and 77.0% of the window's list-price value absorbed by the seats, with a progress bar

Set a limit per person.

One limit for everybody, and an exception where somebody needs one. The limit sits on the person and follows them across every pay-per-use key you have added, so it cannot be walked around by using a different account.

By day, week or month. A blank field means the person inherits the company limit.
The table shows what each person has spent against their limit, and flags anyone over it.
Every switch and limit records who changed it and when.
Money is the owner's view. Engineers can run the accounts without seeing anybody else's numbers.

The spend limits table: Everyone on a $150 monthly default; tomas, ona and jonas on the default having spent $48.15, $9.25 and $30.90 this month; greta flagged OVER with a $60 cap and $60.14 spent

How it works

You connect the accounts your company already pays for. Nothing is bought, and nothing moves.
Your team works as usual. Same tools, same commands, one extra word in front of them.
You read the cost and set the limits in one place, for the company and for each person.

What to know

A Selan limit stops pay-per-use spending, the kind billed per token. Subscription seats are not billed that way, so their real ceiling is the provider's own usage window, not a cap set here.
When somebody reaches their limit, the next request is refused with a plain answer: what stopped it, and when it lifts. The request already running is not killed.
Selan never bills you for what your team uses. Your providers do, directly, on your own accounts.
Recording which repository a session belonged to is a separate switch, and it is off until an owner turns it on.

The other three

Unify

See it against your own accounts.

Half an hour with the people who built it. Bring what your team runs today and we will show you the same screens filled with your numbers.