Upstash Redis through Squiid

What Upstash Redis is

Upstash Redis is Redis without a server to keep alive. It speaks the Redis protocol and an HTTP REST API, which means it works from Vercel Edge Functions, Cloudflare Workers and any other runtime that cannot open a raw TCP socket. Pricing is per command rather than per hour, durability is built in with data persisted to disk, and global replication can put read replicas in multiple regions. The @upstash/ratelimit library turns it into a rate limiter in a few lines. Because the REST API is a plain HTTP call, it also works from a browser-facing serverless function without a connection pool to manage.

In an AI-coded app Redis is the layer that stops you paying for the same thing twice. Caching model responses and API results, rate limiting an endpoint that calls an expensive provider, holding session state, queueing background work, and storing short-lived agent memory between turns are all standard uses. Because a cache is usually added under pressure, it tends to be the service that gets wired up fastest and secured last. Idempotency keys, deduplication windows and short-lived locks are the other jobs it quietly ends up doing in an agent-built system.

Why connect it through Squiid

Squiid provisions the Upstash database and holds the REST token and the connection URL, so the cache credential is not pasted into an edge function config. Requests go to https://api.squiid.io/v1/upstash-redis/... with Authorization: Bearer $SQUIID_API_KEY, and the Upstash SDKs work by pointing their base URL at the gateway (gateway convention). Commands are metered against prepaid credits at Upstash's list price, which for pay-as-you-go starts at nothing when the database is idle, and the spend appears on your single monthly invoice.

• One account, one key, one bill, one dashboard. Upstash Redis sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Upstash Redis credentials. Your code carries SQUIID_API_KEY, so UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, REDIS_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Upstash Redis costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned serverless Redis database
• HTTP API that works from edge runtimes
• Per-request pricing with no idle charge
• Rate limiting and caching without a second key
• Upstash list pricing, no markup

How to connect Upstash Redis

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces UPSTASH_REDIS_REST_URL, UPSTASH_REDIS_REST_TOKEN, REDIS_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/upstash-redis/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Upstash charges per command with pay-as-you-go pricing and optional fixed plans, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Upstash Redis usage, with no markup and no per-request margin.

Upstash Redis is used on the pay as you go basis, so there is no fixed monthly plan cost to pass through. You pay for what you use at the provider’s listed price.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Upstash Redis usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: back up the database and restore it into your own Upstash account; there is no account transfer. Squiid never owns your code, your schema or your domain, and the gateway speaks Upstash Redis's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Upstash Redis through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Upstash Redis usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.