memories
Memories is a self-hosted photo and video management suite built as a Nextcloud app, featuring AI-powered tagging, timeline organization, albums, sharing, and video transcoding. It is designed for users who want to manage large photo libraries privately on their own infrastructure.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | pulsejet/memories |
| Owner | pulsejet |
| Primary language | Vue |
| License | AGPL-3.0 — OSI-approved |
| Stars | 3.8k |
| Forks | 158 |
| Open issues | 591 |
| Latest release | v8.1.0 (2026-07-03) |
| Last updated | 2026-07-08 |
| Source | https://github.com/pulsejet/memories |
What memories is
Vue-based frontend running on Nextcloud (PHP backend) with a Go video transcoder (go-vod), supporting Exif parsing, reverse geocoding, HLS video streaming, and bulk metadata editing. Tested to handle over a million photos with indexed metadata for performance.
Get the memories source
Clone the repository and explore it locally.
git clone https://github.com/pulsejet/memories.gitcd memories# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires a working Nextcloud instance (v23+, version not explicitly stated but app is Nextcloud Store listed). Ensure adequate PHP, Node.js, and Composer tooling for deployment.
- Metadata indexing via `php occ memories:index` is mandatory for existing libraries; plan for downtime on very large photo sets (1M+ photos tested, duration unknown).
- Video transcoding requires go-vod binary deployment and sufficient CPU/storage for HLS output. Evaluate transcoding resource needs in advance.
- AI tagging depends on optional Nextcloud recognize or facerecognition apps. Plan separate installation and configuration if facial/object tagging is required.
- Development environment uses devcontainer and Composer; ensure build toolchain (Make, Node 18+) is available for any customization or patching.
When to avoid it — and what to weigh
- Nextcloud is not part of your infrastructure — Memories is a Nextcloud app only; it cannot run standalone. If you lack a Nextcloud instance or cannot integrate with one, this tool is not viable.
- You require proprietary licensing for commercial use without copyleft obligations — AGPL-3.0 requires source code disclosure and share-alike licensing in network services. Requires legal review for your use case.
- You need production support with SLAs — This is a community-driven open-source project with no commercial support entity. Financial sponsorship exists but does not include support contracts.
- Your users require mobile-first or offline-first workflows — Android is in early access; iOS support is via generic Nextcloud app only. Web app is mobile-friendly but still browser-dependent.
License & commercial use
Licensed under AGPLv3. Subpackages (go-vod, android) have their own licenses; check their directories. AGPLv3 requires source disclosure if software is used over a network.
Commercial use is legally possible under AGPLv3, but requires careful legal review. If you modify or deploy the app as a network service, you must provide users with source code and allow derivative works. Consult counsel before using in commercial products or SaaS offerings.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
AGPL-3.0 licensed code should be audited before deployment. No explicit security policy or vulnerability disclosure statement found in README. Shares Nextcloud's authentication and permission model; inherits Nextcloud's security posture. Video transcoding (go-vod) is separate; review its security practices independently. External sharing features create public URL attack surface; ensure proper access controls and rate limiting at Nextcloud level.
Alternatives to consider
Nextcloud Photos (native)
Simpler, built-in Nextcloud app with lighter footprint; lacks AI tagging, video transcoding, map view, and advanced metadata editing. Memories explicitly supports migration from it.
Immich
Standalone self-hosted photo management with AI tagging, mobile apps (native iOS/Android), and no Nextcloud dependency. Different license (AGPL-3.0 also, but independent codebase) and architecture.
Photoprism
Self-hosted photo management with AI tagging, map view, and web UI. Does not require Nextcloud; offers standalone deployment. Different license (AGPL-3.0) and smaller community than Memories.
Build on memories with DEV.co software developers
If self-hosted photo management on Nextcloud aligns with your needs, assess AGPL-3.0 implications, transcoding infrastructure, and your Nextcloud deployment readiness. Devco can guide architecture and integration planning.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
memories FAQ
Can I use Memories without Nextcloud?
Is there commercial support available?
What video formats and codecs does transcoding support?
Can I share photos with people outside my Nextcloud instance?
Custom software development services
Adopting memories is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source devops software in production.
Evaluate Memories for Your Photo Archive?
If self-hosted photo management on Nextcloud aligns with your needs, assess AGPL-3.0 implications, transcoding infrastructure, and your Nextcloud deployment readiness. Devco can guide architecture and integration planning.