Fedify: ActivityPub server framework

:fedify: [Fedify](https://fedify.dev/ ) is a TypeScript library for building federated server apps powered by [ActivityPub](https://www.w3.org/TR/activitypub/ ) and other standards, so-called [fediverse](https://en.wikipedia.org/wiki/Fediverse ). It aims to eliminate the complexity and redundant boilerplate code when building a federated server app, so that you can focus on your business logic and user experience.

Website: https://fedify.dev/

GitHub: https://github.com/fedify-dev/fedify

JSR: https://jsr.io/@fedify/fedify

npm: https://www.npmjs.com/package/@fedify/fedify

Last Notes

2026-06-29 20:48:07 UTC

[OSSCA] 2026 has started, and Fedify is joining for the second year. 24 mentees will work on Fedify, Hollo, BotKit, DrFed, and Feder over the next four months, with some of that work likely to continue after the program ends.
OSSCA, the Open Source Software Contribution Academy, is a South Korean mentorship program that connects developers with active open source projects. @npub146w…6lpm and @npub1dzk…tewa, both Fedify co-maintainers who first came to the project through OSSCA 2025, are mentoring this year's cohort. Welcome, everyone.
[OSSCA]: https://oss.kr/pages/3

2026-06-26 09:09:10 UTC

### Two new maintainers join Fedify: Chanhaeng Lee and Jiwon Kwon
Chanhaeng Lee (@npub146w…6lpm) and Jiwon Kwon (@npub1dzk…tewa) are now co-maintainers of Fedify. They have already been doing maintainer-shaped work for much of the past year, so this is mostly making the repository match reality.
Chanhaeng has done a lot of the package-boundary work in Fedify. The most visible piece was splitting the old `@fedify/fedify/x/*` modules into standalone packages: `@fedify/cfworkers`, `@fedify/denokv`, `@fedify/hono`, and `@fedify/sveltekit`. They then separated the Activity Vocabulary layer itself into `@fedify/vocab`, `@fedify/vocab-runtime`, and `@fedify/vocab-tools`, making it possible to build custom vocabulary extensions without touching the federation core. They built `@fedify/next` and `@fedify/nuxt` from scratch, contributed to `@fedify/solidstart`, and added Nuxt support to `fedify init`. `@fedify/sqlite` gained `SqliteMessageQueue`: a queue backend that only needs SQLite, handy for single-node deployments and local development. Chanhaeng also implemented the `fedify webfinger` CLI command, fediverse handle utilities (`parseFediverseHandle()`, `isFediverseHandle()`, `toAcctUrl()`), and the `@fedify/webfinger` and `@fedify/lint` packages. They are currently working on a custom background task API built around `defineTask()`.
Jiwon has spent much of the past year making the CLI and relay tooling more useful for real ActivityPub debugging. `fedify relay`, backed by `@fedify/relay`, spins up a local ephemeral ActivityPub relay server with Mastodon and LitePub support. They extended `fedify lookup` with multi-URL traversal and inline image rendering for compatible terminal emulators (Kitty, WezTerm, iTerm, and others), and added configuration file support so options can live in *~/.config/fedify/config.toml* or a project-local *.fedify.toml* rather than being passed on every invocation. They also fixed a race condition in `RedisMessageQueue`, corrected ActivityPub object handling for relative URLs, extended TypeScript types for [RFC 6570] URI Template expressions in dispatcher paths, and implemented the [FEP-5711] inverse collection properties, including `likesOf`, `repliesOf`, and `followersOf`.
Chanhaeng and Jiwon both came to Fedify through OSSCA 2025, Korea's Open Source Contribution Academy. I'm grateful that the program led to long-term maintainers, not just a few merged patches, and I'm looking forward to working with them in this new role.
[RFC 6570]: https://www.rfc-editor.org/info/rfc6570/
[FEP-5711]: https://w3id.org/fep/5711

2025-12-23 15:11:14 UTC

According to @npub1vag…mjkp's [*My 2026 Open Social Web Predictions*][1]:
> Fedify will power the federation layer for at least one mid-sized social platform (500K+ users) that adds ActivityPub support in 2026. The “build vs. buy” calculation for federation shifts decisively toward “just use Fedify.”
We're honored by this recognition and will keep working hard to make #ActivityPub adoption easier for everyone. Thank you, Tim!
#Fedify #fediverse #fedidev
[1]: https://www.timothychambers.net/2025/12/23/my-open-social-web-predictions.html

2025-10-02 15:10:47 UTC

We're excited to announce that #Fedify has been awarded a service agreement by the @npub1yng…nhrk! [The Sovereign Tech Fund is investing €192,000 in Fedify's development over 2025–2026 to strengthen the fediverse ecosystem.][1]
This investment will enable us to significantly expand Fedify's capabilities and make it easier for developers to build federated applications. The commissioned work focuses on improving developer experience, adding comprehensive debugging tools, and ensuring Fedify remains at the forefront of #ActivityPub innovation.
Here are the key milestones we'll be delivering:
- *Web framework integrations*: Official adapters for Next.js, Elysia, Fastify, and Koa, making it seamless to add federation to existing applications
- *ActivityPub debug & development tools*: Real-time debug dashboard with WebSocket monitoring, federation lifecycle hooks, and implementation checklist CLI to make federation interactions transparent and debuggable
- *Storage & infrastructure enhancements*: `SQLiteKvStore` for robust file-based storage across Node.js, Deno, and Bun, plus performance optimizations for production deployments
- *Comprehensive documentation & examples*: Specialized tutorials for building federated blogs, social networks, and content platforms, with complete working examples and migration guides
- *Observability & monitoring*: Full OpenTelemetry metrics, performance benchmarking tools, and federation health dashboards for production environments
- *Advanced features & standards*: [FEP-ef61] (Portable Objects) support and implementation of emerging [Fediverse Enhancement Proposals] to keep Fedify at the cutting edge
All developments will be open source and available for the entire #fediverse community to use, contribute to, and build upon.
<https://www.sovereign.tech/tech/fedify>
#opensource #SovereignTechFund #STF
[1]: https://www.sovereign.tech/tech/fedify
[FEP-ef61]: https://w3id.org/fep/ef61
[Fediverse Enhancement Proposals]: https://w3id.org/fep/

