daily.dev: The Personalized Developer News Feed Built on Open Source

What daily.dev Solves and Who Uses It

Keeping up with a fast-moving technology landscape requires checking a dozen different blogs, release notes, and community sites. daily.dev addresses this by pulling developer content from 2,000+ trusted sources into a single feed that personalizes itself based on the tags you follow (such as #webdev, #ai, or #devops) and what you read, upvote, and bookmark.

The project is aimed at developers who want to stay current without active searching. The README describes it as a tool for learning and staying up to date, for interacting around current trends, and for collaborating with other developers. It is not aimed at managers or general tech readers. The entire core experience is free.

How the Feed Personalization Works

Personalization in daily.dev runs on two inputs: the tags and sources you explicitly follow, and implicit signals from what you read, upvote, and bookmark. You can follow or block tags and sources at any time, and you can switch between a personalized feed and a popular feed.

The feed includes content from sources the platform has indexed, not user-submitted links in the Hacker News sense. The README's FAQ explains how daily.dev differs from alternatives: dev.to is a blogging community where content is written on the platform itself; Hacker News is a single shared ranked list; daily.dev aggregates external content from 2,000+ sources and personalizes it per user. The comparison the README offers is that many developers use daily.dev alongside those platforms rather than as a replacement for them.

Squads are communities inside daily.dev where users share and discuss content with a team or interest group. They function as a social layer on top of the feed, allowing comments and collaborative bookmarking.

The reading list and bookmark features let you save posts across all platforms: the extension, the web app, and the mobile apps all share the same account state. That synchronization is handled server-side. The README does not document an offline mode or a way to export bookmarks to a local format.

Where to Get daily.dev and How to Start

daily.dev is available as a browser extension for Google Chrome and Microsoft Edge, as a web app at daily.dev, and as native mobile apps for iOS and Android.

For the browser extension, installing it from the Chrome Web Store or Microsoft Edge Add-ons store replaces your new tab page with the daily.dev feed. No account is required to see a feed, but creating one enables personalization, bookmarks, Squads, and search.

The extension's permission model is documented explicitly in the README's FAQ: the extension only replaces your new tab page. It does not track browsing on other websites, does not read or modify content on other pages, does not access browsing history, and does not inject scripts into any site. Because the project is fully open source, those claims can be verified in the code at the dailydotdev/apps repository.

Repository Layout: What This Repo Contains and What It Does Not

This repository, dailydotdev/daily, is the central hub for the daily.dev project. Its top-level contents include .agents/, .claude-plugin/, .claude/, .cursor/, .github/, assets/, and skills/. There is no application code in this repository.

The actual frontend code for the browser extension and web app lives in a separate repository: dailydotdev/apps. That distinction matters for anyone who wants to build from source or audit the extension code. This repository functions as a coordination and documentation layer, holding skills and configuration for AI-assisted development rather than the deployed application.

The repository has no GitHub releases, which is consistent with its role as a coordination hub rather than a versioned software package.

AGPL-3.0 License Implications

daily.dev is licensed under AGPL-3.0. The key provision of that license that distinguishes it from MIT or Apache-2.0 is the network use clause: if you modify the software and run it over a network so that others interact with it, you must release your modified source code under the same license.

For a developer who installs and uses daily.dev as-is, the license has no practical effect. For a company that wants to fork the codebase and offer a modified version to its employees or customers through a web interface, AGPL-3.0 requires releasing those modifications publicly.

The README confirms that daily.dev is an ad-supported business. The feed includes clearly marked native ads from developer-relevant brands. An optional paid subscription called daily.dev Plus adds power features. The README does not document what those features are beyond calling them power features.

day-to-day use of the extension does not involve any interaction with the AGPL terms at all. The terms become relevant only to developers who want to fork the codebase, modify the application, and make it available to users over the internet. In that scenario, the full modified source must be released. MIT or Apache-2.0 licensed tools like a self-hosted RSS reader carry no such condition.

daily.dev Versus a Self-Curated RSS Setup

The direct alternative to daily.dev is a self-managed RSS reader (such as Miniflux or FreshRSS) fed by manually chosen blog and release feeds. That approach gives full control over sources and requires no account on a third-party service. It also requires ongoing curation work: adding new sources, pruning dead ones, and filtering low-quality posts by hand.

daily.dev trades control for convenience. The platform curates the source list, handles feed fetching, and applies personalization automatically. The downside is that you cannot add an arbitrary source. The feed only includes content from sources the platform has indexed. The README does not document how to request new source additions or how the indexing process works.

The Squads feature has no direct equivalent in a self-hosted RSS setup. It provides a social reading layer that a personal RSS reader does not.

Maintenance and Community Support

The last push to this repository was on 2026-09-14, indicating active work. The project does not publish GitHub releases in this repository.

daily.dev is not a community-maintained side project. The README identifies it as a business with an ad-supported model and a paid tier, which implies a development team rather than a solo maintainer. The README states that user data is never sold.

The project accepts contributions. The browser extension's open source nature allows any developer to inspect the code and submit pull requests to the dailydotdev/apps repository. Community feedback channels listed in the README include the GitHub Issues and Discussions pages for bug reports and feature requests.

The .github/ directory in this repository contains workflow configuration, indicating that automated CI is in place. The .agents/ and .claude-plugin/ directories suggest AI-assisted development tooling has been integrated into the project's own workflow. These details are visible in the repository layout but their specific contents are not documented in the README.

Editorial conclusion

daily.dev is a practical tool for developers who want a curated, tag-driven news feed without hunting across multiple sites manually. The AGPL-3.0 license is the key constraint for anyone considering a fork or embedding the codebase in a commercial product: AGPL requires that modified versions distributed over a network be released under the same license. For individual use, that limitation does not apply. The frontend code lives in the separate dailydotdev/apps repository, not in this one, so this repository's scope is the central hub and coordination layer rather than the full application.

Frequently asked questions

Official sources

1. Official documentation
2. Official README
3. Project repository