xhostd vs Render: one app plan or independently sized services

Render offers web services, background workers, and managed databases that you can size independently. xhostd includes hosting, PostgreSQL, object storage, and isolated environments in one plan, managed through the AI coding agent you already use. Both support full-stack applications and MCP. xhostd is a strong fit when you want the core stack ready with fewer separate resource decisions and a predictable monthly price.

What xhostd and Render both offer

Both xhostd and Render run full-stack apps in containers that an AI coding agent can deploy and manage.

• Always-on web services and background workers (on paid compute plans on Render).
• Builds from git, including your own Dockerfile.
• Managed PostgreSQL for your app.
• An official hosted MCP server for AI agents.
• Custom domains with automatic certificates and no seat fees.

The differences are in how resources are priced, what the free plan includes, and how far an app can scale.

Key differences between xhostd and Render

One plan or separately priced resources

xhostd: Fixed monthly plans: Basic is free, then Builder costs $10, Indie $20, Studio $40, and Pro $80. The plan covers hosting, PostgreSQL, and S3-compatible storage for each code-running environment.

Render: The workspace plan is Hobby (free), Pro ($25 a month), or Scale ($499 a month). Paid services and databases are priced on top. Free Postgres is 1 GB, has no backups, and expires after 30 days. Render has no native object storage.

Why it matters: On xhostd the database and file storage are part of one price from the start. On Render they are separate items to size and pay for, and a free database lasts only 30 days.

Always on, even on the free plan

xhostd: Every app runs in an always-on container on every plan, Basic included, with no sleep mode and no cold starts. Workers, bots, and queue consumers run on the free plan too.

Render: Free web services spin down after 15 minutes idle and take about 1 minute to wake. Free covers 750 instance-hours a month at 0.1 CPU and 512 MB, with no disks and no free workers. Background workers need a paid compute plan, from 0.5 CPU and 512 MB.

Why it matters: On a free Render app, the first visitor after 15 quiet minutes waits about a minute. On xhostd every request reaches a running app, and a free bot keeps running.

No bandwidth overage

xhostd: xhostd has no traffic or egress charges on any plan. xhostd might throttle disproportionate traffic after contacting you.

Render: Hobby includes 5 GB of bandwidth, Pro 25 GB, and Scale 1 TB. Each GB over the allowance costs $0.15.

Why it matters: A launch or a large download can push a Render bill past the plan price. On xhostd traffic doesn't change the bill.

Preview data on every plan

xhostd: Every plan, Basic included, has separate production, staging, and preview channels. Within the plan price, each channel has its own app, URL, files, and settings, and each code-running channel also has its own database.

Render: Full preview environments need Pro ($25 a month) or higher. They copy Postgres, Key Value, and disks, but the copies are empty. Preview resources bill per second.

Why it matters: On xhostd you can test a change against its own database on the free plan, and the preview doesn't add to the bill.

Compute and runtime

xhostd: Each channel runs in an always-on container, on every plan, with no sleep mode and no cold starts. You can run a static site on nginx, an app on a template with Node.js 22, Python 3.13, and uv, or your own Dockerfile. CPU is a guaranteed share that can burst to 2x, from 0.1 core on Basic to 4 cores on Pro, and memory is an account total from 128 MB to 8 GB. A process has no run time limit, so workers, bots, and queue consumers keep running.

Render: Render runs web services, private services, background workers, and cron jobs, from native runtimes or Docker. Paid compute plans run from 0.5 CPU and 512 MB of memory up to 12 CPU and 96 GB, they stay on, and Pro and higher workspaces can autoscale. On the free plan a web service gets 0.1 CPU and 512 MB for up to 750 instance-hours a month, and it stops after 15 idle minutes, with about a minute to wake.

Summary: Both run always-on containers for web services and background workers. The difference: xhostd keeps every plan on with up to 4 cores, while Render's free web services spin down and its paid plans reach 12 CPU with autoscaling.

Deploys and AI agents

xhostd: Every app has its own git repository. A push stores the code, and a deploy publishes a chosen branch or commit; GitHub-connected apps can also deploy on each push. Every deploy passes a health check before a blue-green switch, and a failed deploy leaves the previous version serving. Agents work through a hosted MCP server, an HTTP API with an OpenAPI spec, and plugins for Claude Code and Codex.

