BrowserHatch Join the pilot
Chrome and Firefox

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.

Join the pilot See how it works

The first paid pilot takes five customers. 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.”

Version 1.5 Tested in both browsers
CChrome
Live Version 1.5, confirmed on the public listing
FFirefox
In review Still on 1.4.2 until Mozilla answers

One subscription covers build, publishing and maintenance

Code generation is the first step. Testing, store submission and maintenance take most of the time.

Built from a sentence

Describe the outcome. If an idea risks a store rejection, we tell you why, and you decide. Sign-in, a database, file storage and connections to services you already use are built in when the idea needs them.

Published to both stores

Submitted under your own publisher accounts, only after you approve that exact release. Two stores, two independent outcomes, tracked apart.

Maintained

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

You describe the extension and approve each release. BrowserHatch does the rest.

1

Describe it

One screen, plain words. We come back with what it will do, what it reads, and what it costs in credits. Change your mind as often as you like; every change is built and tested in both browsers.

2

Try it

Your extension's interface runs in the browser you are already using, as soon as it is built. When you want the real thing, install a test copy in Firefox with one click, or load it into Chrome with a guided two-minute setup.

3

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.

4

It keeps running

Monitoring, dependency checks and tested fixes when a browser or a website changes underneath you. Ask for a change in plain words whenever you like. You approve every release.

Chrome and Firefox review your extension separately

Each store reviews on its own schedule. Chrome can publish while Firefox is still asking a question. BrowserHatch shows a separate status for each store.

✓Your approval
✓Sent to store
✓Store review
✓Live

Live means confirmed on the store page

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, what we propose, and what you need to approve.

Pricing

Both browsers included. No setup fee. Cancel whenever you like and keep everything.

$29 / month, Pro. Up to 5 extensions. Pilot price, held for twelve months

  • ✓Chrome and Firefox, packaged and submitted separately
  • ✓A monthly credit allowance. Unlimited changes inside it, each built and tested in both browsers
  • ✓A backend for your extension when it needs one: sign-in, database, file storage, curated integrations
  • ✓Store page text, screenshots and package submissions
  • ✓A hosted website for your extension
  • ✓Error monitoring, plus free fixes for anything we broke
  • ✓Export to GitHub or download the source, listings and full history at any time

When you go over

More extensions$9 a month for each published extension after the first 5.
Extra creditsMetered. You see the credit cost of every build before it runs.
Your limitYou set a monthly ceiling on extra spending
At the limitNew work pauses and we ask. Your extension keeps running and your website stays up.
Store dashboardsYours. Where a store offers only a form, we generate every value and you paste it in.

Nothing is charged without an approval that names the price first.

What we do not promise

These outcomes are outside our control, or we cannot guarantee them.

  • 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.
  • No steps for you. 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.
  • Hands-on store work. Nobody here logs into your store dashboard. We generate every value a store asks for, and you enter it under your own login.

Questions

Do I need a Google or Mozilla developer account?
Yes, in your name, and that is deliberate. Your extension belongs on your account, so it survives us. We walk you through creating them. For Chrome you link a service account created for your publisher alone. For Firefox you paste an API key from your own account. Both are revocable by you at any moment.
Do I own the code?
Yes. Source, build instructions, store listing content, screenshots and the full release history are exportable from your dashboard at any time, as a download or straight to your GitHub. Third-party libraries keep their own licences, which we list.
What happens if I cancel?
New work stops at the end of the month you paid for. Your extension stays published, your store accounts stay yours, and your export stays available. We do not remove a listing or switch off an extension to keep you subscribed. If your extension uses a backend we host, we tell you before anything is switched off and give you a window to move.
Who can see my users' data?
Nobody here, in most cases. Extensions we build keep data in the user's own browser unless your product needs sign-in or a database. Then it runs on a backend created for that one project, isolated from every other. Diagnostics exclude page content, addresses and form values. Your content is not used to train models.
How fast is it?
A first working preview within minutes, in the browser you are already using. A tested build for both browsers usually within the hour. Store review is the slow part, and that clock belongs to Google and Mozilla. We report the wait, never predict it.
What can you not build?
Anything that harvests credentials, tracks people quietly, injects ads, evades a browser's security, or clones somebody else's extension. If an idea risks a store rejection or breaks another service's terms, we tell you why before you continue. The decision is yours.
Pilot

The first pilot takes five customers

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 pilot

Or email hello@browserhatch.com with a paragraph about the idea.