Layer 5 · self-hosting reality check
What it actually takes to self-host Ente Photos
The docs say 1 GB. In practice you want 2 GB for the server components. 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 Google Photos alternatives, where Ente Photos is one of the picks.
Wondering whether you need to at all? Is Google Photos free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | 1 GB |
|---|---|
| RAM — what it really needs | 2 GB for the server components |
| CPU | 2 vCPU |
| Disk | Library size; the server stores encrypted blobs |
| Monthly cost | $15–30/mo plus object storage |
| Setup time | 2–3 hours — it is the most involved of the three |
| How you install it | docker compose: Go server, PostgreSQL, and an S3-compatible object store |
| Ongoing maintenance | Moderate. Self-hosting is supported but the hosted product is the main path. |
| Where it stops scaling | Fine for personal and family libraries; object storage carries the growth. |
The thing that catches people out
Everything is end-to-end encrypted, which is the reason to choose Ente and also the reason recovery is unforgiving: lose the key and the server operator — you — genuinely cannot help. There is no password reset that recovers data. Write the recovery key down somewhere physical before you upload anything you care about.
When not to self-host Ente Photos
You want server-side search or ML over your library. Encryption means the server cannot see the photos, so that work happens on the client.
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 Ente Photos actually need?
- 2 GB for the server components in practice. The documented minimum is 1 GB, which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU alongside it.
- What does self-hosting Ente Photos cost per month?
- $15–30/mo plus object storage This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for moderate. Self-hosting is supported but the hosted product is the main path.
- How long does it take to set up Ente Photos?
- 2–3 hours — it is the most involved of the three, via docker compose: Go server, PostgreSQL, and an S3-compatible object store.
- When should I NOT self-host Ente Photos?
- You want server-side search or ML over your library. Encryption means the server cannot see the photos, so that work happens on the client.
- What is the most common mistake when self-hosting Ente Photos?
- Everything is end-to-end encrypted, which is the reason to choose Ente and also the reason recovery is unforgiving: lose the key and the server operator — you — genuinely cannot help. There is no password reset that recovers data. Write the recovery key down somewhere physical before you upload anything you care about.