Render: Render deploys from git, Docker images, or Blueprints, and automatic deploys are available, as is deployment rollback. Its official hosted MCP server can create services, static sites, cron jobs, Postgres, and Key Value, trigger deploys, set environment variables, read logs and metrics, and run read-only SQL. The MCP server can't delete or scale services. A service with a persistent disk has no zero-downtime deploys.

Summary: Both deploy from git, including your own Dockerfile, can deploy automatically on each GitHub push, and offer an official hosted MCP server. The difference: xhostd hosts a git repository for each app, while Render can also deploy a prebuilt image from a registry and define services in a Blueprint file.

Database

xhostd: Every code-running channel gets its own PostgreSQL database, included in the plan. Your app receives a main connection, a direct connection for migrations, and a read-only connection; on newer database servers the main connection is pooled through PgBouncer in transaction mode. PostGIS is available. Database storage is an account total across all your apps and channels, from 500 MB on Basic to 80 GB on Pro, as a soft limit: xhostd reaches out instead of stopping your app.

Render: Render Postgres is a managed database that you provision and pay for separately from your services. A free database holds 1 GB, has no backups, and expires after 30 days. Paid databases add high availability and read replicas, and Render also offers Key Value. A database exports separately from disks.

Summary: Both offer managed PostgreSQL. The difference: xhostd includes a database in every code-running channel, while Render prices each database separately and adds high availability and read replicas on paid databases.

File storage

xhostd: Each channel gets its own S3-compatible bucket, so standard S3 libraries work. Versioning is always on, and old versions and deleted files are kept for 120 days. File storage is an account total across all your apps and channels, from 2 GB on Basic to 400 GB on Pro, as a hard limit. Files are served through your app; there are no public object URLs.

Render: Render has no native object storage, so object storage comes from an external provider. Paid services can attach a persistent disk with daily snapshots kept for at least 7 days, but a service with a disk runs as a single instance. Free web services get no disks.

Summary: Similar: both can keep files for your app. The difference: xhostd gives each channel an S3-compatible bucket, while Render offers persistent disks on paid services and leaves object storage to an external provider.

Environments and previews

xhostd: Production, staging, and previews are separate channels. Each channel is its own container with its own URL, file bucket, environment overrides, up to 5 custom domains and, for code-running apps, its own PostgreSQL database. A new preview starts with an empty database, so tests never touch production data. Channels come from one account-wide pool: 3 on the free plans, then 10, 20, 40, or 80.

Render: Render offers service previews and, on Pro ($25 a month) and higher, full preview environments. A preview environment gets its own copies of Postgres, Key Value, and disks, which start empty. Preview resources bill per second, and environment groups share settings across services.

Summary: Both give a full preview its own empty database, away from production data. The difference: xhostd offers previews on every plan within its channel pool, while Render's full preview environments need Pro and bill per second.

User sign-in

xhostd: Google sign-in is built into every channel and custom domain, on every plan, with no OAuth app to create. After sign-in, your app receives a signed token with the user's ID, email, and name, and verifies it against xhostd's public keys. Your app decides which pages need sign-in.

Render: Render doesn't include sign-in for your app's users. Your app brings its own, through an authentication library or an external identity provider.

Summary: Similar: on both, your app checks who is signed in. The difference: xhostd provides Google sign-in on every plan with no OAuth app to create, while Render leaves sign-in to a library or an external identity provider.

Backups and recovery

xhostd: Nightly snapshots cover the database and files, and xhostd also takes a snapshot before each deploy. Free plans keep 24 hours of nightly snapshots and the last pre-deploy snapshot; paid plans keep 7 days and the last 3. A restore can run read-only, behind a maintenance page, or live, and a code rollback boots the previous image without a rebuild. xhostd restores to these snapshots, not to any chosen moment.

Render: Paid Render Postgres has point-in-time recovery for 3 days on Hobby and 7 days on Pro and higher, and logical exports are kept for 7 days. The free database has no backups. Persistent disks get daily snapshots kept for at least 7 days, and deployment rollback returns a service to an earlier deploy.

Summary: Both back up data and roll back code. The difference: xhostd's nightly and pre-deploy snapshots cover both the database and the files, while Render offers 3 to 7 days of point-in-time recovery for paid Postgres and daily disk snapshots.

Networking and domains

xhostd: Every channel gets an HTTPS address, and each channel can add up to 5 custom domains with automatic certificates, on every plan. Paid plans add one public TCP endpoint per channel, with an optional IP allowlist.

