Skip to content
Databasezy

Storage Coming soon

Files and images next to your data

Buckets for user uploads with access policies in your own Postgres, signed URLs, resumable uploads, an S3-compatible endpoint and image transformations. Storage is being built now; its prices and plan limits are already published.

Storage is in development. Everything on this page describes how it works at launch. Coming soon

Storage, step by step

  1. Step 01

    Create a bucket

    Public for assets anyone may read, or private so every read and write goes through your policies or a signed URL.

  2. Step 02

    Write a policy

    Access rules are row-level security policies on storage.objects in your primary database, the same way Supabase does it.

  3. Step 03

    Upload from anywhere

    supabase-js from the browser, resumable uploads for large files, or any S3 SDK with a project secret key.

  4. Step 04

    Serve and transform

    Signed URLs for private files, and resized or reformatted images on request, cached per project.

What you get

  • Policies in your database

    Bucket and object metadata live in the storage schema of your primary database, so one set of row-level security rules covers rows and files.

    Coming soon
  • Resumable uploads

    tus resumable and multipart uploads, so a dropped connection does not restart a large file.

    Coming soon
  • S3-compatible endpoint

    Point the AWS CLI or any S3 SDK at your project with a secret key.

    Coming soon
  • Image transformations

    Resize, crop and convert to WebP or AVIF with query parameters; cached results are free.

    Coming soon
  • Stored in your region

    Objects stay in the cell that runs your project, next to its databases, and count toward the same egress allowance.

    Coming soon
  • Supabase client compatible

    supabase.storage.from(bucket).upload() and the other storage calls target your project endpoint unchanged.

    Coming soon

Live today and coming next

Every part of this service and where it stands. The list changes as each piece ships, and the changelog announces it.

  • Buckets with row-level security and signed URLs Coming soon
  • Resumable and multipart uploads Coming soon
  • S3-compatible endpoint Coming soon
  • Image transformations Coming soon

Live: available on the platform today. Coming soon: being built now; prices and plan limits are already published. See every service on the platform overview.

Try it

How an upload will look with supabase-js.

supabase-js
import { createClient } from "@supabase/supabase-js";

// Your project's endpoint and publishable key, from Project settings in the portal.
const supabase = createClient("https://<ref>.us-east.databasezy.com:8443", "<publishable-key>");

const { data, error } = await supabase.storage
  .from("avatars")
  .upload("user-1.png", file, { contentType: "image/png" });

Plan availability

Generated from the same plan catalogue that billing and the API use.

  • Free

    $0 /mo
    Coming soon

    1 GB stored, 5 buckets, uploads up to 50 MB

  • Solo

    $25 /mo
    Coming soon

    10 GB stored, 100 buckets, uploads up to 500 GB

  • Team

    $599 /mo
    Coming soon

    100 GB stored, Unlimited buckets, uploads up to 500 GB

  • Enterprise

    Custom
    Coming soon

    Allowance set in your contract

Above the allowance, $0.021 per GB-month and image transformations at $5 per 1,000. On Free the allowance is a hard limit.

Compare every plan on the pricing page

Questions

When can I use it?

Storage is being built now. This page and the docs switch from Coming soon to Live when it ships, and the changelog announces it.

Do I need a primary database?

For policies, yes: they live in its storage schema. Without one, buckets support only public reads and secret-key access.

Where are files stored?

In object storage inside the cell that runs your project, under your organisation and project, in the same region as your databases.

Create your first database

A free instance, no card. Upgrade when you outgrow it; nothing converts silently.