Write, publish, grow.
Lavvus is a simple blogging and newsletter platform for independent writers: a distraction-free editor, a built-in newsletter, a link-in-bio page, and an AI-ready API. Built and hosted in Europe, privacy-first. Inside Deuces Media it is also the publishing layer behind every brand blog.
We shipped without a countdown timer or a launch-day thread. Here is what actually happened, and why I would do it the same way again.
The short version: write for the ten people who reply, not the thousand who scroll past.
Automate the whole thing.
Publish over a clean REST API, and let incoming webhooks from Zapier, Make or n8n post for you. An agent can draft and ship a piece without you touching the editor.
Outgoing webhooks fire on every publish, so a new post can fan out to your own site, your socials and anywhere else you distribute, all from one source.
A distraction-free editor
Write in Markdown and publish instantly. No clutter, no fighting the tool, just the words.
Newsletter built in
Every post can go straight to your subscribers as email, so you grow an audience you actually own.
AI-ready, automatable API
Publish over a clean REST API with incoming and outgoing webhooks, so tools and agents can post for you.
These are the highlights. See everything Lavvus does at lavvus.com
Your blog, newsletter and audience in one place.
Lavvus gives independent writers a distraction-free Markdown editor, a built-in newsletter, and a personal link-in-bio page, without the sprawl of WordPress or the lock-in of a walled garden. Publish once and the same post can land in your subscribers' inboxes.
It is built and hosted in Europe, privacy-first, and fully automatable through an AI-ready API with incoming and outgoing webhooks. Inside Deuces Media it is also the publishing layer behind every brand blog.
Latest from Lavvus. Written on the Deuces blog, tagged Lavvus.
All Lavvus postsGrowing in Public: One API, Every Kind of Blog
Some blogs publish themselves on a schedule. Some publish the instant a product changes. Some wait for a person to sit down and write. They share almost nothing about how they work, and they all run on the same platform. Here is why we built Lavvus to hold no opinion about your cadence, your tooling, or your voice, and what running very different blogs of our own taught us about staying out of the way.
Read on LavvusGrowing in Public: Why Your Lavvus Blog Has an API
Most platforms treat this backwards. The dashboard is the product, and an API, if it exists at all, is a bolted-on afterthought with half the features missing. We built Lavvus the other way around. The post is the API. The dashboard is just a friendly face on top of it. Anything you can do by clicking, you can do with a request: POST a draft, PATCH a summary, attach tags, flush the cache. The clicking is optional.
Read on LavvusGrowing in Public: Canonical URLs, AI Readers, and the Distribution Layer
Lavvus is growing on both sides at once. The writers are different: more of them are building websites with AI sitting beside them and want a backend they can program against. The readers are different too: AI assistants are showing up in the access logs and citing posts the way Google used to. The platform is becoming a distribution layer. New canonical-URL control points search engines and AI crawlers at your domain. Webhooks tightened. Mailing wired in.
Read on Lavvus