Haven Hosting
Publish and manage a personal website or blog while retaining ownership of your content.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
Haven’s official links and original website
Haven Website
More
Tech
- Docker image
- ghcr.io/havenweb/haven:latest
- Default port
- 3000
- Database
- postgres
How Haven works
Haven is a private blog built around owner-controlled access. The site owner writes posts in a browser, adds images or other supported media, and creates accounts for the people who are allowed to read. There is no public sign-up path and the project is intended for sharing with known friends or relatives rather than attracting anonymous traffic.
Every authorised reader receives access to the same private publication. Haven also produces private RSS links and includes a feed reader for the owner, so posts from other websites or Havens can be followed alongside the site’s own updates. This creates a small, deliberate publishing circle without relying on a public social network.
Key Haven features
The web interface covers post writing, editing, user administration, and visual customisation. Markdown with live preview keeps writing straightforward, while custom CSS and fonts provide room to shape the appearance. Media can accompany posts, and images are reduced for lighter page delivery.
Privacy is structural rather than an optional page setting. The owner decides who receives an account, readers authenticate before seeing posts, and the application does not offer a public version of the blog. That makes Haven suitable for personal updates that should stay within a trusted circle.
Who uses Haven
Families use Haven for private news, photographs, travel updates, and longer reflections that do not belong on a public profile. Close communities can maintain a shared reading circle, while individuals may keep a personal journal that selected people can follow from the web or through a private feed.
The application is a poor match for a public company blog, search-driven publication, or open membership community. Its defining choice is restricted readership, so projects that need broad discovery, public comments, or anonymous subscriptions should use a different publishing system.
Self-hosting Haven: requirements and cost
Haven resource use is shaped by the number of invited readers, the volume of posts and media, feed-refresh activity, and retained uploads. The catalogue stack includes PostgreSQL for accounts, access rules, posts, and related records. That database container is provisioned with Haven but remains unmanaged by AvaHost.
Haven carries no separate software charge, and AvaHost maps the complete stack to Plan 2 at €5 after applying the database-memory adjustment. For Haven, AvaHost supplies one-click setup, a custom domain, automated HTTPS, automatic application updates, and scheduled backups. A larger plan becomes relevant when media storage or concurrent readership grows beyond the starting configuration.
F.A.Q
Haven starts at €5 on Plan 2 after allowing for both the web application and its PostgreSQL container. The price covers the hosted stack, custom-domain support, automated HTTPS, automatic application updates, and scheduled backups. Post volume, uploaded media, feed activity, and the number of active readers are the main reasons to consider a larger plan.
AvaHost provisions PostgreSQL beside Haven and connects the application to it during deployment. User accounts, access controls, posts, and related records depend on that service. The database container is included but unmanaged, so the persistent application files and PostgreSQL data should be treated as one installation when reviewing changes or recovery.
A custom domain can be attached to the Haven site, and automated HTTPS is applied to the public address used by authorised readers. After DNS points to the hosted application, the owner should test sign-in, media loading, private feed links, and any saved bookmarks that still reference the earlier platform hostname.
Haven is designed for private sharing and does not offer a public publishing mode. The owner creates accounts for each reader, and access is limited to those users. A project that needs anonymous visitors, open registration, search discovery, or a public comment community should choose a publishing application built for those requirements.