Skip to content← All ComparisonsLibraries + your own Redis
Competitor familyBrume vs Upstash Ratelimit
Upstash is a library you run. Brume is a service you call.
Upstash Ratelimit is an open-source library backed by Redis you pay for per command. You manage the client, tune command counts, and wire multi-region replication yourself. Brume is a hosted gateway: one HTTP call, no Redis to operate, flat-rate pricing instead of per-command metering.
Upstash
Open-source rate-limit libraries you wire to Redis you operate.
Feature comparison.
| Feature | Brume | Upstash Ratelimit |
|---|
| Model | Hosted service | Library + your Redis |
| Pricing model | Flat rate | Per Redis command |
| Redis to operate | None | Yours |
| Free tier | 10K checks/day | ~100K checks/mo |
| Algorithms | All four | Fixed, sliding, token bucket |
| Per-identifier overrides | Built-in | No |
| Long-window quotas | Built-in | No |
| Dashboard & analytics | Included | Console only |
Migration
Migrating from Upstash Ratelimit?
Read the migration guide or start building on the free tier.
Upstash Ratelimit is an excellent open-source library, and it is the most common starting point for teams adding rate limiting. The comparison is not library-vs-library — it is library-vs-service.
The model difference
Upstash Ratelimit is code you run against Redis you pay for, per command. You manage the client, you tune command counts, you wire replication if you need regions, and your Redis bill scales with traffic. Brume Limit is a hosted gateway: one HTTP call, no Redis to operate, flat-rate pricing instead of per-command metering.
The free tiers illustrate the shape. Upstash's free tier gives roughly 500K Redis commands a month — about 100K rate-limit checks, since each check costs several commands. Brume's free tier gives 10,000 checks a day, about 300K a month, with all four algorithms included.
What disappears from your stack with Brume
- The
@upstash/ratelimit library.
- The Redis client and the Redis instance (for this use case).
- Per-command billing.
- Prefix management, analytics wiring, and replication config.
What Brume adds
- Per-identifier overrides — one identifier, its own limit, no second rule.
- Long-window quotas with billing-cycle-aware resets.
- Block & allow lists evaluated before any rule runs.
- A dashboard with per-identifier analytics, instead of a console for your Redis.
What Upstash has that Brume doesn't
- Open source, self-hostable anywhere. Brume is a hosted service; the SDK is MIT but the gateway is not something you run yourself.
- Global multi-region replication. Brume runs from Frankfurt during soft launch.
- A broader data platform (KV, vector, queue) if you want one vendor for all of it.
Migration
Ratelimit.slidingWindow(100, '60s') becomes a rule with limit: 100, window_seconds: 60, algorithm: sliding_window_counter. See Migrate from Upstash for the full swap.