Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
End-to-end encrypted photo and video backup — Ente Photos, with its self-hostable server, museum. Files and metadata are encrypted on your device before upload, and face recognition and natural-language search run on your phone or desktop rather than the server. Apps for iOS, Android, desktop and web.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (192 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 install tested), Raspberry Pi 5 (8 GB) (arm64 install tested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick Ente when the reason you are leaving Google Photos is that someone else can see your library — and you want that to stay true on your own server. Files and metadata are end-to-end encrypted on the device, face recognition and magic search run in the mobile and desktop apps, and the server (museum, a Go binary) runs on upstream's 1 GB floor under AGPL-3.0. If you would rather have smart search in the browser and a server that does the indexing for you, Immich is the catalog's other phone-backup pick.
Follow the Ente deploy guide →Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# Ente — the official quickstart (generates compose.yaml + museum.yaml with random credentials), images pinned by digest, behind Caddy for automatic HTTPS, per our Ente deploy guide
# needs a domain with four A records (photos. api. albums. files.) pointed at this server and ports 80/443 open; Ente's own ports bind 127.0.0.1 only
cd ~ && printf 'n\n' | sh -c "$(curl -fsSL https://raw.githubusercontent.com/ente/ente/main/server/quickstart.sh)" # n = do not start yet; we edit the files first
cd ~/my-ente
echo "BASE=example.com" > .env
BASE=$(grep '^BASE=' .env | cut -d= -f2)
# pin the images (digests tested in our guide) so a later pull cannot change the release
sed -i -e 's|image: ghcr.io/ente/server$|image: ghcr.io/ente/server@sha256:3511ff25db3bf950abeb3983928eeadeed7f53b690ee94704c14be72fa719b1d|' -e 's|image: ghcr.io/ente/web$|image: ghcr.io/ente/web@sha256:b043ffe32d612f7def09268d13c688e524ed4edd019406a3368b30c38b7e9e5a|' -e 's|image: pgsty/silo$|image: pgsty/silo@sha256:635197cb9f36d01bee221d34d1c7d7960f6a95c48b0b6c01d99cd13bdae51a46|' compose.yaml
# bind the published ports to loopback and point the web app at the API
sed -i -e 's|^\(\s*- \)\(8080:8080\) # API|\1127.0.0.1:\2|' -e 's|^\(\s*- \)\(3000:3000\) # Photos web app|\1127.0.0.1:\2|' -e 's|^\(\s*- \)\(3002:3002\) # Public albums|\1127.0.0.1:\2|' -e 's|^\(\s*- \)\(3200:3200\) # MinIO API|\1127.0.0.1:\2|' -e "s|ENTE_API_ORIGIN: .*|ENTE_API_ORIGIN: https://api.$BASE|" compose.yaml
# the object store must be reachable at a real address: museum hands clients a pre-signed URL, and localhost on a phone is the phone
sed -i -e 's|^\(\s*\)are_local_buckets: true|\1are_local_buckets: false|' -e "s|endpoint: localhost:3200|endpoint: files.$BASE|" -e "s|public-albums: .*|public-albums: https://albums.$BASE|" museum.yaml
cat > docker-compose.override.yml <<'EOF'
services:
caddy:
image: caddy:2
restart: always
ports: ["80:80", "443:443"]
environment:
BASE: ${BASE}
volumes: ["./Caddyfile:/etc/caddy/Caddyfile:ro", "caddy_data:/data"]
depends_on: [museum, web, minio]
volumes:
caddy_data:
EOF
cat > Caddyfile <<'EOF'
api.{$BASE} {
reverse_proxy museum:8080
}
photos.{$BASE} {
reverse_proxy web:3000
}
albums.{$BASE} {
reverse_proxy web:3002
}
files.{$BASE} {
reverse_proxy minio:3200
}
EOF
sudo docker compose up -d # → Photos on https://photos.BASE, API on https://api.BASE
# keep museum.yaml safe: it holds the credentials for the data in the volumes; create your account as soon as HTTPS answersEnte's self-hosting docs are candid about where a new install goes wrong, and end-to-end encryption adds a rule of its own:
The Ente install snippet is marked verified on Ubuntu 26.04 (Nov 2026).
Ente's requirements page asks for a minimum of 1 GB of RAM and 1 CPU core for the cluster the quickstart script starts. The server is a Go binary, and the heavy work — encryption, face recognition and search indexing — happens on the client devices, not on the server.
Yes — Ente's quickstart script (it needs Docker Compose 2.30 or newer) creates a my-ente folder with compose.yaml and museum.yaml, and offers to start museum (the API on port 8080), the web app (Photos on 3000, public albums on 3002), PostgreSQL and a MinIO-style S3 bucket on 3200. Keep museum.yaml safe: upstream warns that without its credentials Ente cannot access the data in the volumes.
The quickstart sets the bucket endpoint to localhost:3200, and museum hands that address to clients inside pre-signed upload URLs. On a phone, localhost is the phone itself, so the upload never reaches the bucket. Set the endpoint in museum.yaml to an address both the server and your devices can reach — a LAN IP or a domain behind a reverse proxy.
It is the one to pick if privacy is the reason you are leaving: photos and metadata are end-to-end encrypted, and face recognition and magic search run on your own phone or desktop. The desktop app imports a Google Takeout export and reads its JSON metadata. The trade-offs are no machine-learning search in the web app, and no way back in if you lose both your password and your recovery key.