this post was submitted on 11 Nov 2025
133 points (96.5% liked)

Selfhosted

52948 readers
438 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

Hello everyone!

TL;DR:
Journiv is a a beautiful, self-hosted, privacy-first journaling app with mood tracking, daily prompts, and meaningful insights. The mission is simple: your memories should always stay yours. Own them, don’t rent them.

Journiv 0.1.0-beta.4 is now live on GitHub and fully Docker-hostable.
Start owning your thoughts and memories forever and keep them completely private.

The Story Behind Journiv

I got into self-hosting last year and while exploring options journaling solution, I realized there wasn’t a truly modern, self-hosted equivalent to Day One or Apple Journal. Most alternatives were either general note apps or old abandoned projects.

I wanted something focused on journaling with:

  • “On This Day” memories
  • Prompt-based journaling
  • A clean, minimal, distraction-free writing experience

So… I built my own: Journiv, a beautiful (at least I am trying to make it so), self-hosted, privacy-first journaling app with mood tracking, daily prompts, and meaningful insights.

Get Involved

Give Journiv a try, share your feedback and report issues. It means a lot at this stage.

you are viewing a single comment's thread
view the rest of the comments
[–] msokiovt@lemmy.today 11 points 3 days ago* (last edited 3 days ago) (3 children)

It looks like this is open-source, but not Free Software, since you're using PolyForm Noncommercial 1.0.0 as your license. Did you consider other licenses like any of the GPL licenses or BSD-2/3 Clause license, Apache-2.0 or any of the others that fit the Free Software classification?

[–] rockstar1215@lemmy.world 14 points 3 days ago* (last edited 3 days ago) (2 children)

Journiv is source-available but not “Free Software” under the FSF/OSI definition. I chose the PolyForm Noncommercial 1.0.0 license intentionally to keep the code open for personal and educational use which allow hosting for non-commercial while preventing "commercial" redistribution or hosting for commercial gain without permission.

My motivation behind Journiv is to give a solution to self hosted people like me and other a journal first experience on par with any major cloud offering so that they don't have to mold their usage to a notes app and be unsatisfied and frustrated like me. This license enables everyone in the self hosted community to use Journiv.

I did consider permissive and copyleft licenses (Apache, GPL, BSD, etc.), but sustainability is a major concern for this project. I have already spent hundreds of hours on this over last couple of months and there is so much more to build (take a look at the issues page of github repo). I want to keep development open and transparent while ensuring that commercial entities can’t simply repackage and profit from it.

[–] msokiovt@lemmy.today 1 points 2 days ago (1 children)

I see where you're coming from, and can understand why you decided to prevent commercial repackaging and tivoization. Source-available sounds like it's proprietary, which I assume it's not.

[–] rockstar1215@lemmy.world 3 points 2 days ago

Thanks! My main focus right now is simply building the product, the license doesn’t matter much if the product itself isn’t good yet. It’s always easier to move to a less restrictive license later than to go the other way, so this is the approach I’m starting with.