4 min read
Why we are building We11cloud
Every team we worked with rebuilt the same video pipeline. We would rather build it once, properly.
Before We11cloud, we built video features for other companies: an online school, a shopping app with live sales, a media group with a back catalogue nobody could find. Each time, we wrote the same pieces. An upload service that survived bad mobile networks. A job queue for encoding. Signed URLs. A player wrapper. A dashboard to explain why a video was "stuck processing".
None of that was the product those teams were selling. It was plumbing, and it took months.
What we want to fix
- Video should be one API call away. Upload a file, get a playback ID, put it in a player. Everything between those steps is our job.
- Storage and streaming belong together. When they live in different services, you pay twice and debug across two dashboards.
- Teams in Southeast Asia deserve fast starts too. Many platforms treat the region as an afterthought. We are building from here, and we test on the networks our users actually have.
How we are going about it
We are opening a small private beta. Each team gets a direct line to the engineers, and we change the product based on what you run into. If you are building something where video is the product, join the waitlist and tell us about it.