It was time to have infrastructure designed specifically for people shipping browser extensions.
If you’ve shipped an extension, you know the hard part is rarely the code. It’s the path to publishing: store policies, review requirements, permission changes, and the small differences between browsers that turn releases into guesswork.
Extension.dev is designed around that reality.
You always know what’s being built, what’s being reviewed, and what’s going live. Artifacts come from real commits, previews are shareable links, and release channels are explicit. No guessing what the pipeline did.
The goal is fewer surprises between Chrome, Firefox, Edge, and Safari, and more confidence when pressing publish.
I build developer tooling focused on browser extensions and release infrastructure.
I created Extension.js, a zero-config CLI used in real projects to ship cross-browser extensions. It standardizes project structure, handles browser-specific manifest differences, and makes builds predictable across Chrome, Firefox, and Edge, covering the full development and build workflow.
Extension.dev sponsors Extension.js, the open source framework it builds on. The platform addresses the harder part of extension development: releases, previews, and distribution across browsers. Sponsorship funds the framework, and paid plans fund the platform.
If you are building in the margins or need a straight answer, reach out at hello@extension.dev.
Build, preview, and ship cross-browser extensions from GitHub, the console, or an agent.
Links and updates
The skill | Knowledge for your agents |
The MCP | Extension tooling for agents |
The pricing | Plans and the free allowance |