Cloudimage VS Purlo.dev

Purlo.dev's answer:

Purlo does one thing deliberately well: a single API call that resizes, converts (WebP/AVIF/JPEG/PNG), compresses and strips EXIF/GPS metadata — chained in one request, in a fixed, documented order. It's stateless by design — images are processed in memory and discarded immediately, never stored — and it keeps the ICC colour profile when it strips metadata, so privacy-sensitive data is removed without shifting your colours. It's not a media platform or a CDN; it's the focused "clean up an upload" step, built and priced to stay simple.

Purlo.dev's answer:

If you just need to clean and resize user uploads, the big platforms (Cloudinary, imgix, ImageKit) are more than the job asks for — more features, more concepts, and usage-based pricing to model. Purlo is cheaper and simpler: flat pricing from £5/month, a generous free tier (1,000 images/month, no card), one endpoint to learn, and a ten-minute integration. The privacy angle comes for free — images are never stored and EXIF/GPS is stripped by default. Choose Purlo when you want the upload-cleaning job done simply and affordably, not a whole media platform.

Purlo.dev's answer:

Solo developers and small teams building apps that accept image uploads — SaaS products, marketplaces, social and content apps — who need to resize, convert and strip metadata from those uploads without running their own image pipeline or paying enterprise-platform prices. Developers who value a fast, well-documented integration and a clear privacy story.

Purlo.dev's answer:

Node.js (Express) with sharp (libvips) for image processing, SQLite (better-sqlite3) for accounts/keys/usage, Stripe for billing, Resend for transactional email, and Docker behind nginx with Let's Encrypt TLS.

Purlo.dev's answer:

The problem behind Purlo is one I've watched repeat for well over a decade. Since working at the BBC around 2010, the single most common reason I've seen sites turn slow is simple: people upload full-size, unoptimised images straight off a phone or camera and wonder why their pages crawl. Even today, page weight is one of the first things I check for a new client — it's one of the most common mistakes on the web, and one of the easiest to fix. Almost every app that takes image uploads needs to resize them, convert to a web-friendly format, compress, and strip the EXIF/GPS metadata those files carry — yet most teams rebuild that same pipeline every time, security corners (resource limits, SSRF protection) included. Purlo packages that whole job into one simple, affordable API, so a developer can fix it in ten minutes instead of maintaining their own. Built and run by Axiom Testing Ltd.