One Edge Domain for Your CMS API & Assets

Route CMS APIs and media through one edge domain — cached globally, credentials off the client, bandwidth costs cut. Works with Contentful, Prismic, Sanity, Storyblok, Shopify, and more.

Start free Run a Live Demo
Live platform activity
Real traffic routed through Orinami edge nodes.
35.9K Requests routed
104.2 GB Bandwidth delivered
$31.06 Estimated savings

Replace scattered CMS origins with one controlled edge layer — routing, caching, and credential isolation handled before traffic reaches your app.

Trusted by teams at

ExpediaLeonardo.AiGV

Why Orinami

One Domain. Everything Your CMS Delivers.

Orinami gives every project a single edge domain that handles both API responses and media delivery — cached globally, with credentials that never leave the server.

Lower bandwidth costs

Edge caching reduces origin requests and CMS bandwidth bills. Use the savings calculator below to estimate your cost reduction.

One domain, API and assets

API responses and media flow through a single edge domain per project — no scattered origins, no credentials in the browser.

Global edge caching

Content is cached across 300+ locations worldwide. Cached responses return in under 10ms, wherever your users are.

Multi-project ready

Each project gets its own domain, cache, and usage tracking. Manage one site or a hundred from a single dashboard — ideal for agencies.

Works with your headless CMS

ContentfulPrismicSanityStoryblokShopifyCloudinaryImgixGeneric HTTPS

Savings Calculator

See How Much You Save

Compare what you pay your CMS for bandwidth today versus routing through Orinami. Most teams save 60% or more.

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

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

Getting Started

Up and running in three steps

Create a project, connect your CMS, and point your URLs to your new edge domain. Caching, credentials, and delivery are handled from there.

  1. 1. Create your project

    Sign up free, give your project a name, and choose your CMS. You'll get a dedicated *.cmsassets.com edge domain in under a minute.

  2. 2. Route your CMS through it

    Use the API proxy to route all CMS requests through the edge — credentials hidden, responses cached — or use the asset proxy for media-only delivery.

  3. 3. Deploy — done

    Your CMS traffic now flows through the edge. Caching, bot protection, and bandwidth tracking are active from the first request.

Takes about 5 minutes. Start for free →

API Delivery

API Proxy

Proxy CMS API requests through your edge domain. Credentials stay server-side, JSON responses are cached globally, and asset URLs in the response are rewritten to your domain automatically.

Learn more

Media Delivery

Asset Proxy

Serve images, videos, and files through the same edge domain — globally cached, bandwidth-tracked, and bot-protected. No changes to your CMS or API setup.

Learn more

Live Demos

See Orinami in Action

Pick a CMS and watch a real request flow through your edge domain — credentials injected server-side, response cached, 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
Try Demo
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
Try Demo
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
Try Demo
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
Try Demo
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
Try Demo

FAQ

Everything worth knowing before you sign up

Who is Orinami for?

+
Developers and teams using a headless CMS — Prismic, Contentful, Sanity, Storyblok, Shopify, and others — who want lower delivery costs, faster responses, and credentials off the client. Especially useful for agencies managing multiple projects.

What problem does Orinami solve?

+
Your CMS charges for every byte it delivers. Orinami routes API calls and media through one edge domain per project — origin requests drop, responses are cached globally, and your bandwidth costs shrink without changes to your CMS or app logic.

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 $15/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.cmsassets.com), 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 Orinami 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. Orinami caches full responses and handles partial content requests correctly.
✦
Still have questions?Ask Orinami Copilot about features, pricing, integrations, or whether it fits your setup.
Ask Copilot →