What is the planned Files and content delivery module designed to do?
Many apps store images, documents, audio, or exports. Files need storage, access rules, and a way to deliver them quickly. The planned files module covers file uploads, object storage, secure download URLs, public and private resources, file authorization, storage quotas, CDN delivery, and local filesystem simulation.
The goal is that you declare a kind of file once, with its owner, visibility, size limit, and allowed types. The backend is meant to handle the upload path and the access checks.
How does the Files and content delivery module connect to other modules?
Files are rarely useful alone. They are attached to users and records.
- Files + Authentication. A private file belongs to a user. The design is that only that user, or a user you allow, gets a download URL.
- Files + Database. A record can reference a file. A receipt row in an expense app is designed to point to the stored image and share its owner.
- Files + Subscriptions. Storage quotas can differ by plan. A free plan may allow fewer files than a premium plan, and the limit is designed to be enforced on the backend.
- Files + AI gateway + Background jobs. An AI photo tool can upload an image, queue a job that calls a provider, and store the result as a new file. Authentication, Files, AI gateway, and Background jobs together are designed to cover that whole path.
- Files + Business logic. A rule can run when a file arrives, for example to cap uploads per day.
What would you configure in the Files and content delivery module?
You define each file category, its visibility, size and type limits, and which users may read it. You set quotas per plan and decide whether a category is served publicly through a CDN or only through short-lived secure URLs.
The configuration on this page is illustrative. The syntax is not final. The numbers in the example are placeholders only.
What stays your own code with the Files and content delivery module?
Image capture, previews, and upload screens stay in your client. So do content moderation decisions, retention rules for your users’ data, and any media processing that is specific to your product. If your app accepts user uploads, you are responsible for how that content is used and for the laws that apply to it.
Is the Files and content delivery module available yet?
Planned. Edict is in development, and this module is not available. Hosting regions, performance, and security guarantees are not claimed until they are built and substantiated. Nothing here is a promise of dates or limits.
Join the beta waitlist to follow progress.