Edge pipelines that call Cloudinary securely from no-code and frontend clients - with vault-injected credentials and slim JSON responses.
You should not store Cloudinary credentials in Vue / SPA client code. Upload and transform URLs signed at the edge with API secret in Vault. RealComposer Secret Vault injects headers on Cloudflare Workers so only your edge URL is public.
You should not store Cloudinary credentials in Framer client code. Framer components hit RealComposer for signed upload parameters. RealComposer Secret Vault injects headers on Cloudflare Workers so only your edge URL is public.
To merge cloudinary assets with contentful entries, use one RealComposer pipeline with parallel steps. Resolve Contentful asset references with Cloudinary transformation metadata. Your Next.js / React app makes one request instead of several sequential upstream calls.
To merge cloudinary with shopify product images, use one RealComposer pipeline with parallel steps. Shopify product media plus Cloudinary derived URLs in one feed. Your React app makes one request instead of several sequential upstream calls.
Cloudinary payloads are heavy for Vue / SPA. Return public_id format width height only from resources list. RealComposer output mapping returns only the fields your UI needs at the edge.
Cloudinary payloads are heavy for Static HTML / Astro. Admin list endpoints mapped to thumbnail-focused schema. RealComposer output mapping returns only the fields your UI needs at the edge.
To cache cloudinary transformation api at edge, put a TTL cache on your RealComposer pipeline. Cache transformation metadata responses per public_id. Shared edge cache absorbs repeat traffic before it reaches Cloudinary.
React Native apps hit CORS and credential limits when calling Cloudinary. Sign Cloudinary uploads at the edge instead of shipping API secrets in the app bundle. Use one RealComposer edge URL with OPTIONS handling, client tokens, and vault injection.