Skip to main content
OpenCache

Serve your content from inside the network

The largest platforms localized their delivery years ago with embedded caches inside ISPs and exchanges. OpenCache makes that same model available to every content provider, free of charge: a neutral, shared cache layer operated end to end by P Foundation, with no CDN of your own to build or pay for.

Proven on real traffic

Three months of production numbers

OpenCache did not launch as a promise. Multiple content providers ran production traffic through it for three months before this page existed.

0%of on-demand requests served straight from the local cache
up to 0%of live streaming requests served locally
0 in 100on-demand requests that ever travel to the origin
~0 msof round-trip detour removed when delivery moves on-net
What it means for you

Estimate the offload

Move the slider to your monthly volume. The more you serve, the more effective the cache becomes, and the larger the share of delivery you stop paying CDN fees for. Users get local latency; your origin carries a fraction of its former load.

Cache effectiveness94%
$9,484saved per month

About 949 TB served from inside the network, bandwidth you would otherwise pay transit on at $9.99/TB.

949 TBserved from inside the network, at no cost to you
55 TBserved from your origin or partner CDN
6%of the demand your origin actually sees

Cache effectiveness climbs with volume, approaching the 97% measured on production on-demand traffic at scale. Transit billed at $9.99/TB; your figures depend on your traffic mix.

What it costs

Free to serve. Qualify to host.

OpenCache is nonprofit infrastructure, operated by P Foundation and open on equal terms.

Content providersFree

Serving through OpenCache costs nothing. Every request delivered from a local cache node is a request you no longer pay CDN fees for; partner CDNs carry only the remainder outside the footprint.

Host ISPs5 Gbps

An Embedded OpenCache PoP goes into networks that sustain more than 5 Gbps of peak OpenCache traffic. We deploy and operate it; every byte it serves on-net is a byte that never crosses your international transit links, cutting the transit bill for all participating providers' content at once.

How it works

One platform, tiered to stay local

Every node runs the same platform under one control plane; what differs is the network it serves. A miss does not jump straight abroad: it falls through to the PoP at the exchange first. Select any part of the path to see what it does.

Subscribers hit the embedded PoP in their own ISP first

ISP A subscribers
ISP B subscribers
second miss only: international transit

Subscribers served from on-net

An Embedded OpenCache PoP inside an ISP serves that ISP’s subscribers from on-net and offloads its transit. A listen-only BGP session teaches it exactly which prefixes are local, and a health score reported every 15 seconds steers traffic away from a draining or saturated PoP before users notice. Hosting one calls for more than 5 Gbps of peak OpenCache traffic.

For content providers

Onboard in four moves

You keep your origin and full authority over your content. OpenCache localizes the delivery.

Bring a domain, get the edge

Per-provider certificates are issued automatically through ACME, or you supply your own. TLS terminates inside the foundation-operated node, never on host hardware, and every client negotiates HTTP/1.1, HTTP/2, or HTTP/3 over QUIC.

Neutral by architecture

The data plane spreads. The control plane does not.

Hosting grants no control

An ISP hosting an Embedded OpenCache PoP provides space, power, and connectivity. It gains no access to provider configuration, certificates, or traffic policies.

TLS stays inside the node

Certificates live and terminate inside the foundation-operated node. A host network cannot reprioritize, alter, or selectively degrade the content its node serves.

One policy engine, every node

The same policy engine, the same observability, and the same operational team cover the whole fleet, in the same way a neutral exchange offers the same terms to every participant.

Open at the edge

The edge software is open source. Any ISP hosting a PoP, and any provider serving through one, can read exactly what runs at the edge on GitHub.

Coverage

Local where it counts, covered everywhere

OpenCache runs at multiple internet exchanges. At OpenIX Beirut, 37 peering networks carrying roughly 73% of Lebanon's traffic reach it with no transit in the path. Outside the current footprint, partner CDNs keep your audience covered globally, and as the footprint grows, more of that delivery moves local.

For ISPs

Host an Embedded OpenCache PoP

The model the hyperscaler cache programs proved, made available to everyone at once: a single footprint that offloads transit for every participating provider's content, deployed and operated by the foundation inside your network. Networks that sustain more than 5 Gbps of peak OpenCache traffic qualify.

  1. You provide rack space, power, an uplink, and a BGP session.
  2. We deploy and remotely operate the PoP: configuration, monitoring, and lifecycle are handled centrally.
  3. The PoP learns your prefixes and serves your subscribers from on-net, cutting your international transit costs.
Learn more and apply

Your audience is local. Your delivery can be too.

Apply as a content provider and start serving from inside the network, free of charge, with your origin and your authority over your content fully intact.

Newsletter

Get updates from the field

Occasional updates on our programs and products. No spam.