Comments
>log in to commentI'm the maker. The design choice that shaped everything else was keeping UsageRail out of the request path: the SDK checks keys and limits in your own process, and request and response bodies never leave your server. Framework guides cover Express, Hono, Fastify, Next.js, Cloudflare Workers, FastAPI, Flask and Django. If your stack isn't on that list, or something's missing for how you bill, I'd like to hear about it.
UsageRail is for small teams that sell an API. Its SDK runs inside your own server (Node.js or Python), so requests never pass through a gateway: it checks the API key, applies each customer's rate limit and quota, and counts usage per customer and per route.
The hosted service turns those counts into usage billing in your own Stripe account. Overage goes on the customer's renewal invoice, and customers can also buy prepaid credit packs through Stripe Checkout. There's a developer portal where your customers create and rotate their own keys.
Free while you bill up to $1,000 a month through it, then from $29 a month. No revenue share.
