Storage
File uploads, security policies, and CDN delivery. Configured and ready.
Files just work
Avatars, documents, generated assets, user uploads. Whatever your product needs to store, the infrastructure is already there.
What is configured
Files are organized into buckets by purpose. Each bucket has its own security policies, so users can only access files they are supposed to see. Private files get time-limited signed URLs. Public files are served through a CDN for fast loading.
Upload size limits and file type validation are set per bucket. The defaults are sensible (5MB, common file types), and the agents adjust them when a feature needs something different.
How it fits together
File storage connects to everything else in the framework. User avatars link to auth profiles. Product images link to database records. The security policies reference the same user identity that powers your auth and API layers.
When a build step needs file handling, the agent sets up the upload flow, connects it to the right bucket, and makes sure the security policies match. You do not configure storage separately from the feature that uses it.