2025-06-25 10:39:03 UTC

We're pleased to share that [Encyclia has joined our success stories.][1]
@npub120s…0fq8 bridges academic research to the #fediverse by making #ORCID researcher profiles and publications discoverable through #ActivityPub—built with #Fedify for seamless interoperability across Mastodon and other fediverse platforms.
This demonstrates Fedify's versatility beyond traditional social networking, helping specialized domains connect to the federated web.
We're also grateful for #Encyclia's sponsorship support, which helps make Fedify's development possible.
Learn more about Encyclia at <https://encyclia.pub/>. 📚
#fedidev #openscience
[1]: https://fedify.dev/why#encyclia-bridging-academic-research-to-the-fediverse

2025-03-31 06:55:20 UTC

We're incredibly honored to announce that #Ghost (@npub1lxn…wutr) has [become a formal sponsor of Fedify through Open Collective](https://mastodon.xyz/@johnonolan/114255689709555336)!
This is a significant milestone for our project, and we're deeply grateful to @npub1d2v…0l89 and the entire Ghost team for their support and recognition of our work in the #ActivityPub ecosystem.
Ghost's social web integration built on #Fedify is a perfect example of how open standards can connect different publishing platforms in the fediverse. Their backing over the past months has been invaluable, and this formal sponsorship will help ensure Fedify remains sustainable as we continue to develop and improve the framework.
If you're building with ActivityPub or interested in federated applications, please consider joining Ghost in supporting open source development through our Open Collective:
https://opencollective.com/fedify
Every contribution, no matter the size, helps us maintain and enhance the tools that make the fediverse more accessible to developers. Thank you for being part of this journey with us! :fedify: ❤️ :ghost:
#note12vc…ntl5

2025-03-05 05:02:04 UTC

