Ente.io

Private photo storage, honestly reviewed. No marketing fluff, just what you get when you leave Google Photos.

TL;DR

• What it is: End-to-end encrypted photo and video storage — think Google Photos, but the encryption keys never leave your device and the company literally cannot see your photos [website].
• Who it’s for: Privacy-conscious individuals and families who want Google Photos-level polish without Google’s surveillance business model. Also founders and developers who want a self-hosted solution with real encryption, not just “we promise we don’t look” [website][testimonials].
• Cost savings: Google One’s 100GB plan runs $1.99/mo; 2TB runs $9.99/mo. Ente’s equivalent tiers are priced competitively, and self-hosting moves the cost to a VPS bill instead of a recurring subscription. The math gets meaningful at the 200GB+ level.
• Key strength: Genuinely end-to-end encrypted — including face recognition, which runs on-device so even Ente’s servers never see who’s in your photos [website]. Independently audited cryptography [website]. 25k+ GitHub stars [website].
• Key weakness: Self-hosting is more involved than most alternatives. The server stack requires Go, PostgreSQL, MinIO (or S3-compatible storage), and Redis. This is not a one-Docker-container weekend project.

---

What is Ente.io

Ente is an end-to-end encrypted photo and video backup service. The pitch is simple: your photos are encrypted on your device before they leave it, stored in multiple geographic locations, and nobody — including Ente’s own engineers — can decrypt them without your key [website].

That’s a meaningful promise in a market where “private” usually means “we don’t sell to third parties” rather than “we can’t read your files.” Ente means the stronger version.

The project is fully open source under GPL-3.0 and AGPL licenses. The client apps — iOS, Android, web, Linux, macOS, Windows — have been open source for years. The server code was open-sourced later, enabling genuine self-hosting [website]. The cryptographic implementation was independently audited by Nadim Kobeissi of Symbolic Software, who noted: “Ente is really cool. End-to-end encrypted photo backup/sync (unlike Google Photos), truly multiplatform (unlike iCloud Photos), and fully open source (unlike both!)” [testimonials].

As of this writing, the consolidated GitHub repository sits at 25,000+ stars [website]. The original “frame” repo was retired when Ente open-sourced their server and consolidated everything into a single monorepo.

The company is small. This is both a feature (responsive, fast-moving, responsive to user feedback) and a risk (less institutional stability than Google). Multiple user reviews cite bug fixes pushed within hours or days of reporting [testimonials]. One user: “I had a small issue with the app and they pushed an update in under 10 hours. The issue was completely resolved.” [testimonials].

---

Why People Choose It

The migration pattern from Ente’s user base is almost always the same: Google Photos → growing discomfort with Google’s data practices → search for something with actual encryption → land on Ente.

The testimonials on the website make this clear. One user’s criteria checklist: “zero-knowledge encryption, displays thumbnails quickly, handles ‘live’ iPhone photos without separating them, respects HEIC format, retains original quality and EXIF metadata, allows for cross-platform syncing and family sharing” [testimonials]. That’s a demanding list, and Ente hits all of it.

Versus Google Photos. Google Photos offers unlimited storage up to 2TB for $9.99/mo, excellent machine learning, and deep integration with the Android ecosystem. It also trains on your photos (or at minimum, uses aggregate signal) and operates under Google’s privacy policy. Ente’s E2E encryption makes that trade-off impossible by design — if the keys never reach the server, the server can’t do anything with the content [website]. For users who left Google specifically because of this, Ente is the only serious hosted option.

Versus iCloud Photos. iCloud is excellent on Apple hardware and falls apart everywhere else. No Android app, no real Linux support, minimal sharing features beyond Apple’s walled garden. Multiple reviewers cite Ente’s cross-platform story as a decisive factor [testimonials]. iCloud also isn’t E2E encrypted by default (Advanced Data Protection, added in 2022, optionally enables it — but it’s opt-in and still not audited by an independent party).

