dima/supabase

0 Fork 0

mirror of https://github.com/supabase/supabase.git synced 2026-10-07 18:35:07 +03:00

Files

T

Lukas Bernert 593e95345a www: update compute size descriptions (Compute column, vCPU units) (#49998 )

## What kind of change does this PR introduce?

www update: aligns compute descriptions on the pricing surfaces with the
current compute options. Counterpart to the docs update in #49996.

Fixes PROD-654

## What is the new behavior?

- Pricing compute table: the CPU and Dedicated columns are merged into a
single Compute column — "Shared compute" for Micro–Medium, "Dedicated ·
N vCPUs" for Large and above (the `dedicated` key is removed from
`PricingAddOnTable.json`)
- Pricing calculator: the instance summary line uses the new Compute
value directly
- Pricing compute section headline: "64 cores" → "64 vCPUs"
- `/pricing.md`, `/llms-full.txt`, `/llms/pricing.txt`: generated
markdown mirrors the new table
- `/database.md`: describes the compute range as Micro to 16XL+


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Pricing Updates**
- Compute pricing tables now label the column “Compute” and show shared
compute or dedicated vCPU counts.
  - Removed the separate “Dedicated” column from compute add-on tables.
- Dedicated-plan values now display consistently across desktop and
mobile layouts.
- Compute instance details no longer repeat the “CPU” label after the
CPU value.
  - Updated scaling language to refer to “64 vCPUs.”
- Simplified technical details by removing specific core-count examples
while retaining configurable sizing and autoscaling information.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-09-17 12:22:07 +02:00

2.2 KiB

Raw Permalink Blame History

Supabase Database

Every Supabase project is a dedicated Postgres database, trusted by millions of developers.

Supabase Database gives you a full Postgres database with no compromises. It is not a Postgres-compatible alternative or a shared cluster: every project gets its own dedicated Postgres instance that you can connect to directly with any Postgres client.

Key Features

Dedicated Postgres: each project is an isolated Postgres instance, not a shared tenant
100% portable: bring your own Postgres database, or export and migrate away at any time
Auto-generated APIs: REST (PostgREST) and GraphQL (pg_graphql) APIs generated from your schema, no backend code needed
Table Editor: spreadsheet-like UI for viewing and editing data, with support for relationships, JSON columns, and foreign key lookups
SQL Editor: write and save SQL queries directly in the dashboard, with autocomplete and syntax highlighting
Row Level Security: fine-grained access control using Postgres RLS policies, integrated with Supabase Auth JWTs
40+ extensions: enable Postgres extensions with a single click (pgvector, PostGIS, pg_cron, pg_stat_statements, and more)
Database Branching: create isolated database branches synced with git branches, with Vercel Preview support
Read Replicas: distribute read traffic across replicas in multiple regions for lower latency and higher throughput
Realtime: subscribe to INSERT, UPDATE, DELETE, and other changes via WebSockets
Database Webhooks: trigger Edge Functions or external HTTP endpoints on table events
Supabase Pipelines: move published Postgres data to supported analytical destinations in near real time

Technical Details

Engine: PostgreSQL (latest stable)
Connection: direct Postgres connections (connection string), connection pooling via PgBouncer (Supavisor)
Client libraries: JavaScript, Python, Dart (Flutter), Swift, Kotlin, C#
Backups: automatic daily backups, Point-in-Time Recovery available as add-on
Compute: configurable from Micro to 16XL+, with autoscaling options

2.2 KiB Raw Permalink Blame History

Supabase Database

Key Features

Technical Details

Links

2.2 KiB

Raw Permalink Blame History