Piruetas: Self-hosted privacy-focused diary and journaling app

What it does

Piruetas is a self-hosted journaling application with a one-page-per-day interface. It includes rich text editing, drag-and-drop image uploads, auto-save functionality, and a mobile-friendly design. Users can generate public share links to distribute individual entries and export all entries for data portability. The app supports both single-user and multi-user setups deployed via Docker Compose.

Who it is for

The app targets users who want a simple diary without complexity or feature bloat. It appeals to technically inclined people comfortable self-hosting software on their own infrastructure. Privacy-conscious individuals seeking to avoid cloud services and telemetry will find the local-first approach valuable. Those already running their own servers have minimal friction to adoption.

Pricing

Free forever. The software is free and open source. The creator accepts optional donations.

How it stands out

Piruetas emphasizes privacy and simplicity in a crowded journaling space. By requiring self-hosting, it eliminates the trust requirement inherent in cloud diary services. The one-page-per-day structure provides structure without complexity. There is no telemetry collection. The codebase is available for review and modification. The Docker Compose setup makes deployment straightforward for the target audience, though steeper than point-and-click SaaS alternatives. The focus on minimalism—avoiding the feature-heavy design of mainstream competitors—appeals to users who find existing options overwhelming.

What a founder should check

A rival builder should verify retention rates for self-hosted journaling apps and whether user churn stems from technical friction or lack of engagement. The switching cost appears low since users can export their data and re-host elsewhere, so defensibility depends entirely on ongoing simplicity and reliability rather than lock-in. Pricing power deserves scrutiny: the creator has chosen a donation model rather than paid tiers, so a potential competitor should assess whether users would accept paid features or subscription pricing for convenience features like cloud backup, advanced analytics, or design customization, or whether the self-hosted, privacy-first audience inherently resists monetization.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.