We run a small CDN on purpose.
Zipzy CDN started as internal infrastructure for delivering downloads and static assets for our own products. We opened it up because we couldn't find anything this simple elsewhere.
Team
Two people run the infrastructure side day to day — capacity planning, TLS renewal, node health, incident response. A third handles support and the parts of the product that aren't pure ops. That's it, that's the org chart.
We've turned down a few "let's make this a proper company" conversations. Not because we're against growing, just because the current shape is what let us keep it this simple, and simple is the actual product.
Infrastructure
Capacity planning, TLS renewal, node health, incident response.
Support
Email-first, same-day response target on business days. See contact.
Product
Features ship only after they've proven necessary on our own traffic first.
Timeline
How we got here
Built for internal use
Started as a single node serving downloads for our own products.
Opened to the public
Turned the internal tool into a product after enough people asked to use it.
Six nodes, still small
Grew the network to six locations across two continents — see the network map.
Want to reach us?
Support, sales, or just curious how something works.