One edge layer for content delivery

Cache APIs and assets close to users, refresh content when it changes, and see every delivery request from one dashboard.

Start free View integrations
New Free Site Audit — test your website
Live platform activity
Real traffic routed through Cachely edge nodes.
1.5M Requests routed
138.1 GB Bandwidth delivered
3.8% Cache hit rate

Built for sites with more than one backend.

Built for

Fast-moving teams shipping content-heavy websites.

From product teams to agencies managing dozens of client projects.

Why this exists

Your frontend depends on content, media, commerce, and APIs

Modern sites pull content, media, products, previews, and assets from several services. Each one has its own cache rules, limits, domains, and debugging tools. That works — until performance, cost, and delivery issues are spread everywhere.

  • Slow API responses
  • Too much origin traffic
  • Scattered cache rules
  • Hard-to-debug delivery
  • No single view

What Cachely does

Route those requests through Cachely

Your app keeps using the same CMS, commerce, and media services. Cachely sits in front of them, so traffic can be cached, rewritten, measured, refreshed, and protected before it reaches the origin.

What's inside

Everything you need to control content delivery

Cache API responses, media assets, and selected website traffic at the edge. Manage domains, cache rules, webhooks, usage, request logs, and AI transforms from one place. Use the SDK with the tools you already have.

Delivery layer

API Proxy

Cache API responses at the edge. Keep tokens server-side.

Learn more

Delivery layer

Asset Proxy

Serve images, video, and files through the same cached layer.

Learn more

Control plane

Custom Domains

Run APIs and assets on your own domain instead of vendor hosts.

Learn more

Control plane

Webhooks

Refresh cache when editors publish, without redeploying.

Learn more

Control plane

Analytics

See which APIs and assets are requested, how often, and from cache or origin.

Learn more

Security & reliability

Security

Keep origins, tokens, and cache refresh paths behind the edge.

Learn more

AI transforms

Response Transformer

Rewrite JSON responses server-side, then cache the result at the edge.

Learn more

SDK & integrations

CMS Integrations

One SDK across CMS, commerce, media providers, and generic HTTPS APIs.

Learn more

Integrations

Works with the stack you already use

Connect a CMS, commerce API, media provider, or any HTTPS origin. Cachely is designed for mixed stacks — one SDK across providers, with provider-aware adapters underneath.

ContentfulPrismicSanityStoryblokShopifyCloudinaryImgixGeneric HTTPS
Explore CMS integrations →

Playground

Watch real requests move through the edge

Pick a provider and watch a request flow through a Cachely edge domain — credentials injected server-side, responses cached, and asset URLs rewritten automatically.

Prismic API Proxy

Full API proxy demo — fetch Prismic content through your tenant domain with server-side token injection and automatic asset URL rewriting.

  • API requests proxied through /~api
  • Asset URLs rewritten in JSON response
  • Server-side token injection
Open Playground
Contentful API Proxy

Full API proxy demo — query Contentful entries through the edge proxy with credentials hidden from the client and asset URLs rewritten.

  • API requests proxied through /~api
  • Space-aware asset URL rewriting
  • Token never leaves the edge
Open Playground
Sanity API Proxy

Generic fetch recipe — proxy Sanity GROQ queries through your tenant domain using createGenericProvider. No dedicated SDK submodule yet.

  • GROQ endpoint exposed via /~api
  • API token can be injected at the edge
  • JSON content is AI-transform eligible
Open Playground
Storyblok API Proxy

Generic fetch recipe — proxy Storyblok CDN stories through your tenant domain using createGenericProvider. No dedicated SDK submodule yet.

  • CDN stories endpoint via /~api
  • Preview/draft mode via bypass
  • JSON content is AI-transform eligible
Open Playground
Cloudinary Asset Proxy

Asset proxy demo — serve Cloudinary images and videos through your tenant domain with edge caching and bandwidth control.

  • Asset URLs rewritten to tenant domain
  • Cloudinary transformations preserved
  • Edge-cached delivery
