Cloud platform for web services and databases
Render is a cloud platform for deploying web services, databases, cron jobs, and static sites. It sits between Heroku and AWS in complexity. nself is a self-hosted backend CLI that you run on any Linux server. The comparison is managed-PaaS vs self-hosted-stack.
See the [full comparison table](/compare) for a side-by-side view across nself, Supabase, Nhost, Firebase, and Appwrite.
Zero server management. Render handles host provisioning, OS updates, health checks, rolling deploys, and autoscaling. You push Git, Render builds and deploys. No SSH, no Docker commands, no Nginx config. Source: [Render platform](https://render.com/docs).
Managed PostgreSQL with automatic backups. Render's managed Postgres (via their infrastructure) handles daily backups, point-in-time recovery, and failover. You do not configure any of this. nself runs Postgres yourself, so you configure and run `nself backup` manually. Source: [Render Postgres](https://render.com/docs/databases).
Private network for free. Services on Render communicate over a private network with no extra cost or configuration. nself services communicate via Docker networking internally, but external service communication requires nginx configuration. Source: [Render private network](https://render.com/docs/private-services).
Pull Request previews. Render Preview Environments spin up a full-stack copy of your app (including a database fork) for each pull request. This is powerful for frontend-heavy teams. Source: [Render preview environments](https://render.com/docs/preview-environments).
Cost at scale. Render's Postgres starts at $7/mo for 1GB, $19/mo for 8GB, $97/mo for 64GB. Services start at $7/mo. A typical backend stack (service + Postgres + Redis) costs $30-70/mo. A nself stack on a $20/mo VPS (4 vCPU, 8GB RAM) runs Postgres, Hasura, Auth, Storage, and Redis for the same workload. Source: [Render pricing](https://render.com/pricing), [nself pricing](https://nself.org/pricing).
Full-stack backend in one CLI. nself installs PostgreSQL, Hasura GraphQL, nHost Auth, MinIO storage, Nginx, and optional services (Redis, Functions, Search, Mail, Media) with one command. Render requires you to deploy each service separately as individual Render services.
Plugin ecosystem. nself has 87 plugins for AI assistants, media processing, real-time chat, billing, monitoring, and email delivery. Render is a platform for running your own services; it has no installable plugin marketplace. Source: [nself plugins](https://docs.nself.org/plugins).
MIT license, fully open-source core. nself's CLI and 25 free plugins are MIT-licensed. Render is a proprietary platform. If Render's pricing changes or the service is discontinued, you need to redeploy elsewhere. nself's open-source components run anywhere. Source: [nself license](https://github.com/nself-org/cli/blob/main/LICENSE).
GraphQL API generated from your schema. nself uses Hasura to generate a full GraphQL API from your Postgres tables automatically. On Render, you write and deploy your own API server. Source: [Hasura GraphQL](https://hasura.io/docs/).
Multi-tenancy built in. nself supports multiple tenants via table prefixes and Hasura role isolation. Render does not provide multi-tenancy at the platform level. Source: [nself multi-tenancy](https://docs.nself.org/guides/multi-tenancy).
*Prices from Render's public pricing, verified April 2026.*
| Stack | nself | Render |
|-------|-------|--------|
| **Dev (single service + Postgres)** | $5/mo VPS | $14/mo ($7 service + $7 Postgres) |
| **Production (API + Postgres + Redis + Auth)** | $10-20/mo VPS | $35-70/mo (4 separate services) |
| **Scale (high traffic)** | $30-100/mo VPS | $100-500+/mo (autoscaling + larger Postgres) |
nself costs are VPS hosting only. Render costs include per-service billing for each component.
1. You want predictable flat monthly costs with no per-service billing
2. You need a complete backend stack (GraphQL, Auth, Storage, Search) without deploying each piece separately
3. You want a plugin ecosystem for AI, media, or chat features
4. Data ownership and portability matter (no vendor lock-in)
5. You are comfortable managing a Linux server via CLI
1. You want zero server management and do not want to handle OS, updates, or Docker
2. Your team needs PR preview environments with database forks
3. You want per-service autoscaling without manual intervention
4. Your app is a collection of independent microservices, not a monolithic backend stack
5. Your team is not comfortable with server administration
Moving from Render to nself. Render uses standard Postgres, so database migration is straightforward.
### Step 1: Export your Render Postgres database
# Get your Render Postgres connection string from the dashboard
pg_dump \
"postgres://USER:PASSWORD@HOST/DATABASE?sslmode=require" \
--format custom \
--no-owner \
--no-acl \
--file render_dump.pgdump### Step 2: Install nself on a VPS
# On your new Linux server (Ubuntu 22.04 recommended)
curl -fsSL https://install.nself.org | sh
nself init my-project
cd my-project
nself start### Step 3: Restore the database
nself db restore render_dump.pgdump
nself db psql -c "\dt"### Step 4: Track tables in Hasura
# Open Hasura console and track your imported tables
nself hasura console
# Track tables, configure relationships, set permissions### Step 5: Update your app's database connection
# Replace your Render Postgres URL with nself's connection string
nself db connection-string
# Update DATABASE_URL in your app's environment variables### Step 6: Point DNS to your nself server
# Update your domain's A record to your new VPS IP
nself ssl install
# SSL cert provisioned automatically**Does nself have autoscaling like Render?**
nself does not autoscale automatically. For horizontal scaling, you can run nself on larger VPS instances or add read replicas. Most apps outgrow single-server Postgres well after they need to pay $100+/mo on Render.
**Can I keep my services on Render and just move the database to nself?**
Yes. Point your Render services at nself's Postgres URL. This is a common transition path.
**What about Render's background workers?**
nself has a cron plugin (nself plugin install cron) for scheduled tasks, and the Functions plugin for background processing. Persistent workers can run as Custom Services in nself's Compose setup.
**Is nself reliable enough for production?**
nself runs the same Postgres, Hasura, and Nginx stack that thousands of self-hosted teams use in production. Reliability depends on your VPS provider and your backup setup. nself includes nself backup for automated backups and nself doctor for health checks.
**Does Render have a free tier?**
Render has a free tier for static sites and services, but free services spin down after inactivity. The Postgres free tier is limited to 256MB and one database. nself has no free cloud tier, but a $5/mo VPS gives you a full stack with no limits.
[Install nself](https://install.nself.org) | [View pricing](/pricing) | [See all comparisons](/compare)
MIT-licensed CLI. Full backend stack in 5 minutes.