Building in public is supposed to be about showing the work. Today I want to show what the work is becoming.

Lavvus is growing. Not loudly, but steadily. Two shifts are showing up at once.

The writers are different. More of the people starting blogs on Lavvus now are building their websites with AI sitting beside them. They are not opening a WYSIWYG and typing into a box; they are working in Cursor or Claude or Lovable, scaffolding their site, and asking what the API looks like in the same breath. They want a backend their tools can read and write to. They want the blog to be a thing you can program against, not a thing you have to click through.

The readers are different too. A lot of the blogs going live on Lavvus are not just being read by humans anymore. AI assistants are showing up in the access logs the way Google used to. They are quoting posts, citing them, sending readers back to them. The web is being read by machines now, and the machines have taste. They want clean structure, stable URLs, canonical signals, and content that does not change underneath them.

That is the shape Lavvus is starting to fit into, and it is changing what I am building.

A platform for writing is becoming a platform for distribution

The original pitch for Lavvus was simple: a place to write without the WordPress weight. That is still true. What has changed is that more and more of the people writing on Lavvus do not just publish here, they publish from here. They run their own domains, their own typography, their own brand frames, and they treat Lavvus as the place where the post is authored, stored, and authorised to spread.

So Lavvus is quietly becoming the distribution layer. The API is the wire. The blog you read at lavv.us is one rendering, but it is not the only one. Other renderings live on other domains. The platform's job, increasingly, is to make every one of those copies consistent, fresh, and discoverable.

What we shipped to make that work

A small but pointed example: explicit canonical-URL control on each post. If this blog is also published on your own domain, you can now point search engines and AI crawlers at your domain as the primary source. Two clicks in the editor. The right <link rel="canonical"> and og:url show up on the lavv.us rendering. Duplicate-content penalties disappear. Your domain gets the credit. Lavvus does not compete with you for the SEO of your own writing.

This is the kind of feature you do not need until you really need it, and the people who need it are exactly the people I want on the platform. Writers with their own audiences, their own domains, their own ambitions. Lavvus is the easy part underneath.

We have also tightened up the parts distribution depends on:

• Webhooks fire reliably enough that downstream caches can trust them.
• Mailing is wired into the same posting flow, so the same post can land in your readers' inboxes the moment it goes live.
• The API has settled into something predictable enough for AI agents to read from it without surprise.

The shape of the months ahead

More distribution. More canonical signals. More ways to fan a single post out to where the audience already is, without ever asking that audience to switch sites or learn a new domain.

If you are writing on Lavvus today and want to plug in a custom domain or set up the canonical, the option is in the editor sidebar. If you are reading this on lavv.us and curious, start a blog. The rest follows.