Why We're Building Phoenix Ad Blocker

When AdBlock was first created, the internet felt broken. Pop-ups everywhere. Auto-playing videos that blasted sound without warning. Flash ads that crashed browsers. Tracking scripts that followed users across every site they visited.

The team wanted to give people their browsing experience back. Not just block some ads, but restore control. Make the web feel like it belonged to users again, not to advertisers.

It was a simple idea: what if you could browse the internet the way you wanted, without constant interruption? What if privacy was the default, not something you had to fight for?

The response was overwhelming. Within a few years, over 140 million people were using AdBlock. They trusted it to protect their privacy, block intrusive content, and make browsing faster and cleaner.

That trust was everything. People installed a piece of software that had access to every website they visited. They did that because they believed the tool was on their side.

AdBlock succeeded because the incentives were aligned. The team building it were also power users who wanted better browsing. There was no tension between what users needed and what the product did.

The filter lists were community maintained. Updates came from people who cared about blocking ads, not from business development teams negotiating with advertisers.

It was fast. Lightweight. It did one thing well: blocked ads and trackers so you could browse in peace.

Most importantly, it was free and stayed free. No paywalls. No premium tiers. Just a tool that worked for everyone.

Over the years, we watched the ad blocking industry evolve. We saw patterns emerge. Revenue pressures change how products develop.

Some ad blockers introduced programs where advertisers could pay for exceptions. The logic was understandable: servers cost money, development costs money, and the product needed to sustain itself somehow.

But it created a fundamental conflict. If your revenue comes from advertisers paying for exceptions, you're not purely serving users anymore. You're balancing two different interests, and they don't always align.

We realized: how you make money shapes what we build.

We saw acquisitions where ad blocking companies were bought by larger entities. Sometimes those entities had their own advertising businesses or partnerships. Priorities shifted. Products changed.

We noticed privacy practices evolving as companies looked for additional revenue streams. Data collection for "analytics" or "improvement" that wouldn't have existed in the early days.

None of this was malicious. It was rational people responding to business realities. When you need significant recurring revenue and you can't charge users, you find other ways.

The question became: could you build an ad blocker that avoids these pressures entirely?

The ad blocking space has matured. There are excellent tools out there. uBlock Origin is a standout: completely free, no compromises, maintained by a developer who refuses to monetize it. That's admirable and rare.

Other ad blockers have found different paths. Some have programs for advertiser exceptions. Some bundle additional features. Each approach makes sense given different constraints.

Then Manifest V3 arrived. Chrome changed how extensions work, limiting some ad blocking capabilities. This affected several popular blockers, and millions of users needed to find alternatives.

We looked at this landscape and saw an opportunity. Not to compete on features or speed, those things are solvable. But to offer a different structural model entirely.

We started with a question: what if you designed an ad blocker where conflicts of interest were structurally impossible?

Not "we promise not to do bad things," but "the way this is built prevents bad things from being possible."

Structure over promises.

Employee-owned and operated: No single owner who can sell the company. No CEO with unilateral authority. Decisions are made collectively by the team building Phoenix. You can't acquire what isn't for sale, and it isn't for sale because no one person controls it.

No investors: We're not VC-funded. There's no board pushing for growth metrics or exit strategies. No pressure to scale to justify valuations. We can stay small and focused.

Zero revenue from advertisers: No programs for advertiser exceptions. No partnerships with ad networks. No paid allowlisting. We don't take money from the industry we're blocking. That eliminates an entire category of conflicts.

Donation-based: Phoenix will be supported by optional donations from users. No paywalls for core features. No premium tiers. If you want to support development, you can. If you can't or don't want to, Phoenix still works fully.

This isn't about being better people. It's about better incentives. When you don't need advertiser money and you can't be acquired, serving users becomes the only logical path.

Phoenix starts with the fundamentals: block ads and trackers effectively. Make pages load faster. Protect privacy. Do it reliably across different websites.

