Why Juttu

The problem with existing comment systems

Most comment systems (Disqus and similar tools) share the same structural problems:

• Heavyweight: they bring a bundle of JavaScript, ads, or tracking pixels into your page.
• Privacy-invasive: user data is collected and monetized by a third-party platform you don’t control.
• Platform-controlled: if the vendor shuts down, changes pricing, or alters their terms, your comment history goes with it.

They also create a new social silo. Readers have to create yet another account on yet another platform just to leave a comment.

The Bluesky angle

Bluesky is built on the AT Protocol — an open, decentralized standard for social data. Every post on Bluesky is a public record owned by its author, stored in their personal data repository, and portable across services.

Juttu uses this directly. When you embed Juttu on an article, you link that article to a Bluesky post. The reply thread of that post becomes the comment section. Comments are real Bluesky posts — they exist on the open network, they belong to their authors, and they are readable by anyone with a Bluesky client.

No new accounts

Visitors authenticate with their existing Bluesky identity. There is no Juttu account, no separate password, and no profile to maintain. Login happens via AT Protocol OAuth, and the session is stored only in the user’s browser.

Built on open standards

Juttu uses standard.site lexicons to connect articles to Bluesky threads. site.standard.document is an AT Protocol standard for long-form publishing being adopted across Bluesky-native blogging platforms.

Using Juttu is the easiest way to make your blog compliant with the standard.site ecosystem. By simply adding the Juttu script, your blog posts become first-class citizens in the AT Protocol network, discoverable and interoperable with other platforms that implement these open standards.

This means:

• No proprietary lock-in. Article–post links are stored in a public, interoperable format — not in a Juttu-specific database.
• Interoperability. Your content works with any platform or tool that understands the standard.site lexicons.
• Works with compatible platforms. If your blogging platform already emits site.standard.document records, Juttu just works with no extra setup.
• Owned by you. The link between your article and its Bluesky thread is a record in your AT Protocol repository, not ours.

Open source

Juttu is licensed under AGPL-3.0. The source code is public, auditable, and forkable. You can run your own instance on your own infrastructure with full control over the data.

What Juttu stores

Juttu stores nothing beyond an OAuth session token in the user’s browser (IndexedDB). There is no database of users, no comment archive, and no analytics. The comments themselves live on Bluesky — Juttu just displays them.