Ente

TL;DR

• What it is: A fully open source, end-to-end encrypted photo storage platform with iOS, Android, web, and desktop clients
• Who it’s for: Privacy-conscious individuals and families who want Google Photos functionality without giving Google their photos
• Cost savings: Self-hosted runs for under $3/month in infrastructure costs vs. $2.99–$9.99/month for iCloud or $1.99–$9.99/month for Google One
• Key strength: Genuine end-to-end encryption audited by three independent security firms, combined with full open source code and self-hosting support
• Key weakness: Self-hosting setup has real complexity — CORS configuration, multiple services, and domain routing trip up most first-time deployers

---

What is Ente

Ente is an end-to-end encrypted photo backup and storage service. The company, Ente Technologies, builds both a hosted cloud service and a fully open source codebase that you can run on your own infrastructure. The same codebase powers both. The GitHub repository has accumulated over 25,000 stars.

The product suite includes three apps built on the same encrypted platform: Ente Photos (the main product, an alternative to Google Photos and Apple Photos), Ente Auth (a 2FA authenticator replacing the deprecated Authy), and Ente Locker (for storing sensitive documents and credentials). All three share the same end-to-end encryption architecture — client-side encryption means the server never sees your unencrypted data.

The cryptography has been independently audited by Cure53 (a German cybersecurity firm), Symbolic Software (French cryptography experts), and Fallible (an Indian penetration testing firm). That is more independent scrutiny than most consumer photo apps receive. The source code is AGPL-3.0 licensed, which means modifications must also be open source.

For users who do not want to self-host, Ente offers 10GB free and paid tiers starting at $2.49/month for 50GB. Self-hosting removes storage limits entirely — one deployer granted themselves a 100TB allocation via CLI commands.

---

Why people choose it over Google Photos, iCloud, and Proton Drive

Google Photos remains the default for most Android users. The appeal is obvious: intelligent search, face grouping, automatic albums, and free storage (up to 15GB). The tradeoff is that Google has full access to your photos and uses them in ways governed by their privacy policy. Ente’s architecture makes a structural difference — not just a policy promise — because client-side encryption means the server cannot read your photos regardless of what anyone at the company does.

iCloud Photos works well if you are in the Apple ecosystem. Apple introduced Advanced Data Protection which enables end-to-end encryption for iCloud Photos in some regions, but it requires explicit opt-in and remains off by default. iCloud is also effectively iOS/macOS-only, while Ente runs natively on iOS, Android, Windows, macOS, Linux, and web — a genuine limitation for mixed-device households.

Proton Drive is the most direct privacy-focused competitor. Proton offers end-to-end encryption with 1TB storage, GDPR and HIPAA compliance support, and a well-established privacy reputation. Ente’s advantage over Proton is the self-hosting option: Proton does not offer a self-hostable version. If data sovereignty — knowing exactly where your photos live — is the requirement, only Ente gives you that option among consumer-grade photo apps.

---

Features: what it actually does

Storage and backup

• End-to-end encryption on all data before it leaves the device
• 3x data replication across locations
• Background uploads on mobile
• Original quality retention including EXIF metadata
• HEIC format support

Organization and discovery

• Face detection and grouping (on-device machine learning)
• Semantic search — find photos by natural language descriptions
• Smart albums
• Curated memories (photos from past years, trips, celebrations)
• Hidden photos

Sharing

• Collaborative albums
• Public links with password protection
• Guest view access
• Family plans at no extra cost

Security and privacy

• Client-side encryption (server cannot read your photos)
• Audited by Cure53, Symbolic Software, and Fallible
• Legacy contact feature for account succession
• 2FA support

Platforms

• iOS (App Store), Android (Play Store and F-Droid), Web, macOS, Windows, Linux desktop

Self-hosting specifics

• Server written in Go (lightweight binary)
• PostgreSQL database
• S3-compatible object storage (MinIO, Cloudflare R2, Wasabi, etc.)
• Docker Compose deployment
• SMTP required for email notifications

---

Pricing math

Option	Monthly cost	Storage	Notes
Ente Photos (cloud) — free	$0	10GB
Ente Photos — Starter	$2.49	50GB
Ente Photos — Standard	$4.99	200GB
Ente Photos — Unlimited	$19.99	2TB
iCloud — 50GB	$0.99	50GB	Apple ecosystem only
iCloud — 200GB	$2.99	200GB
Google One — 100GB	$1.99	100GB	No E2E encryption
Ente self-hosted (Cloudflare R2)	~$0.05–$3	Unlimited	Depends on storage size

