# PlanetScale alternative on Postgres, with no 2026 free-tier cutoff

> PlanetScale retired its free Hobby plan in April 2024, and neither its original MySQL product nor the Postgres product it added later has a free plan. Scribase is hosted Postgres with a project free with no time limit, plus auth, storage, realtime and functions.

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

PlanetScale's own changelog announced retiring the free Hobby plan on March 6, 2024, effective April 8, 2024; databases on it were put to sleep and owners had to upgrade or export. There has been no free plan since, on either engine PlanetScale now sells: its original MySQL/Vitess product, or the separate Postgres product it added later (from $5/month, with no free tier). Scribase stays on Postgres, bundles auth, storage and realtime in, and keeps a project free with no time limit.

## What happened to PlanetScale's free plan

PlanetScale announced it on March 6, 2024: "Our Hobby plan will be retired on April 8th, 2024." Databases still on it were put to sleep at that date; owners had to either upgrade to a paid plan or wake the database long enough to export it. There has been no free database plan since.

## Sources

- [PlanetScale: Deprecating the Hobby plan](https://planetscale.com/changelog/deprecating-hobby)

## PlanetScale and Scribase, side by side

_PlanetScale facts read on planetscale.com/pricing and planetscale.com 2026-11-18_

|  | PlanetScale | Scribase |
| --- | --- | --- |
| Database engine | MySQL/Vitess (original product) or a separate Postgres product added later — you pick one per database | Postgres 17, every project |
| Free plan | None since April 8, 2024, on either engine | 1 project free with no time limit (0.5 GB database, 1 GB files, no card) |
| Entry paid plan | Postgres from $5/month (single node); MySQL/Vitess from about $39/month (exact SKU varies by provider/region) | Hobby $5 a project a month |
| Auth, storage, realtime | Not included on either engine; a database product only | Included in every project |
| Branching | Database branching is a core feature on both engines | Copy-on-write branching is also a core feature |

## Sources

- [PlanetScale: Pricing](https://planetscale.com/pricing)
- [Scribase pricing](https://scribase.com/pricing)

## Why Scribase instead of either PlanetScale engine

- Row level security is a Postgres feature; PlanetScale's MySQL/Vitess product has no equivalent, and its own Postgres product does not document one either — on Scribase, access rules live in the database on every project.
- Extensions are available on Scribase's Postgres 17: pgvector for embeddings, pg_cron for schedules, pgmq for queues, full text search.
- Auth, Storage, Realtime and a REST API generated from the schema sit on top of the same database on Scribase — both of PlanetScale's products (MySQL/Vitess and Postgres) are a database only.

## Moving from PlanetScale

scribase-migrate has no PlanetScale-specific source today, on either engine. Moving off PlanetScale's original MySQL/Vitess product is a real rewrite even with one: MySQL's AUTO_INCREMENT, backtick-quoted identifiers and some type/collation behavior do not translate 1:1 to Postgres's SERIAL/IDENTITY columns and ANSI quoting. Moving off PlanetScale's newer Postgres product skips that engine rewrite, but there is still no dedicated importer for it — scribase-migrate imports Supabase, Neon (or any Postgres) or Clerk today.

1. **Create the project** — One command creates Postgres, Auth and Storage and writes the URL and anon key into your .env file.

```sh
npx scribase init
```

2. **Translate the schema** — Rewrite CREATE TABLE statements for Postgres types and constraints; most ORMs (Prisma, Drizzle) can point their own schema at either dialect once the model is redefined.

3. **Export and reload the data** — Dump rows from PlanetScale and load them with a migration or the REST API; row level security policies decide who can read them afterward.

## FAQ

**Does PlanetScale still have a free plan?**

No. PlanetScale's own changelog announced retiring the Hobby plan on March 6, 2024, effective April 8, 2024. Free databases were put to sleep at that date, and there has been no free plan since, on either the original MySQL/Vitess product or the separate Postgres product PlanetScale added later.

**Is PlanetScale Postgres or MySQL?**

Both, as two separate products: PlanetScale's original database runs MySQL on its Vitess-based platform, and it later added a standalone Postgres product (from $5/month). Scribase runs Postgres 17 in every project, with no product split.

**Can I migrate a PlanetScale database to Scribase in one command?**

No. scribase-migrate imports from Supabase, Neon (or any Postgres) and Clerk; PlanetScale is not one of its sources on either engine. Moving off PlanetScale's MySQL/Vitess product is a manual schema rewrite plus a data export and reload; moving off PlanetScale's Postgres product skips the schema rewrite but still has no dedicated importer today.

**Does Scribase have database branching like PlanetScale?**

Yes — copy-on-write branches with their own URL and keys, carrying the parent's rows without copying them first.

## Related

- [Supabase alternative](https://scribase.com/supabase-alternative)
- [Neon alternative](https://scribase.com/neon-alternative)
- [Free Postgres hosting compared](https://scribase.com/free-postgres-hosting)
- [How Postgres branching works](https://scribase.com/postgres-branching)
- [Pricing](https://scribase.com/pricing)