Application hosting / PaaS: read the guide

Render

HostedPaaS

Your fastest path to production for any workload

Homepage Docs Pricing

Scanned 15 Oct 2026 · Schema v5 · features v21

From: $7/mo
Workspace plans Hobby $0/mo, Pro $25/mo, Scale $499/mo, Enterprise custom; compute and storage billed separately, services prorated by the second.
Free tier: Not documented
Hobby $0/mo plus free instance options, subject to limitations; free web services spin down on inactivity; free Postgres expires after 30 days.
Isolation: Container
shares the host kernel
Regions: 5
United States (West) · United States (East) · United States (East) · Germany (EU) · Singapore (Asia)
Capabilities: 24 / 61
8 partial · 29 fail · 0 not assessed
Agent readiness: 11/11 · 11/11
read · drive, pre-login surface

Advertised for

Web services (HTTP) · Static sites (CDN) · Private services · Background workers (queues/schedulers/agents) · Cron jobs · Workflows (durable long running) · Managed Postgres · Key Value (Redis compatible)

Built for

Developers, then mixed

· git-connected services + Dockerfile/Blueprints
· REST API + OpenAPI + CLI + SSH
· 'cloud for builders', web service/worker/cron vocabulary

01 Pricing Workspace plans Hobby $0/mo, Pro $25/mo, Scale $499/mo, Enterprise custom; compute and storage billed separately, services prorated by the second.

Tier	EntryHobby (workspace)	Pro (workspace)	Scale (workspace)	Enterprise (workspace)	Instance: free	Instance: 0.5c-512mb	Instance: 1c-2g	Instance: 2c-4g	TopInstance: 8c-32g
Price	$0/mo	$25/mo	$499/mo + compute	Custom pricing	$0/mo	$7/mo	$25/mo	$85/mo	$450/mo
Includes	Personal projects/prototypes; Free + Starter instances; community support	Production apps/agents; autoscaling, high availability, more instance tiers, longer log retention	Advanced governance and compliance; SAML SSO, HIPAA workspaces, advanced RBAC	Dedicated support and uptime SLAs; contact sales	512 MB / 0.1 CPU; spins down on inactivity	512 MB / 0.5 CPU; always-on	2 GB / 1 CPU	4 GB / 2 CPU	32 GB / 8 CPU (12c-96g reaches $1,500/month)
Transfer	5 GB	25 GB	1000 GB	—	—	—	—	—	—
Transfer overage	$0.15/GB	$0.15/GB	$0.15/GB	—	—	—	—	—	—

Free tier: Hobby $0/mo plus free instance options, subject to limitations; free web services spin down on inactivity; free Postgres expires after 30 days.

per instance/month (prorated by the second); GB-month for disks/DBs·Card required: No·render.com

Overages: Persistent disks $0.25/GB-month; Postgres expandable storage $0.30/GB-month; outbound bandwidth beyond plan allowance $0.15/GB. Key Value up to 50GB at $750/month; Postgres up to 1024GB RAM at $11,000/month. Dedicated outbound IP set $100/month (Pro+).

02 Website design Desktop public website · assessed 15 Oct 2026

Complete assessment.

A white, grid-led developer website with oversized black typography, thin rules, square controls and selective violet technical motifs; documentation preserves the brand while adding a dense navigation rail.

Swiss-inspired
Technical illustration

Landing page: captured
Pricing: captured
Docs: captured

03 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Containershares the host kernel

Persistence

All service local files are ephemeral by default across restarts/redeploys. Attach a persistent disk on supported paid services; managed Postgres and Key Value provide separate persistence.

Snapshots / forks

Persistent-disk snapshots + managed Postgres backups for data recovery; NO copy-on-write fork/snapshot of a running service instance.

Resources & limits

Storage

Persistent disks $0.25/GB-month; expandable Postgres storage $0.30/GB-month. Managed Postgres up to 1024 GB RAM; Key Value up to 50 GB RAM/storage ($750/month).

Limits & quotas

Services and workers up to 12 CPU / 96 GB RAM ($1,500/month), with smaller free and paid tiers; workspace limits, autoscaling and workflows concurrency vary by plan.

GPU

None — no GPU compute. (The 'Accelerated' tiers are high-performance Postgres, not GPUs.)

Access

Deploy interface

git-pushdockerfilecontainer-imagecliapimcpdashboardtemplate

SDK languages

TypeScriptPython

Network & secrets

Egress controls

Dedicated static outbound IP sets on Pro+ for $100/month per three-address set. This enables external allowlisting, not destination-filtering outbound policy.

Secrets

Environment variables, secret files, and environment groups (shared across services).

Bring your own cloud

No — Render is a fully-managed platform; no bring-your-own-cloud / run-in-your-VPC option advertised.

Placement & use

Jurisdiction

5 regions: Oregon, Ohio, Virginia (USA), Frankfurt (Germany), Singapore.

Advertised workloads

Web services (HTTP)Static sites (CDN)Private servicesBackground workers (queues/schedulers/agents)Cron jobsWorkflows (durable long running)Managed PostgresKey Value (Redis compatible)

04 Capabilities 24 pass · 8 partial · 29 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 2/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Partially supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Partially supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Not supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 5/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Supported

Custom domainsBring-your-own domain via CNAME/DNS.

Supported

Public preview URLsShareable per-deploy / per-branch URLs.

Supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 6/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 3/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Not supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Partially supported

Data 2/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 4/6

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Partially supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Supported

Organisation & security 2/9

Built-in authPlatform-provided authentication / IAM for workloads.

Not supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Supported

SharingShare a running workload/resource via link (optionally gated).

Partially supported

BYOCRuns inside the customer's own cloud account.