Versus Immich. Immich is the privacy-focused alternative for power users — it’s faster, has a richer admin interface, and its Docker setup is cleaner for self-hosting. But Immich is explicitly not encrypted. It stores photos as-is on your filesystem. If you’re running it at home on a trusted network, that’s fine. If you want genuine zero-knowledge encryption — where even if someone gets your server, they get ciphertext — Immich doesn’t provide that. Ente does.

Versus Nextcloud Photos. Nextcloud is the general-purpose self-hosted file storage solution that happens to include a photo gallery. The photos module is serviceable but it’s not the product’s core focus. Ente is purpose-built for photos: face recognition, timeline view, curated memories, smart albums — the features you actually use in Google Photos, rebuilt around encryption.

The honest competitive positioning: Ente is for people who want Google Photos’ UX in a privacy-respecting wrapper, and are willing to pay for it or self-host it.

---

Features

Based on the official website [website]:

Core storage:

• End-to-end encryption for all photos and videos — client encrypts before upload [website]
• Stored in 3 geographic locations for redundancy [website]
• Original quality preservation, HEIC/HEIF support, EXIF metadata retention [testimonials]
• 10GB free forever tier [website]

Photo intelligence (all on-device):

• Face recognition and grouping — runs locally, no faces sent to server [website]
• Zero-knowledge AI search — natural language queries (“beach 2022”, “birthday dinner”) processed without server seeing content [website]
• Curated memories — automated highlights from past trips and events [website]

Organization:

• Smart Albums [website]
• Hidden photos [website]
• Public links and shared albums for collaboration inside and outside Ente [website]
• Comments and likes on shared content [website]
• Widgets for memories, albums, and people [website]

Family and sharing:

• Family plans — share your subscription with up to 5 family members at no extra cost per seat [website]
• Guest view via public links [website]
• Album collaboration with external users [website]

Privacy hygiene:

• No ads, no tracking, no training on your photos [website]
• Independent cryptographic audit [testimonials]
• Legacy contact — designate who gets access to your photos if something happens to you [website]

Self-hosting:

• Full server stack is open source [website][github]
• GPL-3.0 license [github]

What’s missing or unclear:

• Video handling beyond basic storage and playback — one user note mentions “automated compressed video previews for quick viewing” as a missing feature [testimonials]
• Third-party integrations are minimal — Ente is a closed ecosystem by design; the encryption model makes API access to content structurally difficult
• No Lightroom-style editing or advanced photo management tools; this is backup and organization, not an editing suite

---

Pricing: SaaS vs Self-Hosted Math

Ente Cloud (their managed service):

• Free: 10GB, forever, all features [website]
• Paid tiers exist for 50GB, 200GB, and higher storage — exact current pricing at https://ente.io/pricing (pricing page not included in source data for this review; check directly)
• Family plans: storage shared across up to 6 members, typically priced as a single subscription

Google One for comparison:

• 100GB: $1.99/mo
• 200GB: $2.99/mo
• 2TB: $9.99/mo
• No family plan at the lower tiers without a Google One upgrade

Self-hosted Ente:

• License: $0 (GPL-3.0)
• Infrastructure: VPS ($5–15/mo), S3-compatible object storage (Backblaze B2, MinIO, Wasabi — typically $0.006/GB/mo at Backblaze for photo storage), PostgreSQL and Redis (can share a VPS)
• Your time: meaningfully more than simpler self-hosted tools

Concrete math for a family at 500GB:

At Backblaze B2 at $0.006/GB/mo, 500GB of object storage runs $3/mo. A Hetzner VPS to run the server at ~€4/mo. Total infrastructure: roughly $7–8/mo for self-hosted Ente covering a family of 5.

Google One Family plan with 2TB runs $9.99/mo — but that 2TB is shared with Google Drive and Gmail, and you’re still in Google’s data environment.

The self-hosted savings become real at scale. At 2TB of photos, self-hosted Ente runs roughly $14/mo in storage (Backblaze) plus ~$5 in server costs: $19/mo. Google One 2TB is $9.99/mo. In this case, self-hosting doesn’t save money on storage costs — but it gets you off Google’s infrastructure, genuine E2E encryption, and full data ownership. That’s the actual trade-off: privacy over cost at scale.

