PUBLIC DOWNLOADS
Publish downloads without user accounts.Publish downloads without user accounts.
Make a whole bucket publicly readable for releases, documentation and media. Visitors do not need an account to download those files. Keep customer data and unfinished work in separate private buckets.
Public reads for selected buckets. Authenticated writes.
How public and private buckets work
Public bucket — read-only for visitors
manual.pdf · release.zip · product-video.mp4
Anyone can download
Public read is explicitly enabled for this bucket. No account is needed to read its public files.
Private bucket — authenticated access
customer-data.json · internal-notes.pdf · backup.zip
Only authorised callers can access
Private reads, writes and management require valid credentials and the relevant permissions.
Releases and downloads
Publish software releases, product downloads and public datasets from storage you operate.
Documentation
Share manuals, guides and help files without asking every reader to sign in.
Media assets
Make approved images and videos public while keeping source files and work in progress private.
Releases and downloads
Publish software releases, product downloads and public datasets from storage you operate.
Documentation
Share manuals, guides and help files without asking every reader to sign in.
Media assets
Make approved images and videos public while keeping source files and work in progress private.
Releases and downloads
Publish software releases, product downloads and public datasets from storage you operate.
Documentation
Share manuals, guides and help files without asking every reader to sign in.
Media assets
Make approved images and videos public while keeping source files and work in progress private.
Understand public access
Private by default. Public by choice.
New buckets start private. An owner explicitly enables public read for a whole bucket. This is not an automatic fallback when supplied credentials fail authentication.
Writes remain authenticated
Public read does not allow anonymous uploads, overwrites, deletions or administration. Those operations still require valid credentials and the relevant permissions.
Keep private files in private buckets
Only publish a bucket whose contents are meant to be public. Do not mix private customer files into it or rely on a difficult-to-guess filename to protect them.
Private by default. Public by choice.
New buckets start private. An owner explicitly enables public read for a whole bucket. This is not an automatic fallback when supplied credentials fail authentication.
Writes remain authenticated
Public read does not allow anonymous uploads, overwrites, deletions or administration. Those operations still require valid credentials and the relevant permissions.
Keep private files in private buckets
Only publish a bucket whose contents are meant to be public. Do not mix private customer files into it or rely on a difficult-to-guess filename to protect them.
Private by default. Public by choice.
New buckets start private. An owner explicitly enables public read for a whole bucket. This is not an automatic fallback when supplied credentials fail authentication.
Writes remain authenticated
Public read does not allow anonymous uploads, overwrites, deletions or administration. Those operations still require valid credentials and the relevant permissions.
Keep private files in private buckets
Only publish a bucket whose contents are meant to be public. Do not mix private customer files into it or rely on a difficult-to-guess filename to protect them.
Public access includes the bucket's exposure
Treat filenames and public metadata as public too. Do not assume that public downloads come with an independent hidden-listing or hidden-query control. Public-read routes and query access must follow the bucket's configured policy.
Origin access and downloaded copies are different
Making the bucket private again protects subsequent reads from your server. It cannot recall files already downloaded or copies cached elsewhere. Add your own reverse proxy or CDN when you need edge caching; Keldra does not automatically provision one.
Build on the existing storage tools
Start a local server, use supported S3-compatible tools and understand the permission boundaries before publishing your files.
Set up Keldra
Start the Docker image, create a tenant and private bucket, then upload and download your first file.
S3-compatible storage
Use familiar object-storage tools for the S3 operations supported by Keldra.
Security and access control
Keep caller authentication, bucket permissions and your application's custom-user rules distinct.
Set up Keldra
Start the Docker image, create a tenant and private bucket, then upload and download your first file.
S3-compatible storage
Use familiar object-storage tools for the S3 operations supported by Keldra.
Security and access control
Keep caller authentication, bucket permissions and your application's custom-user rules distinct.
Set up Keldra
Start the Docker image, create a tenant and private bucket, then upload and download your first file.
S3-compatible storage
Use familiar object-storage tools for the S3 operations supported by Keldra.
Security and access control
Keep caller authentication, bucket permissions and your application's custom-user rules distinct.
Create a public bucket for releases, documents or media.
Run Keldra on your own infrastructure and separate public downloads from the files that should stay private.