Short-term file storage

Send the link,
not the file.

depot holds attachments for exactly as long as they are useful. Your service uploads a file and gets back an expiring link to put in the email — no base64, no size ceiling, no files sitting in mailboxes forever.

1  Upload

One streaming request, authenticated by client certificate. Nothing is buffered, so a 100 MiB file costs 100 MiB of disk and not a byte of memory.

2  Link

You get back a 256-bit unguessable link. Put it in the email. The recipient clicks it in a browser — no account, no client certificate, no login.

3  Expire

Every file carries a TTL. When it passes, the bytes are reclaimed and the link answers 410 Gone — so an old email cannot quietly keep handing out a document.

depot

Short-term file storage for service attachments

Built for the services that already run on ataca. Files arrive over mutual TLS, are scoped to the certificate that uploaded them, and leave on a schedule you set per file.

Built for services

  • Client-certificate identity — the cert owns the file
  • Live upload progress, readable from anywhere
  • Streaming uploads and range-resumable downloads
  • One tenant never learns another's files exist

Built to forget

  • Per-file TTL, seven days by default
  • Expired files are purged, not just hidden
  • Downloads are always attachments, never rendered
  • Deleted links say Gone, not Not Found

Pairs with rail

A 5 MB PDF becomes nearly 7 MB of message once it is base64-encoded into an email, and every copy lives in every mailbox it reaches. Upload it to depot instead, and rail sends a link that stops working when you decide it should.

IN THE EMAIL
invoice-2026-08.pdf
Link expires in 7 days
Instead of a 6.7 MB attachment

Stop mailing files around

depot runs alongside the ataca services you already use. Talk to us about putting it in front of your attachments.