About

Shipping a frontend build to a cache should not need a plugin, a dashboard tour or a purge button. You publish a versioned release, it propagates, and the URL is fast from the first request. That is the entire product.

How it works

Releases are written once to replicated origin storage and pushed to Tier 1 PoPs over a private mesh. Other PoPs fill on demand from the nearest shield. Objects are immutable, so there is no invalidation protocol to get wrong and a popular asset effectively never leaves the cache.

What we leave out

No server-side rendering, no edge functions, no per-user request logs. Marina serves bytes that were already public and stays out of the way. Access logs are aggregated by package and PoP and kept for 30 days.

Public packages from open-source projects are served free of charge. Commercial and private releases are billed per terabyte of egress, with no charge for requests or publishes.

Questions, abuse reports and PoP requests go to hello@cdnmarina.com. Security disclosures: security@cdnmarina.com. We read everything.