Render
Render is a cloud computing platform that provides a wide range of services, including web hosting, cloud computing, and application development. Render offers several hosting options, including static site hosting, web application hosting, and managed databases.
What detecting Render tells you about a site
Render is a developer-focused cloud host that runs web services, static sites and databases. You infer it from delivery rather than a loud vendor banner: sites served from onrender.com subdomains (or custom domains fronted by Render's edge), its TLS/CDN response characteristics, and x-render-* style headers on some responses. Spotting it signals a small-to-mid team that wanted Heroku-like git-push deploys without managing infrastructure — typically an indie product, a startup MVP or a side project where simplicity and predictable pricing beat hyperscaler flexibility.
Render in a real-world stack
When you find Render, it rarely travels alone. Commonly hosts Node, Python or Go services with a managed PostgreSQL/Redis, fronting a React/Next.js or static front end.
About
Render is a cloud computing platform that provides a wide range of services, including web hosting, cloud computing, and application development. Render offers several hosting options, including static site hosting, web application hosting, and managed databases.
Categories: PaaS
Quick facts
Detection methodology for PaaS
Platform-as-a-Service offerings show up as response headers and deployment domains. Heroku's `Server: Cowboy` plus `*.herokuapp.com`; Render's `*.onrender.com`; Fly.io's `*.fly.dev`. We pair the host detection with framework signals so you can tell what's running on the platform — a Heroku dyno serving Rails looks very different from a Heroku dyno serving Node, even though both fit the same hosting fingerprint.
How we detect Render
Sourcemap Explorer carries 1 fingerprint signal for Render, spread across 1 channel — response header. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.
Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.
Server-side fingerprint: the response header reveals the technology behind the page. Visible in DevTools → Network → response headers.
x-render-origin-server: Render
FAQ
How do I check if a website is using Render?
Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. Render's specific fingerprints here are response header, and the popup flags Render whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.
What Render version can Sourcemap Explorer detect?
Render ships as a hosted paas rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.
How much does Render cost?
Render's pricing model is documented as: low, freemium, payg, recurring. Detection is independent of the pricing tier — Sourcemap Explorer flags the technology by its fingerprints, regardless of which paid plan a site is on. See the official site for the current pricing page.
Where can I read more about Render?
Official site: https://render.com. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.
Keep reading on Sourcemap Explorer
Alternative tools
Detected by Sourcemap Explorer
Open the popup on any page running Renderand you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.