Playground
Generic Playground
Generic Fetch + API 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 Generic.
Choose a provider
Every provider has its own playground
Define a custom provider for any CMS or asset origin. Route both API requests and assets through one tenant domain.
Custom apiHosts and assetHostsWorks with any HTTPS originAPI + asset proxy combinedFull createGenericProvider control
Integration facts (verified against the SDK)
- SDK module
- @cachely-io/sdk (generic recipe)
- Built-in provider id
- No — must use
createGenericProvider(provider: 'generic'would throw) - Real SDK exports used
createGenericProvidercreateCachelyFetch- CLI setup
- Writes a generic createGenericProvider recipe with placeholder hosts.
Recommended: createGenericProvider + createCachelyFetch for any HTTPS origin
✓ Supported ◐ Partial — Not applicable
Generic Fetch + API Proxy- ✓Supported
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.
- ✓Supported
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.
- ✓Supported
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.