Hyvor Post is a privacy-first, open-source newsletter platform for publishers, organisations and developers who want to send newsletters to subscribers without click or open tracking, built in PHP and based on the Hyvor Relay self-hosted email API.
What it is
Hyvor Post lives in the Hyvor ecosystem of self-hosted communication tools. It is an open-source newsletter platform whose backend is a PHP and Symfony API, whose frontend, embed and archive website are built with SvelteKit and the Hyvor Design System, and whose data sits in a PGSQL database. It is built on top of Hyvor Relay, an open-source, self-hosted email API for developers, which supplies the sending layer the newsletter application sits on. The repository is organised into /backend for the Symfony API, /frontend for the SvelteKit application, /embed for the signup form embed code, and /archive for the newsletter archive website.
The concrete problem it solves is surveillance in email marketing. Conventional newsletter platforms record who opens a message and who clicks which link, then build subscriber profiles from that behaviour. Hyvor Post deliberately does not do this: its first listed feature is "No Tracking" — no click tracking and no open tracking — so subscribers remain readers rather than data points. The README states the intent as "For People, Not Funnels". It replaces the tracking-centric newsletter platform with a list-and-send tool that still offers an editor, subscriber management, signup forms and an archive, but treats recipient behaviour as private.
Key capabilities
- No click or open tracking anywhere in the platform, so subscriber reading behaviour is never recorded.
- Rich text editor with markdown support for composing newsletters.
- Multi-tenancy with scoped access, so one installation can serve several tenants.
- Multiple newsletters per user, with list management for importing and managing subscriber lists.
- Customizable email templates, an embeddable signup form for a website, and an automatically generated archive website for published newsletters.
- Console API for automating newsletter management programmatically.
- Architecture split across a PHP and Symfony API backend, a SvelteKit frontend with the Hyvor Design System, and PGSQL as the database.
Who uses it and how
- Publishers who want to send regular newsletters without collecting open and click data on their readers.
- Organisations running several brands or publications from one deployment, using multi-tenancy with scoped access to separate them.
- Website owners who embed the signup form to collect subscribers and let the archive website publish past issues automatically.
- Developers who drive newsletter management from scripts and services through the console API.
- Early adopters willing to work with a small, young project: the repository shows 32 stars, 3 forks and 37 open issues, with the most recent push in September 2026.
Getting started
The README points to hyvor/dev for the HYVOR development environment, where ./run post starts Hyvor Post at https://post.hyvor.localhost. There is no supported self-hosting path yet, so the documented route is the development environment rather than a production install.
How it compares
The facts name no comparable newsletter products, so Hyvor Post stands alone in this registry on that axis. Its only named relative is Hyvor Relay, the open-source self-hosted email API it is built on, which is a sending component rather than a competing newsletter platform.
When to use it — and when not to
Self-hosting is not yet ready: the README lists setting up OIDC and writing self-hosting documentation as pending tasks, so anyone self-hosting today must operate the Symfony backend, PGSQL database and email sending themselves without official guidance. The project is small and young, with 37 open issues against 32 stars, and the enterprise licence option mentioned in the README is commented out rather than offered. Teams that need a production newsletter service or a commercial licence right now should not pick it yet.