---

Deployment Reality Check

This is where Ente differs sharply from something like Activepieces or Immich. Self-hosting Ente is a multi-component deployment:

What you need:

• A Linux VPS (2GB+ RAM recommended)
• Docker and docker-compose
• PostgreSQL database
• Redis
• S3-compatible object storage (MinIO locally, or Backblaze/Wasabi/AWS externally)
• A domain with TLS (Caddy or nginx)
• SMTP for user invitations and recovery codes

The official server code lives at https://github.com/ente-io/ente with a server/ directory containing Docker configuration. The repository also contains all client apps in the same monorepo.

What can go sideways:

• MinIO configuration is non-trivial if you’ve never worked with S3-compatible object storage. Common issues: bucket policies, CORS settings for the web client, and getting pre-signed URL generation working correctly.
• The Go server has more configuration surface area than a simple application — you’ll be editing a YAML config file with multiple service endpoints.
• Data migration from Google Photos or iCloud requires the Ente desktop app or CLI tools — the process works but takes time for large libraries.
• Recovery codes are critical. Because everything is E2E encrypted, if you lose your master key and recovery code, your photos are unrecoverable — not “contact support,” literally mathematically unrecoverable [website]. This is the correct behavior for true E2E encryption, but it requires users to understand the stakes.

Realistic time estimate: A technically capable user who has deployed Dockerized applications before should budget 3–6 hours for a working Ente server. That includes configuring storage, getting TLS working, and testing upload/download from a mobile app. For someone new to self-hosting, this is a weekend project.

Managed alternative: Ente’s own cloud service offers identical features without the operational burden. For privacy use cases, the meaningful question is whether you trust Ente (small company, audited crypto, open source) versus whether you want to own the infrastructure entirely.

---

Pros and Cons

Pros

• Genuinely end-to-end encrypted. Not “encrypted at rest,” not “we promise we don’t look” — mathematically zero-knowledge, independently audited [website][testimonials]. This is the actual differentiator.
• On-device face recognition. Google Photos-style face grouping without sending face data to any server [website]. Remarkable engineering.
• Cross-platform without compromise. iOS, Android, Linux, macOS, Windows, web — all first-class clients [website]. Not an afterthought.
• Family plans included. Sharing a subscription across up to 5 members at no per-seat cost is meaningfully better than most competitors [website].
• Responsive team. Multiple user reviews cite under-48-hour bug fixes and genuinely responsive support [testimonials]. This matters for a small team.
• 25k+ stars. Meaningful signal for a focused privacy tool, not a general-purpose platform [website].
• GPL-3.0 + full server open source. You can audit every line, self-host completely, and your photos aren’t hostage to Ente’s business continuity [github].
• 10GB free forever — not a trial, not a countdown [website].

Cons

• Self-hosting is involved. Multi-component stack (Go server, PostgreSQL, Redis, S3) means this isn’t beginner self-hosting. Immich is significantly easier to deploy [github].
• Video compression not available. One user specifically flags missing automated compressed video previews for quick mobile viewing [testimonials]. For heavy video users, this is a UX gap.
• Ecosystem is intentionally closed. The encryption model makes third-party integrations structurally difficult. No IFTTT, no Zapier, no API for apps to read your photos.
• Small company risk. This is a small team. Not YC-backed, not enterprise-funded. If the company doesn’t survive, the open-source code continues but the hosted service stops. Plan accordingly.
• Recovery is unforgiving. Lose your master key and recovery code → photos are permanently unrecoverable. This is cryptographically correct but operationally risky for non-technical users [website].
• No AI editing or filters. Ente is a backup and organization tool, not a photo editor. If you want AI enhancements, background replacement, or color grading, you need something else.
• Pricing page not included in research data — exact current tier prices require checking https://ente.io/pricing directly.

---

Who Should Use This / Who Shouldn’t