Render: Render supports custom domains with automatically managed TLS certificates. Public web services use HTTP, and private services and private links connect services privately. Render runs services in five regions (Oregon, Ohio, Virginia, Frankfurt, and Singapore), and static sites are served from a global CDN.

Summary: Both offer custom domains with automatic certificates. The difference: xhostd adds a public TCP endpoint on paid plans, while Render offers five regions, a CDN for static sites, and private links between services.

Logs and monitoring

xhostd: You get deploy and runtime logs, including logs from earlier containers, plus health findings with latency percentiles (p50, p95, and p99) and resource readings. Visitor analytics show visits, unique visitors, top pages, broken links, and status codes, without adding a script to your pages.

Render: Render provides service logs, metrics, and health monitoring, and logs are kept 7 days on Hobby, 14 days on Pro, and 30 days on Scale and Enterprise. Built-in visitor analytics are not documented.

Summary: Both provide logs, metrics, and health monitoring. The difference: xhostd also reports visitor analytics, which Render doesn't document.

xhostd and Render pricing

xhostd: Fixed monthly plans: Basic free, Builder $10, Indie $20, Studio $40, and Pro $80. For example, Builder includes 10 channels, 0.5 CPU core, 1 GB of memory, 10 GB of database storage, and 50 GB of file storage. Hosting, PostgreSQL, storage, and backups are included, with no traffic, egress, or seat charges; xhostd might throttle disproportionate traffic after contacting you. See xhostd plans.

Render: Since April 23, 2026, the workspace plan is Hobby (free), Pro ($25 a month flat, previously $19 per seat), or Scale ($499 a month flat), with no seat fees. Compute, databases, and disks are priced per service on top. Included bandwidth is 5 GB on Hobby, 25 GB on Pro, and 1 TB on Scale, with $0.15 per GB beyond it.

Summary: Neither charges per seat. The difference: xhostd's plan price covers hosting, the database, storage, and traffic, while Render adds each service, database, and bandwidth overage to the workspace fee.

Price example: On xhostd, a small always-on app with PostgreSQL and file storage costs $0 on the free Basic plan (0.1 CPU core, 128 MB of memory), or $10 a month on Builder (0.5 core, 1 GB). On Render, a free web service sleeps after 15 idle minutes and free Postgres expires after 30 days, so an always-on app with a lasting database needs paid instance and database plans.

Where xhostd is a better fit

xhostd is the stronger choice when:

• You want a free app or bot that stays on. xhostd's Basic plan keeps containers running with no sleep mode, while free Render web services spin down after 15 idle minutes and free workers aren't available.
• You want object storage without another provider. Each xhostd channel has an S3-compatible bucket with versioning, and Render has no native object storage.
• You want previews with their own database on any plan. xhostd channels start on Basic, while Render's full preview environments need Pro at $25 a month and bill per second.
• You expect more traffic than a bandwidth allowance covers. xhostd has no bandwidth charges, while Render charges $0.15 per GB beyond 5 GB on Hobby and 25 GB on Pro.

Where Render is a better fit

Consider Render if you want:

• Autoscaling and large machines. Render autoscales on Pro and higher, with machines up to 12 CPU and 96 GB of memory. xhostd's largest plan, Pro, has 4 cores and 8 GB.
• Point-in-time recovery and read replicas. Render Postgres can restore to any moment in the last 3 days on Hobby or 7 days on Pro, and offers read replicas. xhostd restores to its nightly and pre-deploy snapshots.
• More free memory. Render's free web services get 512 MB, but they sleep after 15 minutes idle, and free Postgres expires after 30 days. xhostd's free plan has 128 MB, never sleeps, and keeps its database.

xhostd vs Render at a glance

	xhostd	Render
Compute model	Always-on containers	Web services, workers, cron jobs
Sleep and cold starts	None, on every plan	Free services sleep after 15 minutes
Run time limit	None	Long-running services; limit not documented
Languages and Docker	Node.js, Python, any Dockerfile	Native runtimes and Docker
Database	PostgreSQL in every code-running channel, included	Render Postgres, priced separately
File storage	S3-compatible bucket per channel, included	Paid disks; no object storage
Previews with their own data	Yes, every channel	Pro and higher; copies start empty
Point-in-time recovery	No; nightly and pre-deploy snapshots	Yes, 3 to 7 days
AI agent access	Hosted MCP server, API, plugins	Official hosted MCP server
Pricing model	Fixed plans, $0 to $80	Workspace fee plus per-service pricing