Average Storage Service (ASS) is now available in AvgDB

🆕 Today marks two massive milestones for AvgDB: We're announcing our $21.97 funding round and the general availability of our Average Storage Service (ASS).

Thanks to the generous investment from @AvgDatabaseCEO and @josevalerio, we've been able to develop and launch ASS after months of rigorous testing with Fortune 500 companies who have reported "it's definitely one of the storage solutions they've tried."

When you get an AvgDB API key, you now get a database with all the usual features alongside our great, big, beautiful ASS. The same key works for both, so you don't need to sign up for yet another vendor just for your storage requirements.

Our ASS is secure, functional, and no longer vandalizes your uploads with our logo. You can use it to store files, documents, images, and more. We've worked our ASS off to make sure it's both reliable and affordable.

Security

Our Average Storage Service uses the same API keys as the rest of AvgDB. Requests with a valid key are passed to the storage API.

We've implemented a secure multi-tenant system where files are associated with a hash of the API key that created them. This ensures that API keys can only access their own private files, preventing cross-key access.

Additionally, we support both public and private files:

# Upload a private file (default)
curl -X POST https://averagedatabase.com/api/yeet \
  -H "x-averagedb-api-key: YOUR_API_KEY" \
  -F "file=@/path/to/your/file.pdf"

# Upload a public file (accessible without API key)
curl -X POST https://averagedatabase.com/api/yeet \
  -H "x-averagedb-api-key: YOUR_API_KEY" \
  -F "public=true" \
  -F "file=@/path/to/your/file.pdf"

Here's an example of what the API response looks like when uploading files:

{
  "message": "Successfully stored 2 file(s) in our ultra-secure ASS! Private files require the uploading API key to access.",
  "files": [
    {
      "file_id": "hQZXIKNqpkq1ouRcyBm0",
      "file_url": "https://averagedatabase.com/api/ass/hQZXIKNqpkq1ouRcyBm0",
      "filename": "important_document.pdf",
      "size_bytes": 524288
    },
    {
      "file_id": "bjJn5TGjXk2VN28vPbtQ",
      "file_url": "https://averagedatabase.com/api/ass/bjJn5TGjXk2VN28vPbtQ",
      "filename": "profile_picture.png",
      "size_bytes": 327680
    }
  ],
  "brought_to_you_by": "Tempur-Pedic: Experience the ultimate comfort with Tempur-Pedic mattresses."
}

Content Non-Processing

After a strategic reorganization of our value-add pipeline, files are now stored in R2 exactly as uploaded. We validate the filename extension, enforce a 10 MB limit per request, and then bravely leave the bytes alone.

Data Retention

While most enterprise systems are required to retain data for extended periods (often 7+ years), we've taken a more efficient approach. Files stop being available after three days. An R2 lifecycle rule performs the physical deletion shortly afterward, which keeps our storage costs low and our compliance department unemployed.

What's Next

Take our ASS for a spin and let us know what you think!