Open Playground
Imgix Asset Proxy

Asset proxy demo — route Imgix-processed images through your tenant edge domain while preserving all rendering parameters.

  • Asset URLs rewritten to tenant domain
  • Imgix rendering params preserved
  • Global edge caching
Open Playground
Generic API Proxy

Define a custom provider for any CMS or asset origin. Route both API requests and assets through one tenant domain.

  • Custom apiHosts and assetHosts
  • Works with any HTTPS origin
  • API + asset proxy combined
Open Playground

Getting Started

Up and running in three steps

Create a project, point your CMS through Cachely, and add control as the project grows.

  1. 1. Create your project

    Sign up free, give your project a name, and choose the CMS or origin you want to route through the edge.

  2. 2. Route APIs and assets

    Use the API proxy for CMS data, the asset proxy for media, or both through one controlled delivery layer.

  3. 3. Add control as needed

    Add custom domains, webhooks, analytics, and security controls as the project moves toward production.

Takes about 5 minutes. Start for free →

Origin impact

Less origin traffic. More predictable delivery.

When repeated API and asset requests are served from the edge, your CMS and media providers do less work. Lower cost is one result. Faster, more predictable delivery is the bigger win.

GB
M
Prismic Direct$15.00per month50 GB × $0.30/GB
Cachely Pro$19.00per month$19.00 base
Your Savings$0.00 per month
$0.00per year
Cost comparison$15.00
Cachely Pro Prismic bandwidth cost

Ready to start saving? See what's included on each plan →

Free Site Audit

Not sure where to start?

Run a free Site Audit. Cachely checks your site’s delivery setup and shows where caching, security, or origin protection can help — no sign-up required.

Run free Site Audit View docs

FAQ

Everything worth knowing before you sign up

Who is Cachely for?

+
Developers and teams building content-heavy websites with CMS, commerce, media, or custom APIs. Cachely is especially useful when one frontend depends on several services and you want caching, custom domains, analytics, refresh controls, and credentials off the client.

What problem does Cachely solve?

+
Modern sites pull from several services — CMS, commerce, media, previews, and assets. Cachely puts one edge layer in front of those requests, so they can be cached, rewritten, measured, refreshed, and protected in one place. Lower origin traffic and lower bills are useful side effects; the main win is having one observable delivery layer instead of scattered vendor origins.

Is there a free plan?

+
Yes — free forever, no credit card required. The free plan includes 1 project, 500,000 requests/month, and 5 GB bandwidth. When you're ready for production, Pro is $19/month with 5M requests, 200 GB bandwidth, unlimited projects, and pay-as-you-go overage.

How do we integrate it into an existing site?

+
Create a project, point your CMS URLs to your new edge domain (e.g. your-project.cachely.io), and optionally enable the API proxy for data fetches. Integrate with the SDK, CLI agent, or a small URL change in your CMS client. No infrastructure rebuild needed.

What’s the difference between asset proxy and API proxy?

+
The asset proxy handles media delivery — images, videos, and files cached at the edge with bandwidth tracking and bot protection. The API proxy handles CMS API requests — credentials injected server-side, JSON responses cached, and asset URLs in the response rewritten to your edge domain automatically.

How fast is Cachely compared to the direct CMS CDN?

+
Cached responses return in under 10ms from the nearest edge location. First requests fetch from your CMS origin and cache the response globally, so subsequent visitors anywhere get near-instant delivery.

Does it work with multiple sites or brands?

+
Yes. Each project gets its own edge domain, cache, and usage tracking — perfect for agencies managing multiple clients. The Pro plan includes unlimited projects.

What about video and large files?

+
Videos and large assets are fully supported, including Range requests for streaming. Cachely caches full responses and handles partial content requests correctly.
✦
Still have questions?Ask Cachely Copilot about features, pricing, integrations, or whether it fits your setup.
Ask Copilot →