Use Ente if:

• You left (or are leaving) Google Photos because you’re genuinely uncomfortable with Google seeing your family photos.
• You need cross-platform sync — Android phone, iPad, Linux desktop — without Apple’s or Google’s ecosystem walls.
• You want a family photo sharing solution where the provider literally cannot access your memories.
• You’re comfortable with (or willing to learn) multi-container Docker deployments, or you’ll use Ente’s managed cloud.
• You have a library of 50GB–2TB of photos and the math on Backblaze + VPS works for your situation.

Skip it (use Immich instead) if:

• You want the easiest possible self-hosted photo manager and don’t need encryption at-rest on the server side.
• You want advanced admin controls, multi-user management, and library organization features beyond what a consumer app provides.
• Docker-compose single-file deployment matters to you.

Skip it (stay on Google Photos) if:

• Your Google account storage tier is cheap enough and you’re at peace with the privacy trade-off.
• You rely heavily on Google Lens, Google’s AI editing, or deep Android integration.
• The idea of “recovery code or your photos are gone” creates too much anxiety.

Skip it (use iCloud with Advanced Data Protection) if:

• You’re entirely in the Apple ecosystem — iPhone, iPad, Mac only — and never need Linux or Android access.
• You want E2E encryption without the operational overhead of a separate app and subscription.

Skip it (Nextcloud) if:

• You need a general-purpose file storage system where photos are one module among many.

---

Alternatives Worth Considering

• Immich — most popular self-hosted photo manager; no E2E encryption but far easier deployment, richer admin UI, active development. Choose Immich if encryption isn’t a hard requirement.
• Google Photos — the incumbent; best AI, best UX, worst privacy. The product Ente is explicitly replacing for privacy-focused users.
• iCloud Photos with Advanced Data Protection — Apple’s E2E encrypted option; excellent for Apple-only households, nonexistent outside that ecosystem.
• Nextcloud Photos — general-purpose Nextcloud with a photos module; serviceable but not the core focus. Better if you need file sync + photos in one system.
• Photoprism — self-hosted photo manager with AI features, no encryption; aimed at power users who want ML-based organization on their own hardware.
• Stingle Photos — another E2E encrypted photo app; smaller community, fewer platforms, less development velocity than Ente.

For the non-technical founder or privacy-conscious family the realistic shortlist is Ente vs. Immich. If you need encryption and zero-knowledge assurance, Ente. If you just want Google Photos-style convenience off Google’s servers, Immich.

---

Bottom Line

Ente is the best answer to a specific question: “I want Google Photos-quality photo storage, but I need the encryption to be real and independently verified, not a promise.” For that use case, nothing else in the open-source space is as complete — cross-platform clients, on-device face recognition, family plans, and a cryptographic audit that an independent expert will put their name on. The trade-offs are real: self-hosting is non-trivial, the company is small, the ecosystem is closed by design, and the E2E model means losing your recovery code is catastrophic. But for the people who need what Ente offers, those trade-offs are the point, not the problem. If you’re tired of your photos being the product, this is where you go.

If the self-hosting setup is the blocker, that’s exactly what unsubbed.co’s parent studio upready.dev deploys for clients. One-time setup fee, you own the infrastructure.

---

Sources

1. Ente.io Official Website — homepage, feature descriptions, testimonials. https://ente.io
2. Ente.io User Testimonials — collected on homepage from App Store, Google Play, and direct users. https://ente.io
3. Ente GitHub Repository (monorepo) — GPL-3.0 license, open source server and clients. https://github.com/ente-io/ente
4. Ente Pricing Page — current tier pricing (consult directly; not available in source data for this review). https://ente.io/pricing
5. Ente Blog — Open Sourcing Our Server — announcement of server open-source release and monorepo consolidation. https://ente.io/blog/open-sourcing-our-server/

Note: No usable independent third-party review articles were available in the source data provided for this review. All claims are sourced from official Ente materials and verified user testimonials on the official website. Readers should seek current independent reviews before making a hosting decision.