We're using community-maintained filter lists like EasyList and EasyPrivacy. These have been refined over years by people who care about blocking ads, not by business teams balancing revenue interests.

The architecture is straightforward: everything runs locally on your device. No data goes to our servers because we don't run servers that collect user data. It's not in our privacy policy. It's impossible with how we've built this.

For Chrome, we're building within Manifest V3 constraints. That means some limitations, but it also means Phoenix works where users are actually browsing. We'll launch on Chrome first and then Edge.

The goal is simple: effective ad blocking that works reliably and respects user privacy. Nothing revolutionary about the features. The innovation is in the structure.

We're building Phoenix in public because transparency matters. Not as a marketing strategy, but as a commitment.

When we launch the beta, the code will be open source. You'll be able to see exactly what Phoenix does. Security researchers can audit it. Developers can fork it. Users can verify it does what we say.

If we say Phoenix is user-first, people should be able to verify that. Show the code. Show the structure. Then users can judge for themselves.

The employee-owned and operated structure isn't common in tech. There's a reason we chose it.

In a traditional company, ownership concentrates at the top. A CEO or founder owns enough equity to make unilateral decisions. They can sell the company, change direction, or bring in investors without requiring broader consensus.

We've seen how that plays out in ad blocking. Companies get acquired. New owners have different priorities. Products change. Users discover their ad blocker is now owned by an entity with advertising interests.

An employee-owned and operated structure distributes ownership across everyone building the product. Decisions require collective agreement. No single person can sell the company. No acquisition can happen without consensus from the team.

It's slower. It requires more discussion. It's messier than top-down decision making. But it also prevents the exact scenarios we've watched play out in this industry.

Democratic governance is our moat.

You can't buy Phoenix because buying requires convincing every team member to sell. You can't pressure Phoenix through investors because there aren't any. You can't force Phoenix to monetize users because the people building it are the ones who decide, and they're building it for themselves as much as for others.

Here's what we're committed to:

• 100% blocking, zero compromises: No acceptable ads. No allowlists. No deals with advertisers. If it's an ad or a tracker, we block it.
• Privacy by architecture: We literally can't see your browsing data. It never touches our servers. This isn't a policy. It's how the system is built.
• Transparency: Open-source code. Democratic governance through an employee-owned and operated business. No secrets.
• Donation-based sustainability: Phoenix is supported by optional donations. No paywalls for core features. Free forever, supported by people who care.
• Can't be sold out: Employee-owned and operated structure means no single person can sell the company. No investors to satisfy. No acquisition offers to tempt us.

Fair question. Can an ad blocker survive on donations alone?

We're not trying to build a unicorn. We're not aiming for hundreds of millions in revenue. The goal is simpler: support a small team building quality software.

If Phoenix can sustain 7 to 10 full-time contributors, that's enough to build and maintain an excellent ad blocker. That's the target. Not growth for growth's sake. Not scale to justify valuations. Just sustainable development.

Wikipedia raises over $180 million annually from donations. Signal supports millions of users on donations. Mozilla funds Firefox development. Donation models work when users trust the mission.

We're building that trust through structure and transparency. Show users exactly how Phoenix works, what we spend money on, and how decisions get made. Then let them decide if it's worth supporting.

Build trust first. Ask for support second.

If donations don't sustain Phoenix, we'll shut it down rather than compromise. We've done this before. We know what compromising looks like and we won't repeat it.

The timing makes sense for a few reasons.

Manifest V3 changed the ad blocking landscape. Some popular blockers were significantly affected. Millions of users are looking for alternatives that work well within the new constraints.

More broadly, users are more aware of privacy issues than ever before. They understand that free products often mean they're the product. They're asking better questions about how software is funded and what trade-offs that creates.

And the employee-owned and operated model is gaining interest in tech. More people are questioning whether traditional startup structures serve users well, especially for tools that handle sensitive data.

We think there's space for an ad blocker that's transparent about its structure, honest about its limitations, and committed to never compromising on user interests.