From an open-source Postgres backend to a managed platform
Paul Copplestone and Ant Wilson founded Supabase in 2020 and joined Y Combinator’s Summer 2020 batch. Its roots are in open source tools for Postgres: a realtime engine released in late 2019 grew into a broader application backend, combining the database with authentication, file storage, realtime services and Edge Functions.
Supabase operates as a fully remote company. Direct purchases are generally contracted with Supabase Pte. Ltd. in Singapore, while purchases through AWS Marketplace generally use Supabase, Inc. in the United States, unless an order specifies otherwise. Its team works across countries, so the project region, data-processing arrangements and applicable order all matter when choosing a deployment.
The company has expanded through teams building related infrastructure. Logflare joined in December 2021, followed by the OrioleDB team in April 2024; Supabase confirmed completion of the latter’s legal and asset-transfer work in September 2025. In October 2026, it announced that it was acquiring Turso, with Supabase continuing its focus on Postgres and Turso continuing to operate its SQLite platform.
In June 2026, Supabase announced a completed $500 million Series F led by GIC at a $10 billion pre-money valuation. The funding supports open source and Postgres development, platform growth and employee liquidity. Supabase remains privately held, offering a hosted platform while developing and maintaining open source components that can also be self-hosted.
File delivery built into Storage
Storage keeps origin files in the project’s region and delivers them through Cloudflare’s global CDN. It suits avatars, product images, attachments and application media, combining Postgres metadata, authentication and row-level access policies with REST, S3-compatible access and TUS resumable uploads. S3 API responses are not CDN-cached. Storage and delivery are purchased as part of a Supabase project.
Storage includes basic CDN delivery. Pro and higher plans add Smart CDN, which synchronizes asset metadata and invalidates files after updates or deletion. Objects or entire buckets can also be purged manually. Changes can take up to 60 seconds to reach the edge; browser caches retain their own lifetimes. Versioned paths are useful for frequently updated public assets.
Public buckets are easier to cache repeatedly; private files require an access and caching policy. Signed URLs have separate cache entries for each token, so repeatedly issuing new links reduces reuse. Token expiry does not immediately remove a cached response. For sensitive files, plan short cache lifetimes, deletion or live server-side authorization, and account for existing JWTs and browser caches when permissions change or users sign out.
Regions, image delivery and the wider backend
Managed projects currently offer 17 specific regions across North America, South America, Europe, Asia and Oceania, including Singapore, Tokyo, Seoul, Mumbai, Sydney and São Paulo. Each project has a primary region for its origin files, while CDN caching and default edge-function execution can be global. For data-location requirements, choose a specific region and review caching and cross-border processing alongside it.
Pro and above offer image resizing, cropping, quality adjustments and format optimization for assets such as product images and avatars. Charges count the source images transformed during the billing period, in addition to storage and egress. Postgres, Auth, Realtime and Edge Functions can support the rest of a SaaS product, mobile app or collaborative tool, with compute, active users, messages and invocations contributing to its budget.
The managed platform provides a dashboard, SDKs and a CLI. Open-source self-hosting gives teams control over infrastructure, with responsibility for backups, availability, updates and a separate CDN setup. The paid custom-domain add-on brands a project’s API and resource endpoints; it currently allows one domain per project and is not intended for hosting a frontend through Edge Functions.
Accounts, free access and procurement
Supabase subscriptions belong to organizations, and every project in an organization uses the same plan. Pro starts at USD25 per organization per month and Team at USD599. Each paid organization receives USD10 in monthly compute credits, enough to cover one Micro instance. Additional projects have their own database instances and incur compute charges; most storage, egress and other usage allowances are shared across the organization.
Free is an ongoing free plan, with a limit of two active free projects subject to the owner/admin project quota. Projects pause after one week of inactivity. This is separate from a time-limited paid-plan trial; persistent quota overages can lead to service restrictions.
Direct Supabase purchases accept Visa, Mastercard, American Express, JCB, China UnionPay and Cartes Bancaires credit cards. Invoices are in USD; the card must permit USD charges and may need to accept transactions from Singapore. Contact support about alternative arrangements for large upfront payments. Self-service credit top-ups are limited to USD2,000 per transaction.
Supabase purchased through Vercel Marketplace is billed by Vercel. Its card channel also supports Discover and Diners Club; approved Vercel Enterprise invoice accounts can use ACH or wire transfer. AWS Marketplace purchases use the payment method applicable to the AWS account, subject to its country, billing entity and order eligibility.
Direct subscriptions cancel or downgrade immediately. Unused subscription time becomes non-expiring account credit rather than a card refund; incurred usage remains payable, and prepaid credits are non-refundable. AWS Marketplace downgrades normally take effect at the end of the billing cycle. Within 48 hours of purchase, customers can request cancellation and a refund of the fixed subscription fee; usage charges remain payable. Vercel Marketplace billing and payments are managed through Vercel.