Show HN: Making video a software primitive (starting with generation)

Every major computing primitive followed the same path:

Text became a primitive when we had standards (UTF-8), instant rendering, near-zero cost Images became a primitive when we had standards (JPEG/PNG), CDNs, cheap storage APIs became a primitive when we had standards (REST), infrastructure (AWS), tooling

Video is next. The technology is getting there (Sora, Veo, Runway), but the infrastructure layer doesn't exist yet.

I'm building that layer.

What makes something a primitive: - Fast enough (instant or near-instant) - Cheap enough (marginal cost near zero) - Standard interfaces (abstraction layer) - Composable (programmatic manipulation) - Great DX (easy to integrate)

Current status: - Multi-provider abstraction (not locked to single API) - Intelligent routing (optimize for cost/latency/quality) - Developer-first (npm install, 5 lines of code) ```python & Node JS

pip install vloex npm install vloex

import vloex video = vloex.generate("Your content") # Auto-routes to best provider, handles failover

Test case: Auto-generate video release notes from GitHub commits Live example: https://vloex.com check live example section This is Part 1 (generation).

Vision includes composition, templating, manipulation, serving - full primitive stack.

The bet: Video generation hits "fast enough + cheap enough" in 2-3 years. When it does, every app will use video. They'll need infrastructure.

This is that infrastructure. YC's current RFS: "Treat video as a computing primitive, not an output"

The question: Am I building at the right time, or 2 years too early?

Docs: https://api.vloex.com/docs

Code: https://github.com/vloex/vloex-python

Honest feedback welcome.

PS: I have few slots for beta users and design partners that are interested in video space so do let me know or connect with me at [email protected]

Comments URL: https://news.ycombinator.com/item?id=45496299

Points: 1

# Comments: 0