The self-hosted economics depend on your storage backend. One deployer running 11GB of photos and thumbnails on Cloudflare R2 (no egress fees) reported costs under ₹3/month (approximately $0.04). A larger library of 500GB would run roughly $5–8/month using Wasabi or Cloudflare R2 at their standard rates, plus the cost of a small VPS or existing server.

The hosted Ente pricing is competitive for what it offers — $2.49/month for 50GB with genuine end-to-end encryption beats iCloud’s equivalent tier on price. The self-hosted route makes sense primarily for users who want unlimited storage at near-zero cost, or who require data to live on their own infrastructure.

---

Deployment reality

A self-hosted Ente instance requires four components: the Museum API server, PostgreSQL, an S3-compatible object store, and a reverse proxy with SSL. Docker Compose handles the first three together.

Ricardo Pereira ran this on a Raspberry Pi. Abhay Ashokan ran it on a $5/month AWS EC2 instance with Cloudflare R2 for storage and Caddy as the reverse proxy. Meysam Azad deployed the full stack on Kubernetes using CloudNative-PG for the database and Wasabi for S3.

The step that trips people up: CORS configuration between the Museum server and your S3 bucket. If your MinIO or R2 bucket is not configured to accept requests from your Ente domain, uploads will silently fail or return opaque errors.

A second non-obvious requirement: Ente’s server needs two separate domains — one for the API and one for the storage bucket — with correct routing between them. Getting SSL certificates for both domains adds setup time.

For a developer comfortable with Docker and a reverse proxy, plan for 3–5 hours on a first deployment. Kubernetes deployment adds significant complexity and is only worth it if you are already running Kubernetes infrastructure.

---

Who should use Ente

Best fit

• Privacy-conscious individuals or families who want Google Photos features without Google’s data practices
• Users who want verifiable end-to-end encryption with published audits
• Developers or sysadmins who can manage a Docker Compose stack and want unlimited photo storage at low infrastructure cost
• Mixed-platform households (some iOS, some Android, some Windows) where iCloud is not an option
• Users moving away from Authy who need a 2FA app — Ente Auth is free and covers this

Not the right tool if

• You want a no-setup cloud solution and privacy is secondary to convenience
• Your photo library is primarily about AI editing tools (Reimagine, Magic Eraser) — Ente does not have those
• You need a self-hosted solution without internet exposure — the client apps require reachable server endpoints
• You are expecting identical feature parity with Google Photos — some AI features are less developed

---

Alternatives worth considering

• PhotoPrism — Self-hosted, AI-powered photo management. No cloud option; requires you to run your own server. Better for on-premises deployments on a NAS or homelab.
• Proton Drive — End-to-end encrypted cloud storage including photos. No self-hosting, but strong privacy reputation and GDPR/HIPAA compliance.
• Immich — Popular self-hosted alternative with a very active development community and a near-identical feature set to Google Photos. No hosted cloud option; fully self-managed.
• Lychee — Simpler self-hosted photo manager. Lighter footprint than Ente, but no E2E encryption and no mobile backup.
• Piwigo — Open source photo management supporting large collections with extensive plugin ecosystem. More suited to photo galleries than personal backup.

Sources

This review synthesizes 5 independent third-party articles along with primary sources from the project itself. Inline references throughout the review map to the numbered list below.

1. [1] ricardopereira.eu (2025-03-07) — “Self-hosting Ente Photos: My Journey to Google Photos Alternative” — deployment (link)
2. [2] abhay.app (2025-05-24) — “How I Self-Hosted Ente - And How You Can Too” — deployment (link)
3. [3] developer-friendly.blog (2025-02-24) — “Ente: Self Host the Google Photos Alternative and Own Your Privacy” — privacy (link)
4. [4] jwestall.com (2026) — “Jacob Westall Review of Ente Photos: A Private Google and iCloud Photos Alternative” — review (link)
5. [5] slashdot.org (2026) — “Ente Alternatives: Self-Hosted and Cloud Photo Management Solutions” — comparison (link)
6. [6] GitHub repository — official source code, README, releases, and issue tracker (https://github.com/ente-io/ente)
7. [7] Official website — Ente project homepage and docs (https://ente.io)

References [1]–[7] above were used to cross-check claims about features, pricing, deployment, and limitations in this review.