Playground
Imgix Playground
Asset ProxyRun real requests through the Cachely edge proxy and see how server-side token injection, edge caching, asset URL rewriting, preview bypass, and AI transforms work for Imgix.
Choose a provider
Every provider has its own playground
Asset proxy demo — route Imgix-processed images through your tenant edge domain while preserving all rendering parameters.
Asset URLs rewritten to tenant domainImgix rendering params preservedGlobal edge cachingSingle-domain delivery
Integration facts (verified against the SDK)
- SDK module
- Asset proxy — no SDK module
- Built-in provider id
- Not applicable (asset-only)
- Real SDK exports used
- None — asset URL rewriting only
- CLI setup
- Not a CLI provider — configure asset URLs manually.
Recommended: Asset proxy — serve assets through the tenant domain (no CMS/API SDK)
✓ Supported ◐ Partial — Not applicable
Asset Proxy- —Not applicable
API proxy
- What it does
- Routes CMS API calls through the Cachely edge.
- Use it for
- Hiding tokens, caching CMS responses, using one tenant domain.
- Benefit
- Faster repeated reads, safer public apps, unified delivery.
- —Not applicable
Server-side token injection
- What it does
- Keeps CMS credentials on the edge/server side.
- Use it for
- APIs that normally require private tokens.
- Benefit
- The token never ships to the browser.
- ✓Supported
Edge cache
- What it does
- Caches CMS/API responses at the edge.
- Use it for
- Repeated content reads and high-traffic pages.
- Benefit
- Lower origin/CMS usage, faster responses, better resilience.
- ✓Supported
Asset URL rewriting
- What it does
- Rewrites CMS asset URLs inside JSON responses to your tenant domain.
- Use it for
- Serving images/assets from the same delivery layer.
- Benefit
- Fewer third-party domains, edge delivery, simpler security policy.
- ✓Supported
Preview / bypass mode
- What it does
- Skips the cache for fresh CMS/editor preview content.
- Use it for
- Preview flows, draft content, editor QA.
- Benefit
- Editors see fresh content without disabling production cache.
- —Not applicable
AI transforms
- What it does
- Applies a named AI transform profile to eligible JSON/text responses.
- Use it for
- Localization, summaries, formatting, content adaptation.
- Benefit
- Transform responses without changing the CMS or app code.
- —Not applicable
Native SDK integration
- What it does
- Wraps the provider SDK and automatically proxies its requests.
- Use it for
- Nuxt/Next apps that already use the CMS SDK.
- Benefit
- Minimal code changes, safer defaults.