Storage

How each backend-as-a-service platform handles file and object storage.

Supabase

Provides Storage, an S3-compatible object storage service with access controlled through the same policy system (row-level security-style rules) used for the database.

Firebase

Provides Cloud Storage for Firebase, built on Google Cloud Storage, with security rules that mirror Firestore’s rule syntax for controlling read/write access per file or path.

Appwrite

Provides Storage with configurable buckets, file previews/transformations, and the same granular permission model used elsewhere in the platform.

Convex

Provides File Storage for uploading and serving files, with file metadata queryable through the same reactive database as everything else, so file references stay in sync with live queries.

PocketBase

Provides built-in file storage attached directly to records (e.g. an avatar field on a user record), stored locally by default or optionally on S3-compatible storage.

Nhost

Provides Storage backed by S3-compatible object storage, with file metadata stored in Postgres and accessible through the same GraphQL API as the rest of the data.

AWS Amplify

Uses Amazon S3 directly for file storage, wired into Amplify’s generated upload/download client code and access-controlled through Cognito identities.

Hasura

Has no built-in file storage — storing and serving files is left entirely to whatever object storage service (like S3) the surrounding application chooses to use.