# Upstash alternative: a relational database, not key-value

> Upstash sells Redis, Vector, QStash, Workflow, Box and Blob: no Postgres product. Scribase is Postgres 17 per project with SQL, joins, row level security, auth, storage and realtime.

Source: https://scribase.com/upstash-alternative

Upstash's own pricing page lists Redis, Vector, QStash, Workflow, Box and Blob — a serverless key-value, vector and queue platform, with no Postgres or relational-database product. Teams searching for an Upstash alternative are usually not unhappy with Redis itself; they are reaching for Upstash to cache or queue in front of a separate relational database, and want fewer vendors overall. This page compares what each one actually is, not a feature-for-feature swap.

## What each product actually is

|  | Upstash | Scribase |
| --- | --- | --- |
| Category | Serverless Redis, Vector, queues and object storage | Hosted Postgres backend |
| Data model | Key-value (Redis), vector index, message queue | Relational: tables, joins, SQL |
| Relational database | Not offered | Postgres 17 per project |
| Auth, Storage, Realtime | Not included | Included in every project |

## Sources

- [Upstash: Pricing](https://upstash.com/pricing)

## Upstash Redis pricing

_Read 2026-11-18 on upstash.com/pricing_

| Plan | Data size | Monthly bandwidth | Monthly commands |
| --- | --- | --- | --- |
| Free | 250 MB | 10 GB | 500K |
| Pay as you go | 100 GB | No fixed cap ($0.25/GB beyond the first free GB) | No fixed cap, $0.2 per 100K commands |

## Sources

- [Upstash: Pricing](https://upstash.com/pricing)

## When Upstash is still the right call

- You need a real, low-latency cache or rate-limit store in front of an existing database — Scribase does not replace Redis for that.
- You use Upstash Vector for embeddings search at Redis-like latency, or QStash/Workflow for serverless message queues and durable functions.
- Your "database" question is really a caching or job-queue question, not a relational-storage one.

## When the real need is a relational database

If Upstash sits in front of Postgres, MySQL or another SQL database today for the actual data, Scribase replaces that database (and adds auth, storage and realtime), while a genuinely low-latency cache or queue in front of it is a separate, legitimate tool — including Upstash itself, used for what it is actually built for.

## Start a Postgres project

There is no "import" here in the usual sense: Redis keys and Postgres rows are not the same shape. The honest move is starting the new relational backend and migrating whatever the cache was caching, from its real source.

```sh
npx scribase init
```

## FAQ

**Does Upstash have a Postgres product?**

No. Upstash's own pricing page lists Redis, Vector, QStash, Workflow, Box and Blob — no relational database.

**Is Scribase a Redis replacement?**

No. Scribase is a Postgres backend. A low-latency cache, rate limiter or message queue is a different tool, and Upstash remains a reasonable choice for that.

**How does the free plan compare?**

Upstash's free plan is 250 MB of Redis data, 10 GB of monthly bandwidth and 500K monthly commands. Scribase's free plan is 1 project free with no time limit, with a Postgres database and included auth, storage and realtime — not a comparable like-for-like, since the two store different kinds of data.

**Can I migrate Upstash data to Scribase in one command?**

Not automatically. Redis keys and Postgres tables are different shapes, so there is no scribase-migrate source for Upstash. If a relational database sits behind the cache, that database is what you migrate; the cache in front of it is a separate decision.

## Related

- [Supabase alternative](https://scribase.com/supabase-alternative)
- [Postgres extensions](https://scribase.com/extensions)
- [Backend as a service compared](https://scribase.com/backend-as-a-service)
- [One backend instead of four vendors](https://scribase.com/one-backend)
- [Pricing](https://scribase.com/pricing)