# Brume vs Render

> Render autoscales and runs Postgres with failover, at a price per instance. Brume, still in alpha, puts apps, databases and backups on one server you own.

Alpha 0.1 · in progress. This is https://brume.dev/vs/render in Markdown, for agents and terminals.

|  | Brume | Render |
| --- | --- | --- |
| Where it runs | Your own server, one VPS in alpha 0.1 | [Render's platform, in 5 regions](https://render.com/docs/regions) |
| Who holds your data | You: your server and your S3 bucket | [Render, on AWS and GCP](https://render.com/security) |
| Price | Free. You pay for your VPS and your bucket | [Free tier; instances from $7/month; Pro $25/month](https://render.com/pricing) |
| Lock-in | Plain containers, no config file in your repo, a documented bucket format | [render.yaml Blueprints, Render's IaC format](https://render.com/docs/infrastructure-as-code) |
| Databases | PostgreSQL, MongoDB and Redis templates | [Managed Postgres and Key Value (Valkey)](https://render.com/docs/key-value) |
| AI agents | A CLI and a local MCP server. Irreversible actions wait for your approval | [Hosted MCP server, open source](https://render.com/docs/mcp-server) |
| Scaling and regions | One server, no autoscaling | [Autoscaling on Pro, up to 100 instances](https://render.com/docs/scaling) |
| Compliance | No certifications: it runs on infrastructure you pick | [SOC 2 Type 2, ISO 27001](https://render.com/security) |
| License | Free and open source (FSL-1.1-ALv2, Apache 2.0 after two years) | [Platform source not public; MCP server is Apache-2.0](https://github.com/render-oss/render-mcp-server) |
| Maturity | Alpha 0.1, in progress | [4.5M+ developers; Series C extension in 2026](https://render.com/blog/series-c-extension) |

Facts checked on November 1, 2026 in each project's official docs. "If the panel is hacked" is our reading of them. Brume is shown in its recommended modes: Cloudflare Tunnel and Tailscale.

## Where Brume is different

- Databases and their backups live on your server and your bucket.
- Brume is free: you pay for the VPS and bucket, not per instance.
- Your AI agent can do what the panel does. Irreversible actions wait for you.

## Where Render is better today

- Autoscaling on CPU or memory, up to 100 instances.
- Managed Postgres with point-in-time recovery and a standby for failover.
- A free tier for prototypes, and no server to run.

**Pick Render if…** You need autoscaling, Postgres with point-in-time recovery, or ISO 27001 and HIPAA.

**Pick Brume if…** Your load fits one VPS and you want apps, databases and backups on it, at its price.

## Install

```sh
curl -sSL https://brume.dev/install.sh | bash
```

Needs a fresh Debian or Ubuntu VPS and an S3-compatible bucket. Cloudflare and Tailscale recommended.

## Other comparisons

- [Brume vs Railway](https://brume.dev/vs/railway)
- [Brume vs Fly.io](https://brume.dev/vs/fly)
- [Brume vs Vercel](https://brume.dev/vs/vercel)
- [Brume vs Heroku](https://brume.dev/vs/heroku)

---

## More from brume.dev

Every page in Markdown. The whole site in one file: https://brume.dev/llms-full.txt. The index: https://brume.dev/llms.txt

- [Home](https://brume.dev/index.md)
- [Architecture](https://brume.dev/architecture/index.md)
- [Roadmap](https://brume.dev/roadmap/index.md)
- [Compare](https://brume.dev/vs/index.md)
- Brume vs [Coolify](https://brume.dev/vs/coolify/index.md), [Dokploy](https://brume.dev/vs/dokploy/index.md), [CapRover](https://brume.dev/vs/caprover/index.md), [Portainer](https://brume.dev/vs/portainer/index.md), [Kamal](https://brume.dev/vs/kamal/index.md), [Dokku](https://brume.dev/vs/dokku/index.md), [Easypanel](https://brume.dev/vs/easypanel/index.md), [Railway](https://brume.dev/vs/railway/index.md), [Render](https://brume.dev/vs/render/index.md), [Fly.io](https://brume.dev/vs/fly/index.md), [Vercel](https://brume.dev/vs/vercel/index.md), [Heroku](https://brume.dev/vs/heroku/index.md)