Skip to content
Frontier Leaf FL markFLFrontierLeaf

A field journal of new AI developments.

Model updates

IndieWeb creator launches IndieKey for domain auth after AI-assisted rewrite

An IndieWeb toolmaker has released a new authorization server, separating it from older services after using AI to modernise legacy code.

Depth
2 outlets · newest source 292h ago
IndieWeb creator launches IndieKey for domain auth after AI-assisted rewrite

Key points

  • The creator launched IndieKey as a distinct authorization server for domain-based sign-ins.
  • Legacy Ruby codebases for IndieAuth and webmention.io required modernisation due to age and security risks.
  • Claude Code was instrumental in enabling the launch of the new IndieKey service.

An IndieWeb project creator has launched IndieKey, a new authorization server that issues tokens for Micropub apps. This release follows a period of development using Claude Code to modernise long-standing, insecure legacy systems.

The evidence

The creator noted that Claude Code appeared in the commit history of several IndieWeb projects. Observers on Lobsters AI tag noticed this activity, prompting the creator to explain the rebuild process. The original codebases for webmention.io and IndieAuth.com were launched approximately fifteen years ago.

These older services relied on ancient versions of Ruby and long-abandoned object-relational mappers. The creator described the legacy code as a security risk that would have necessitated shutting down the services if not rewritten. The decision to rebuild was driven by the need to maintain functionality rather than a desire to change core principles.

The decision

IndieAuth.com originally served two distinct functions: an authorization server for users and a service for developers to add sign-in features. This dual purpose created confusion, leading to the creation of IndieLogin in 2018. IndieLogin allows developers to integrate web sign-in without implementing the IndieAuth specification or RelMeAuth themselves.

However, the authorization server component remained coupled with the developer-facing service for years. The creator had previously intended to split these functions but lacked the resources or method to do so effectively. The development of a comfortable workflow with Claude Code finally enabled the separation and launch of IndieKey.

The takeaway

The IndieWeb principles emphasise owning one's domain, data, and web presence rather than relying on centralized silos. These principles do not dictate the tools used to build services or how the underlying code is created. The focus remains on user control and data portability, independent of the development methodology employed.

The rewrite was not about changing the hosting model or forcing users to self-host. Instead, it addressed the technical debt inherent in fifteen-year-old Ruby applications. The creator maintained that the core identity and data ownership goals remained unchanged throughout the modernisation process.

Building on this

Developers can now utilize IndieKey as a dedicated authorization server for their Micropub applications. This service issues tokens that allow users to sign in using their own domain names. The separation from the developer-facing tools clarifies the architecture for those building on IndieWeb standards.

The availability of IndieKey provides a stable, modern backend for domain-based authentication. It resolves the historical confusion where a single service handled both user authorization and developer integration. Builders of Micropub clients can link to IndieKey as their authorization endpoint without managing the legacy codebase complexities.

Why it matters

  • Legacy system modernisation often stalls due to resource constraints; AI assistance can unblock critical infrastructure updates.
  • Separating user-facing and developer-facing services can improve clarity and security in long-running projects.
  • The use of AI in commit histories is becoming visible and trackable within open-source communities.
  • Maintaining decade-old codebases without modernisation poses significant security risks that may force service shutdowns.

Updated

Story timeline

  1. 08 Nov 2026 Rebuilding some Indieweb Tools with Claude
  2. 10 Nov 2026 Anthropic News page updated: 284

Did this article give you the evidence you needed?

No vote saved on this device.
Your choice stays on this device. No public tally.

Questions readers ask

What is IndieKey and how does it differ from IndieLogin?

IndieKey is the authorization server that issues tokens for Micropub apps, while IndieLogin helps developers add sign-in features without implementing the IndieAuth spec.

Why was the rewrite of IndieAuth.com necessary?

The original code used ancient Ruby versions and abandoned ORMs, creating security risks that would have required shutting down the service.

Did the creator use AI to rewrite webmention.io?

The source states Claude Code was used to enable the launch of IndieKey, but does not explicitly confirm its use for rewriting webmention.io.

Reading receipt

  • The creator launched IndieKey as a distinct authorization server for domain-based sign-ins.
  • Legacy Ruby codebases for IndieAuth and webmention.io required modernisation due to age and security risks.
  • Claude Code was instrumental in enabling the launch of the new IndieKey service.
Time spent: 0:00 · Depth: Full

Sources

  1. Lobsters AI tag

Related stories

Background reading