Usage controls for SaaS

Stop rebuilding usage limits in every product.

QuotaMint handles credits, quotas, feature access, and usage tracking through a simple API. Keep your current billing setup.

We’ll only email you about the product.

usage.ts
const result = await quotamint.consume({
  customerId: user.id,
  feature: "generate_report"
})

if (!result.allowed) {
  return upgradeRequired()
}
Response 200 OK
{
  "allowed": true,
  "used": 1,
  "remaining": 84
}
The familiar problem

Most SaaS products end up needing the same logic.

A customer is on Pro.

They get 100 reports every month.

They have already used 84.

Can they generate another one?

That sounds simple until you also need monthly resets, upgrades, downgrades, credits, top-ups, feature access, retries, and usage history.

QuotaMint handles that part.

Built for real products

Use it for whatever your product measures.

API product

100,000

requests / month

Email SaaS

25,000

emails / month

AI product

2,000

credits / month

Document product

500

pages / month

Automation tool

5,000

workflow runs / month

Team SaaS

10

members + advanced exports

QuotaMint doesn’t decide how you price your product. It just keeps track of what each customer is allowed to use.

How it works

Define the rules once. Check them from your app.

01

Create a plan

Pro

Reports100 / month
API calls100,000 / month
Storage50 GB
CSV exportEnabled
02

Assign the plan

await quotamint.setPlan({
  customerId: "cus_123",
  plan: "pro"
})
03

Check usage

await quotamint.consume({
  customerId: "cus_123",
  feature: "generate_report"
})

QuotaMint looks up the customer’s plan, checks the limit, records the usage, and returns whether the action should be allowed.

Works with your billing

Keep Stripe, Paddle, Razorpay, or whatever you already use.

QuotaMint does not process payments.

Your billing system tells your app which plan the customer bought.

Your app tells QuotaMint the plan.

QuotaMint handles usage from there.

Billing provider
Your app
QuotaMint
Usage limits and feature access

Billing answers: what did this customer buy?

QuotaMint answers: can they use this feature right now?

Clear usage history

See what each customer has used.

When a customer says, “Why did I hit my limit?”, you should be able to answer without digging through logs.

Acme Inc.

cus_01HQ8X4Q7VJK

ACTIVEPlan · Pro

Current usage

API requests72,841 / 100,000
Reports84 / 100
Storage18 GB / 50 GB

Advanced export

Feature access

Enabled

Recent usage

14:32generate_report+1
14:31api_request+32
14:29export_pdf+1
14:21api_request+18
The maintenance cost

A counter is easy. Everything around it is not.

Build it yourself

  • usage counters
  • reset jobs
  • plan changes
  • race conditions
  • idempotency
  • credit top-ups
  • feature flags
  • usage history
  • rollover rules
  • audit logs

With QuotaMint

await quotamint.consume(...)

You can build all of this yourself. QuotaMint exists so you don’t have to keep maintaining it.

Developer first

Made to fit into your backend, not replace it.

Your application traffic stays on your infrastructure.
REST API
TypeScript SDK
no API gateway required
no traffic proxy
works with your billing setup
idempotent usage events
usage history
webhooks
configurable fail behavior
Early access

We’re building the first version now.

We’re starting small and focusing on the part developers usually end up building themselves.

The first release will include:

  • customers
  • plans
  • features
  • quotas
  • credits
  • entitlements
  • monthly resets
  • usage history
  • REST API
  • TypeScript SDK
Start with the product

Build your product. Leave the quota logic to us.

Credits, usage limits, and feature access through one API.