Not supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Partially supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Not supported

05 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

10 full · 1 partial · 100% of applicable checks

llms.txt
Supported
“Rich root /llms.txt (metadata, permissions, scope, conventions) + a dedicated api-docs.render.com/llms.txt for the API.”
llms-full.txt
Supported
“api-docs llms.txt indexes all pages in Markdown + endpoints in OpenAPI; docs are markdown-native; modular set.”
robots.txt AI policy
Supported
“https://render.com/robots.txt explicitly allows major AI agents; Content-Signal: ai-train=yes, search=yes, ai-input=yes.”
JSON-LD
Supported
“homepage carries Organization + WebSite + SoftwareApplication JSON-LD.”
Sitemap
Supported
“robots Sitemap -> sitemap-index.xml (site + docs + community sitemaps). (Root /sitemap.xml 404 but the canonical index exists.)”
Meta tags
Supported
“Complete title + description + OG, descriptive ('The cloud for builders').”
Markdown negotiation
Supported
“Markdown served broadly: docs *.md, api-docs *.md, per-agent guides (claude.md/codex.md/cursor.md/opencode.md).”
Content efficiency
Partially supported
“Fresh extracted visible-text/raw HTML byte ratio 1.3337%; partial by rubric.”
Docs discoverable
Supported
“docs first-class in nav; reachable; api-docs separate site.”
Machine-readable pricing
Supported
“Pricing page has structured instance/Postgres/Key Value tier tables.”
No anti-bot wall
Supported
“Fresh anonymous browser, HTTP and well-known fetches accessed public content without a bot challenge. Community sitemap DNS fails separately.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

11/11

10 full · 1 partial · 100% of applicable checks

Public API
Supported
“Full REST API with a dedicated reference site (api-docs.render.com): services, deploys, env vars, secret files, etc.”
OpenAPI spec
Supported
“Published OpenAPI spec (api-docs.render.com/docs/api-spec.md) — usable with Postman/Insomnia / client codegen.”
MCP server
Supported
“Hosted MCP at mcp.render.com/mcp, discoverable via /.well-known/mcp + a server-card.json. Verified Model Context Protocol.”
SDK packages
Supported
“Official TypeScript and Python Workflows SDKs: https://render.com/docs/workflows-sdk-typescript.md and https://render.com/docs/workflows-sdk-python.md”
Auth documented
Supported
“Authentication reference (Bearer RENDER_API_KEY).”
Self-serve credentials
Partially supported
“https://render.com/agents.md: Only a human can authorize access; OAuth approval or human-provided environment API key required.”
Webhooks
Supported
“https://render.com/docs/webhooks.md documents webhook-signature verification.”
CLI tool
Supported
“Official Render CLI (render.com/docs/cli).”
Error model
Supported
“https://api-docs.render.com/openapi/render-public-api-1.json defines JSON error id/message/code and stable machine-readable errorCode.”
Rate limits documented
Supported
“Dedicated Rate Limiting reference (api-docs.render.com/reference/rate-limiting.md).”
Agent config files
Supported
“Many surfaces: agents.md + per-agent guides (claude/codex/cursor/opencode) + official skills (render-oss/skills) + /.well-known/mcp + dual llms.txt.”

06 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 5

Claude Code Anthropic
Supported
“Render works with agentic tools like Claude Code, Cursor, Codex, and OpenCode through the Render MCP server and official Render skills. ... Claude Code + Render: Set up Claude Code with Render MCP and Render skills.”
Source render.com
Cursor Anysphere
Supported
“Cursor + Render: Add Render MCP and skills to Cursor so your editor agent can inspect services, update env vars, read logs, and manage deploy workflows in context.”
Source render.com
Codex CLI OpenAI
Supported
“Codex + Render: Connect OpenAI Codex to Render so it can inspect services, read deploy logs, draft Blueprints, and manage deploy workflows from the CLI.”
Source render.com
OpenCode opencode
Supported
“OpenCode + Render: Configure OpenCode with the Render plugin, MCP, and skills for an open-source terminal workflow.”
Source render.com
Pi earendil-works
Supported
“Pi uses the Render Pi package to add Render skills and hosted MCP tools for services, deploys, logs, metrics, and databases.”
Source render.com

Plausible compatibility 11

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

Aider
Amp
Antigravity
Devin
Droid
Gemini CLI
Goose
Hermes Agent
Kilo Code
Kiro CLI
Qwen Code

07 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 4

ISO/IEC 27001
certifiedhosted
“ISO 27001 (compliance reports and agreements validate our commitment to information security best practices).”
Source render.comConfidence: high
SOC 2 Type II
certifiedhosted
“SOC 2 Type 2.”
Source render.comConfidence: high
HIPAA
self-attestedhostedHIPAA-compliant platform + BAA; no third-party HIPAA certification body. Higher plans.
“Build and scale healthcare applications on a compliant platform.”
Source render.comConfidence: high
GDPR
self-attestedhosted
“GDPR-DPA.”
Source render.comConfidence: high

Regions 5

United States (West)Oregon
United States (East)Ohio
United States (East)Virginia
Germany (EU)Frankfurt
Singapore (Asia)Singapore

5 regions + global CDN for static sites.

Legal

Privacy notice Terms of service

08 Company & presence Facts only, not scored

Company

Headquarters: San Francisco, California; distributed remote team
Founded: —
Team size: 100–200 (vendor-declared structured data, not independently verified)
Hiring: Open roles

Activity

Last release: 2026-10-01: updated Key Value plans render.com
Last blog post: 2026-10-08: Data needs its DevOps moment render.com

Presence 6

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from render.com's unauthenticated pages, docs, pricing and repository on 15 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All PaaS products →