I build open source tools for the AT Protocol ecosystem — libraries,
CLIs, and self-hosted infrastructure for a decentralised social web.

What I've built:

• malachite — import your Last.fm and Spotify history to the AT
  Protocol network as fm.teal.alpha.feed.play records, with full
  OAuth support, smart rate limiting, and a browser-based frontend at
  malachite.croft.click

• jasper — import your Instagram photos (eventually videos) to the AT Protocol, with full
  OAuth support and a browser-based frontend at
  jasper.croft.click

• @ewanc26/atproto — an AT Protocol service layer covering
  identity resolution, profile fetching, Standard.site documents,
  Bluesky posts, and music/mood status, with a built-in cache

• bismuth — a CLI and library for converting pub.leaflet
  ATProto documents to Markdown

• @ewanc26/supporters — webhook-backed SvelteKit components for
  Ko-fi and GitHub Sponsors, storing events as ATProto PDS records

• Custom lexicons — uk.ewancroft.* for structured data on the
  network, including supporter events and site metadata

• pds-backup — automated, resumable PDS backups over SSH with
  checksum-based change detection

All of the above (and more) lives in the
@ewanc26/pkgs monorepo —
TypeScript, Rust, and Python, with full git history preserved across
migrations.

Why AT Protocol?

It's genuinely nice to use — and I find it meaningful to build tools
that help people take ownership of their own data. That's really it.

Support my work:

Sponsorships fund open source AT Protocol development, documentation,
and the server infrastructure behind it. I'm also open to commissions
for AT Protocol integrations, custom lexicons, and SvelteKit
development — details on my Ko-fi.