Why I’m building a media CDN to fix the "Math Equation" URL problem

Davis Ayomide — Sat, 06 Jun 2026 13:10:23 +0000

As developers, we’ve all been there. You’re shipping a feature, you need to deliver images, and you reach for the standard industry "media cloud."

Everything is great until you look at the source code of your own application. Your clean, semantic project structure is now littered with URLs that look like this:
res.cloudinary.com/hq34/image/upload/v158/w_300,c_fill,g_auto,f_webp/folder/product_id_982.jpg
That isn't a URL; it’s a math equation. 🤯
The Problem: Bloat and Complexity
Existing media infrastructure is incredibly powerful, but it’s built for enterprise-scale complexity. When you’re building in a fast-paced environment—especially when you’re optimizing for sub-120ms latency in emerging markets—that level of configuration becomes a bottleneck.
Between the complex URL syntax, the unpredictable pricing, and the latency issues caused by routing traffic through global nodes far from your actual users, I realized something: The DX (Developer Experience) is broken.

The Solution: PixoraCloud
I’m building PixoraCloud to strip away the complexity. I wanted to create a CDN that treats media delivery as a native file system, not a database query.
Here is what I’m building into the core (in Go, for maximum performance):

Semantic Routing: Your files should be where you put them. pixoramedia.cloud/WhatsApp/image.jpg is all you need to know.
Auto-Optimization: The platform detects the user's browser and device and serves the most efficient format (WebP/AVIF) automatically—no manual URL tinkering required.

Infrastructure for the Next Billion: We’re engineering this specifically to solve for latency in Africa, ensuring that developers in Lagos, Nairobi, and beyond get the same sub-120ms performance as developers in London or NY.

The "Clean DX" Vision
I’m also experimenting with a custom SDK for React and other frameworks so developers can handle media with clean components:

src={data.url}
variant="avatar"
size={80}
/>

What’s Next?
I’m currently in the lab engineering the core infrastructure in Go. I'm building this in public because I want to ensure that when we hit Beta, we’re actually solving the problems that keep you up at night.
If you’re a developer who is tired of bloated media platforms and wants a leaner, faster, and more intuitive alternative, I’d love for you to follow along or join the waitlist.
Join the waitlist: pixoracloud.pxxl.click
What’s the biggest frustration you’ve faced when implementing media delivery in your apps? Let’s chat in the comments. 👇

DEV Community: Davis Ayomide

Why I’m building a media CDN to fix the "Math Equation" URL problem