Layer 5 · self-hosting reality check
What it actually takes to self-host Appsmith
The docs say 8 GB. The Docker docs say to plan for at least 8 GB on the host for the all-in-one container. In practice you want 8 GB with 2 vCPU. That is Appsmith's own baseline for standard deployments, which it describes as an entry point for pilots and low traffic rather than a production guarantee. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Retool alternatives, where Appsmith is one of the picks.
Wondering whether you need to at all? Is Retool free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 8 GB. The Docker docs say to plan for at least 8 GB on the host for the all-in-one container |
|---|---|
| RAM — what it really needs | 8 GB with 2 vCPU. That is Appsmith's own baseline for standard deployments, which it describes as an entry point for pilots and low traffic rather than a production guarantee |
| CPU | 2 vCPU baseline (vendor) |
| Disk | Keep 10–15 GB free, per the vendor's best-practice page. The internal databases, Git-connected app data and local backups all live in the /appsmith-stacks volume and grow together. |
| Monthly cost | $24–48/mo on an 8 GB VPS. MongoDB, Redis and PostgreSQL run inside the one container, so nothing else is required |
| Setup time | 20 minutes to a working instance; an hour with a domain, HTTPS and a scheduled backup |
| How you install it | One docker compose service. Use the appsmith-ce image for the Apache-2.0 Community edition; the docs default to appsmith-ee, which runs on a free plan. Either image bundles MongoDB, Redis, PostgreSQL, a reverse proxy and supervisord |
| Ongoing maintenance | The vendor recommends updating every two weeks on a pinned tag, with nightly appsmithctl backups stored off the box. Backups are encrypted with a password you must not lose; Appsmith says a forgotten password makes the backup impossible to restore. |
| Where it stops scaling | One 8 GB box for pilots and light internal use. For production, high availability or scale, Appsmith recommends Kubernetes with MongoDB and Redis moved out to external services. |
The thing that catches people out
Appsmith has checkpoint versions you cannot jump over. Anything older than v1.96 must stop at v1.99 before going to 2.x, because 2.0 ships MongoDB 7 and the migration for it lives in v1.96–v1.99. Appsmith's June 2026 notice says skipping that step makes the upgrade fail, external MongoDB included. The checkpoint docs add that you will see failures in the logs and have to roll back. Instances older than v1.9.2 face a second checkpoint before that. It catches people who left an instance alone for a year. Take an appsmithctl backup, then step through each checkpoint in order.
When not to self-host Appsmith
You need SAML or OIDC sign-in (Enterprise, from $2,500/mo for 100 users), granular role permissions (Business, $15 per user/mo) or audit logs (Enterprise). If 8 GB of server is more than the tool is worth to you, Appsmith's cloud free plan covers up to 5 users.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does Appsmith actually need?
- 8 GB with 2 vCPU. That is Appsmith's own baseline for standard deployments, which it describes as an entry point for pilots and low traffic rather than a production guarantee in practice. The documented minimum is 8 GB. The Docker docs say to plan for at least 8 GB on the host for the all-in-one container, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU baseline (vendor) alongside it.
- What does self-hosting Appsmith cost per month?
- $24–48/mo on an 8 GB VPS. MongoDB, Redis and PostgreSQL run inside the one container, so nothing else is required This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for the vendor recommends updating every two weeks on a pinned tag, with nightly appsmithctl backups stored off the box. Backups are encrypted with a password you must not lose; Appsmith says a forgotten password makes the backup impossible to restore.
- How long does it take to set up Appsmith?
- 20 minutes to a working instance; an hour with a domain, HTTPS and a scheduled backup, via One docker compose service. Use the appsmith-ce image for the Apache-2.0 Community edition; the docs default to appsmith-ee, which runs on a free plan. Either image bundles MongoDB, Redis, PostgreSQL, a reverse proxy and supervisord.
- When should I NOT self-host Appsmith?
- You need SAML or OIDC sign-in (Enterprise, from $2,500/mo for 100 users), granular role permissions (Business, $15 per user/mo) or audit logs (Enterprise). If 8 GB of server is more than the tool is worth to you, Appsmith's cloud free plan covers up to 5 users.
- What is the most common mistake when self-hosting Appsmith?
- Appsmith has checkpoint versions you cannot jump over. Anything older than v1.96 must stop at v1.99 before going to 2.x, because 2.0 ships MongoDB 7 and the migration for it lives in v1.96–v1.99. Appsmith's June 2026 notice says skipping that step makes the upgrade fail, external MongoDB included. The checkpoint docs add that you will see failures in the logs and have to roll back. Instances older than v1.9.2 face a second checkpoint before that. It catches people who left an instance alone for a year. Take an appsmithctl backup, then step through each checkpoint in order.