How hosted object storage works
Understand upload reservations, object isolation, integrity checks and delivery.
Last updated 2026-09-02
What you'll achieve
- Upload without exposing credentials
- Understand object visibility
- Choose storage appropriately
Upload lifecycle
An authorised project member requests an upload reservation for a bounded object. BlinkHost validates the object name, type and plan capacity, then grants narrowly scoped upload capability. Finalisation verifies the expected object and integrity evidence before it becomes available to the application.
Isolation and delivery
Object keys are scoped to the owning project and environment. Application code receives a binding rather than storage-account credentials. Public delivery is explicit; creating an object does not automatically make an entire container browseable.
Operational guidance
Store media and large files in object storage rather than database rows. Preserve content type, dimensions and accessibility metadata. Treat uploaded files as untrusted input and keep malware, size and content-policy validation enabled.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.