As developers, many of us keep journals. Whether personal logs, learning notes, or scattered ideas stored across Notion, Apple Notes, Evernote, Obsidian, or a pile of markdown files collecting dust in a repo somewhere.
But journaling has a problem.
Most modern tools come with a tradeoff:
- Great UX… but your data lives on someone else’s servers, or
- True ownership… but the tooling feels like 1990, or
- Self-hosted options… but they lack polish or long-term sustainability
I felt that tension for years. I wanted something beautiful, private, long-lasting.
So I built Journiv, a self-hosted, privacy-first journaling app designed for people who want modern features without giving up ownership of their memories.
This is the story of why it exists, how it’s built.
Why I Started Building a Journaling App
A few years ago, I was scrolling through hundreds of photos of my toddlers, thinking about all the tiny moments I wanted to remember: the first clumsy dance, how they mangle new words, the small adventures that make up childhood.
I started looking for a journaling app to capture these stories, something to preserve not just the photos, but the context, the emotions, the narrative that makes memories complete.
Every journal solution I found had the same problem: third-party servers, vendor lock-in, inconvenient and incomplete export formats. My children's memories, my personal reflections, my family's stories - all locked away, profiled, and out of my control.
As a developer who loves self-hosts everything, this felt wrong.
But when I looked for self-hosted alternatives, I found something surprising: there weren't any. Not real ones.
Privacy Is Not a Feature — It's the Foundation
When your journal is about your inner thoughts, reflections, mental health, and personal relationships, privacy is not optional.
This became Journiv’s core value:
Your data stays with you. Full stop.
So Journiv is built with:
- Self-hosting as the primary mode
- No tracking, analytics, or telemetry
- Local encryption support (in progress)
- Standard export formats
- A long-term migration philosophy (“Your data should live longer than the app”)
In Journiv, privacy isn’t a checkbox. It’s the entire architecture. Read more about story behind Journiv here.
🏗️ The Architecture
Backend
- FastAPI + SQLModel
- SQLite or PostgreSQL
- Vector DB (optional upcoming features: semantic search, embeddings)
- Media storage on local disk
- OIDC support (Keycloak, Authentik, Authelia)
Frontend
- Flutter Web app
- Mobile apps coming soon
Deployment
- Docker-first
- One command to self-host
- Works on Synology, Unraid, Proxmox, Raspberry Pi, and plain Docker
Journiv is built so anyone, technical or not, can host it at home.
Immich Integration
One of the most powerful things you can do in a journal is bring your photos into it. Not just as attachments, but as memories.
Here’s what Journiv + Immich will unlock:
- Browse your Immich library while writing an entry
- Insert photos or videos directly without re-uploading
- Keep full ownership (media stays in Immich, not duplicated)
This integration will make Journiv feel “alive” in a way traditional markdown-based journals never achieve.
A journal without media is a diary.
A journal with media becomes a story.
If any of that interests you… well, Journiv might be for you. Read more about Immich integration here.
Final Thoughts: Why Open, Private Tools Matter
We spend so much time building software for others that we rarely stop to build something that protects our own lives, memories, and emotions.
Journiv is my attempt for that.
Not by replacing existing tools,
but by offering a modern journaling experience without sacrificing privacy or ownership.
If you’re interested, curious, or want to contribute, I’d love to hear from you.
GitHub: https://github.com/journiv/journiv-app
Docs: https://journiv.com/docs
Website: https://journiv.com
Thanks for reading — and if you journal, I hope Journiv helps you keep your memories safe for decades to come.
Top comments (0)