Describe your extension. We build it, publish it, and keep it working.
Say what it should do in plain words. BrowserHatch writes it, tests it in both browsers, submits it to both stores under your own publisher accounts, and maintains it after launch.
Five places in the first paid pilot. No code, no toolchain, no cloud account.
“When someone saves a quote, keep the page title and the date, and give them a tag box.”
One subscription, the whole life of the thing
Generating code is the easy part. What costs people their evenings is everything after it.
Built from a brief
Describe the outcome. We generate the code, build separate Chrome and Firefox packages, and test both before you see anything.
Published to both stores
Submitted under your own publisher accounts, only after you approve that exact release. Two stores, two independent outcomes, tracked apart.
Kept alive
Error reports, dependency checks, and tested fixes when a browser or a website changes underneath your extension.
A website included
A hosted page for your extension with install links and screenshots, built from its own details. One click to create it.
Four steps, and two of them are yours
You make the decisions. We do the work between them.
Describe it
One screen, plain words. We come back with what it will do, what it will not do, what it reads, and what it costs from your monthly allowance. You approve that before anything is built.
Try it
Your extension's interface runs in the browser you are already using, a second after it is built. When you want the real thing, install a test copy in Firefox with one click, and every later version arrives by itself.
Approve the release
You see the changes, the test results for both browsers, and exactly what the extension reads and stores. Approval covers that specific version. Change any of it and we ask again.
We keep it running
Monitoring, fixes, store questions, listing updates and reviews. You hear from us when a decision belongs to you, and not otherwise.
Chrome and Firefox never agree, and we stop pretending they do
Each store reviews on its own schedule and answers to nobody. Chrome can publish while Firefox is still asking a question. Most tools show you one status bar and hope. We show you both, honestly.
A submission is not a launch
We confirm a version by reading your public store page, not by trusting the upload response.
Partial success stays visible
A working Chrome release is never pulled because Firefox is slow. Both facts sit on the screen at once.
Reviewer questions in their words
When a store asks something, you see what they asked, who is answering, and what you need to approve.
One price per extension
Both browsers included. No setup fee. Cancel whenever you like and keep everything.
$39 / month, per extension
- ✓Chrome and Firefox, packaged and submitted separately
- ✓15 changes a month, built and tested in both browsers
- ✓60 minutes of hands-on store work from a person
- ✓Store page text, screenshots and submissions
- ✓A hosted website for your extension
- ✓Error monitoring, plus free fixes for anything we broke
- ✓Export the source, listings and full history at any time
When you go over
Nothing is charged without an approval that names the price first.
What we do not promise
Every one of these is somebody else's decision. Anyone who tells you differently is selling you a date they cannot keep.
- A review date, or approval. Google and Mozilla decide when they answer and what they accept. We tell you where each one stands and what happens next.
- Rankings, installs or revenue. We measure what can honestly be measured, label where each number came from, and never add a page visit to an install.
- That every bug is caught first. We tell you exactly what was tested, on which browsers, and what was not.
- Literally zero clicks. The stores require you to own your publisher accounts and do a few steps yourself. We show you that list before you pay, not after.
- Any extension you can imagine. Two supported patterns at launch, done properly, rather than everything done badly.
Questions people actually ask
Do I need a Google or Mozilla developer account?
Do I own the code?
What happens if I cancel?
Who can see my users' data?
How fast is it?
What can you not build?
The first pilot is small on purpose
We are taking five paying customers through the whole thing, from a sentence to a maintained extension on both stores. Tell us what you want to build.
Join the pilotOr email hello@browserhatch.com with a paragraph about the idea.