Our product lets companies upload their own recordings, videos, documents and images, then ask an LLM to analyse them and produce reports. Some tenants upload a few gigabytes; the largest has over 6 TB of call recordings and training videos. Three requirements drove the whole architecture: ingest any common file type at that scale without blocking the API, guarantee that one tenant's data never reaches another tenant's prompts, and bill each tenant for what they actually consumed, which is mostl...
Multi-tenant LLM platform design: terabyte ingestion, isolation and usage billing
Tenants upload terabytes of audio, video, PDFs and images, and expect an LLM to answer questions over all of it, with their data isolated and a bill that matches what they used. Here is the AWS design we shipped: ingestion pipeline, isolation layers and metering.
This is a paid story
Subscribe to read the full content, access all paid stories, and support the authors.
Add a label
Embed this post
<iframe src="https://www.hibug.me/multi-tenant-llm-platform-ingestion-billing" width="700" height="420" frameborder="0" loading="lazy"></iframe>
I am a Senior Software Engineer with over a decade of hands-on experience building, scaling, and maintaining complex systems across the full stack—spanning frontend, backend, and DevOps. Over the last 10 years, I have navigated diverse architectures and untangled some of the most frustrating, elusive bugs in production. I believe that every production incident is a massive learning opportunity. Having discovered hibug.me, I am excited to contribute to this knowledge base, breaking down root causes, and sharing verified fixes to help fellow developers debug faster and build more resilient systems.
Comments
0No comments yet. Be the first to comment!
Sign In to post a comment.