## Fedify is looking for new partnership opportunities!
### :fedify: What is Fedify?
#Fedify is an #ActivityPub-based federated server framework that helps developers easily integrate their applications with the #fediverse, a decentralized social network. It simplifies the complex implementation of the ActivityPub protocol, significantly reducing development time. Fedify is an open-source project available under the MIT license.
### 💼 Projects using Fedify
Various projects are already leveraging Fedify:
- **[Ghost](https://activitypub.ghost.org/)**: A professional publishing platform with millions of users, open source under MIT license, and a major sponsor and partner of Fedify.
- **[Hollo](https://docs.hollo.social/)**: A lightweight microblogging platform for individual users (open source, AGPL-3.0)
- **[Hackers' Pub](https://hackers.pub/)**: A fediverse blogging platform for software engineers (open source, AGPL-3.0)
- **[Encyclia](https://encyclia.pub/roadmap#progress)**: A bridge service that makes ORCID academic records available via ActivityPub
### 🚀 Value provided by Fedify
- **80% development time reduction**: Utilize a proven framework instead of complex ActivityPub implementation
- **Immediate fediverse compatibility**: Instant compatibility with various fediverse services including Mastodon, Misskey, Pleroma, Pixelfed, PeerTube, etc.
- **Expert technical support**: Direct support from ActivityPub and Federation protocol experts
- **Custom development**: Tailored feature development to meet your specific requirements
### 🤝 Potential collaboration models
- **Custom consulting and integration support**: Professional assistance for integrating Fedify into your platform
- **Custom feature development**: Development and implementation of specific features needed for your platform
- **Long-term technical partnership**: Long-term collaboration for continuous development and maintenance
### 🌟 Benefits of collaborating with Fedify
- **Technical advantage**: Save time and resources compared to in-house implementation
- **Brand image**: Enhance corporate image through support of the open-source ecosystem
- **Entry to decentralized social networks**: Easily participate in the fediverse ecosystem
- **Competitive edge**: Strengthen product competitiveness through social features
### 📩 Interested?
If you're considering implementing ActivityPub or wish to collaborate with the Fedify project, please get in touch:
- **Email**: <sponsor@fedify.dev>
- **Fediverse**: @npub1tlf…wz08
- **GitHub**: <https://github.com/fedify-dev/fedify>
We're excited to explore customized collaboration opportunities that align with your requirements and goals.

2025-02-25 05:07:05 UTC

We'd like to introduce the #Fedify project family—a set of related tools that make building #ActivityPub applications more accessible:
### [Fedify] :fedify:
[Fedify] (@npub1tlf…wz08) is a #TypeScript library for building federated server applications powered by ActivityPub and other #fediverse standards. It provides [type-safe objects for Activity Vocabulary][1], WebFinger client/server, HTTP Signatures, and more—eliminating boilerplate code so you can focus on your application logic.
[Fedify]: https://fedify.dev/
[1]: https://fedify.dev/manual/vocab
### [Hollo] :hollo:
[Hollo] (@npub1mz3…tpw7) is a single-user microblogging server powered by Fedify. While designed for individual users, it's fully federated through ActivityPub, allowing interaction with users across the fediverse. #Hollo implements Mastodon-compatible APIs, making it [compatible with most Mastodon clients][2] without needing its own web interface.
Hollo also serves as our testing ground for bleeding-edge Fedify features before they're officially released.
[Hollo]: https://docs.hollo.social/
[2]: https://docs.hollo.social/clients/
### [BotKit] :botkit:
[BotKit] (@npub1sql…0z0c) is our newest family member—a framework specifically designed for creating ActivityPub bots. Unlike traditional Mastodon bots, #BotKit creates standalone ActivityPub servers that aren't constrained by platform-specific limitations (like character counts).
BotKit's API is intentionally simple—you can create a complete bot in a single TypeScript file!
[BotKit]: https://botkit.fedify.dev/
---
All three projects are open source and hosted under the [@fedify-dev] GitHub organization. While they serve different purposes, they share common goals: making ActivityPub development more accessible and expanding the fediverse ecosystem.
If you're interested in trying any of these projects or contributing to their development, check out:
- Fedify: <https://fedify.dev/>
- Hollo: <https://docs.hollo.social/>
- BotKit: <https://botkit.fedify.dev/>
#fedidev
[@fedify-dev]: https://github.com/fedify-dev

2024-11-29 15:35:31 UTC

The version 1.3.0 of #Fedify, an #ActivityPub server framework, released! The key changes include:
- [Instrumented spans for OpenTelemetry] are added. In most cases, it's automatically enabled if your application configured [OpenTelemetry SDK].
- Since Fedify 1.3.0, you can configure different [`MessageQueue`]s for incoming and outgoing activities.
- [Fedify now allows you to manually route an `Activity` to the corresponding inbox listener.][1] It is useful for invoking an inbox listener for an `Activity` enclosed by another `Activity`.
- `Context.sendActivity()` and `InboxContext.forwardActivity()` methods now reject when they fail to enqueue the task.
- Thanks to @robin_maki@planet.moe, [@fedify/fedify/x/sveltekit] module is added for integrating with [SvelteKit] hook.
- Fedify now makes HTTP requests with the proper `User-Agent` header, e.g., `User-Agent: Fedify/1.3.0 (Deno/2.1.2)`.
For details, see the [full changelog] as well!
Fedify 1.3.0 is available at [JSR] and [npm].
[Instrumented spans for OpenTelemetry]: https://fedify.dev/manual/opentelemetry
[OpenTelemetry SDK]: https://opentelemetry.io/docs/languages/js/
[`MessageQueue`]: https://jsr.io/@fedify/fedify@1.3.0/doc/federation/~/MessageQueue
[1]: https://fedify.dev/manual/inbox#manual-routing
[@fedify/fedify/x/sveltekit]: https://fedify.dev/manual/integration#sveltekit
[SvelteKit]: https://kit.svelte.dev/
[full changelog]: https://github.com/dahlia/fedify/releases/tag/1.3.0
[JSR]: https://jsr.io/@fedify/fedify@1.3.0
[npm]: https://www.npmjs.com/package/@fedify/fedify/v/1.3.0