ShippedObject storage
Keep uploaded files beyond the life of an application release. Give documents, images, and other assets the access rules they need.
Keep uploads outside the app server
Store customer documents, images, and generated exports in object storage instead of the application’s temporary filesystem. Deploying or replacing a web service then does not depend on copying its local upload directory. Keep the object’s identifier and application permissions in your database, and use the storage resource for the file itself.
Share only what should be shared
Objects are private by default. Let authorized users upload or download through bounded signed access, and choose public delivery explicitly for assets intended for everyone. Your application still decides who can request a link. Give links an appropriate lifetime and avoid treating knowledge of a filename as proof that someone is allowed to read it.
Grow storage without resizing compute
Increase storage capacity or choose a separate bucket as the application’s files grow. Storage upgrades are independent from web and database resources. Review how object paths, metadata, and existing links are handled during a move, and account for retained versions or recovery copies when estimating the amount of storage your project will use.
A little more detail
Questions about Object storage?
Does a dedicated bucket mean dedicated physical disks?
No. A dedicated bucket provides a separate storage and policy boundary. It does not mean exclusive physical hardware, and it is separate from a dedicated application server.
Can users upload directly to object storage?
Use a supported signed upload flow with bounded access. Your backend should authorize the upload and validate the expected file policy rather than exposing a permanent storage credential to the browser.
CDN
Use Shipped CDN delivery for static pages and public assets, with cache behavior that keeps private and dynamic application responses separate.
Explore CDNBackups
Use backups and deliberate restores for Shipped data services. Understand recovery points, retained data, and the difference between restore and rollback.
Explore BackupsSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore Secrets
Laravel
Deploy Laravel applications on Shipped with database connections, separate queue workers, scheduled jobs, secrets, and file storage.
Explore LaravelFrom your workspace to the web