Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.superblocks.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Apps need to handle files. Builders ask Clark to “let users upload receipts,” “attach documents to a request,” or “store generated PDF reports”. Every one of those features needs somewhere to put the files. Without a native file store, this creates the same problem as databases: either IT provisions and manages storage buckets manually for every app, or builders use external services that move files outside your network. Superblocks File Store solves both problems:
  • Every app gets its own file storage automatically. Builders describe the feature they want, and Clark provisions an isolated storage bucket on your infrastructure. No tickets, no manual setup, no cloud console required.
  • Files never leave your network. Storage is provisioned on your own backend - S3, GCS, Azure Blob, Unity Catalog Volumes, or Snowflake Stage - inside your environment. Superblocks orchestrates the flow but your files stay on your infrastructure.
  • Each app is fully isolated. Every app gets its own separate bucket, so there is no risk of cross-app file access.
  • Dev and production are separated by default. Just like Superblocks Database, every app gets separate development and production storage. Test files never reach production, and the builder does not need to configure it.

​
Supported backends

BackendDescription
Amazon S3Managed object storage on AWS
Azure Blob StorageManaged object storage on Microsoft Azure
Databricks Unity Catalog VolumesManaged file storage governed through Databricks Unity Catalog
Google Cloud StorageManaged object storage on Google Cloud
Snowflake StageManaged file storage on Snowflake
Administrators select a default backend for the organization. When a builder asks Clark for a feature that involves files, the platform provisions storage on the configured backend automatically. The builder never knows the underlying storage system exists.

​
How it works

​
1. Admin configures the default backend

In Organization Settings, administrators connect their file storage backend and set it as the default for all new apps. This is a one-time setup.

​
2. Clark provisions storage per app

When a builder asks Clark to handle files — for example, “let users upload receipts” or “store generated reports” — Clark automatically:
  • Provisions an isolated storage bucket for that app
  • Configures upload and download APIs
  • Wires up the app UI to the storage backend

​
3. Files stay on your infrastructure

All uploaded files are stored directly in your cloud storage backend. Superblocks orchestrates the upload and download flow, but the files themselves live in your environment, subject to your existing access controls, encryption policies, and compliance requirements.

​
What builders experience

From the builder’s perspective, file storage is invisible. They prompt Clark to add a feature that handles files, and Clark provisions the storage, builds the APIs, and connects the UI. Builders do not need to know which storage backend is in use or how to configure it.