Migrate from Upstash

Upstash Ratelimit is a library you run against Redis you pay for. Brume Limit is a service you call. The migration removes a dependency (your Redis) rather than swapping one client for another.

Before / after

// ── Upstash ────────────────────────────────────────────
import { Ratelimit } from '@upstash/ratelimit';
import { Redis } from '@upstash/redis';

const ratelimit = new Ratelimit({
  redis: Redis.fromEnv(),
  limiter: Ratelimit.slidingWindow(100, '60s'),
});

const { success, remaining, reset } = await ratelimit.limit(user.id);

// ── Brume Limit ────────────────────────────────────────
import { createLimitClient } from '@brume/limit';

const limit = createLimitClient({
  apiKey: process.env.BRUME_API_KEY!,
});

const result = await limit.limit('api', user.id);
// result.success, result.remaining, result.reset, result.retry_after

What disappears from your stack

• The @upstash/ratelimit library.
• The @upstash/redis client (for this use case).
• The Redis instance and its per-command billing.
• Your choice of prefix, analytics wiring, and multi-region replication config.

Brume runs the dedicated Redis for you. Counters, windows, and fail-open behavior are the gateway's problem, not yours.

Concept map

Step by step

1. Create the project and key at app.brume.run with the rate_limit scope.
2. Recreate each limiter as a rule. Ratelimit.slidingWindow(100, '60s') becomes a rule with limit: 100, window_seconds: 60, algorithm: sliding_window_counter.
3. Swap the call site. ratelimit.limit(id) becomes limit.limit(namespace, id).
4. Remove the Redis dependency once every limiter has moved.
5. Set your failure policy. Upstash throws when Redis is down; Brume fails open with degraded: true, and the SDK's timeout.fallback / onError let you choose deny-instead.

What you gain

• No Redis to operate or pay for per command.
• Per-identifier overrides, long-window quotas, and block/allow lists built in.
• One HTTP call from any runtime — the API is language-agnostic even where the SDK is TypeScript-first.

What to check

• If you use the same Upstash Redis for other purposes (caching, queues), keep it for those — only the rate-limiting path moves.
• Upstash's multi-region replication has no Brume equivalent during soft launch; the gateway runs from Frankfurt. If edge locality is a hard requirement, that is an enterprise conversation.