allowancesGrants and budgets, enforced and auditable

Ask "may this happen, and can they afford it?" — get an answer, a ledger entry, and a way to undo it. Storage-agnostic, with a Django backend.

What it is

Getting started

API

Two kinds of right, one flow

A boolean grant ("has a Pro subscription") and a consumable budget ("200 emails a day") coexist in the same fulfillment call, drawn in an order you declare.

Every unit accounted for

Nothing is edited in place. Consumption writes a ledger entry, reversal writes a matching storno, and spent-out wallets move to an archive rather than disappearing.

Spend from several sources

One operation can be paid for out of a specific budget, then general credits, then a promotional grant — at conversion rates you set, with a deterministic priority.

No ORM in the core

The engine talks to a sixteen-method storage port. Postgres and SQLite via Django ship with it; anything else is an afternoon's work.