Back to catalog
Openinary
AGPL-3.0Open-source, self-hosted media server replacing Cloudinary with on-the-fly URL transformations, modern WebP and AVIF optimization, and S3 storage.
Open-source alternative to — compare it against:
Overview
Cloudinary charges recurring subscriptions based on transformation credits and bandwidth tiers that escalate rapidly as web properties scale their responsive image derivatives. Openinary moves that transformation pipeline directly onto your own infrastructure, parsing URL-based manipulation queries and caching optimized formats against any S3-compatible bucket. Self-hosting the stack gives teams complete custody over original assets and eliminates metered processing charges entirely.
Why Openinary instead of Cloudinary
The primary integration advantage of Openinary is syntax parity with Cloudinary's established URL structure. Developers configure responsive image sources or dynamic video thumbnails using familiar path tokens like /t/w_800,h_600,c_fill/photo.jpg. Swapping an existing client library or templating helper requires changing the base host URL rather than rewriting transformation logic across application views. Storage integration is equally direct: instead of storing masters inside proprietary cloud silos, Openinary hooks straight into AWS S3, Cloudflare R2, or a local MinIO bucket defined through standard environment variables. Community automations, including community n8n nodes and deployment recipes for Coolify and Dokploy, make integrating the server into existing self-hosted stacks straightforward.
What Openinary lacks compared to Cloudinary is an integrated global content delivery network and an expansive suite of proprietary media algorithms. Cloudinary offers automated multi-CDN edge caching, generative AI content expansion, enterprise digital asset management, and complex dynamic video splicing. With Openinary, global edge caching requires placing your own CDN or caching reverse proxy in front of the origin container. Transforming heavy media also shifts computational load from a managed SaaS fleet onto your host CPU, making server sizing and concurrency planning essential for bursty workloads.
What it does well
- URL-driven transformations process resizing, cropping, gravity adjustments, and quality tuning dynamically on request without pre-rendering derivative files.
- Pluggable storage integrations connect directly to local MinIO instances, AWS S3 buckets, and Cloudflare R2 endpoints using standard S3 API credentials.
- Automated format negotiation inspects incoming client headers to serve WebP or AVIF variants instead of bulky JPEG originals without database schema adjustments.
