Hype StackHypeStack
Ships with every new project

Chrome, Edge, Firefox.
One extension for all three.

The template ships a browser extension built with the same React, the same theme tokens, and the same typed API as the rest of your stack.

See the startersRead the docs
Browser / toolbarmanifest v3
app.aether.dev

Aether

signed in as sarah@acme.io

Open tasks

7

Mentions

3

live from your backend

Payment received: sarah@acme.io moved to Premier

same typed sdk as the web app

deploy extension

  • Chrome Web Store
  • Edge Add-ons
  • Firefox AMO

published from one command

One build, three stores

One codebase. Every browser family.

Vite builds the extension twice: a Manifest V3 target that Chrome and Edge both accept, and a Firefox target of its own. Nothing forks. The source directory, the components, and the theme are shared.

Chrome Web Store

Edge Add-ons

Firefox AMO

What you get

What it does, and where to check.

Plain answers on the left, the file or command that proves each one on the right. The extension reads the same design tokens as the web app, so a retheme covers the toolbar too.

  • A real extension app inside the monorepo

    apps/extension

  • Same Tailwind tokens as the web app

    --extension-theme

  • Talks to your backend with full types

    sdk.users.$get

  • Chrome and Edge share one MV3 build

    dist/chrome

  • Firefox build signed and submitted

    web-ext

  • Each store publishes independently

    deploy extension
Ship it

Store submission, scripted.

hype-stack deploy extension builds both targets, zips the artifacts, and pushes each one through its store's API. A store without credentials is skipped with setup instructions instead of failing the run, so the first deploy doubles as the setup guide.

a failed store never blocks the others

It also chains after the web deploy, so one session puts everything out. Read the deploy docs.

The payoff

What it saves you.

No second repo, no per-browser forks, and no afternoon lost to store dashboards every release.

  • 3

    Chrome
    Edge
    Firefox

    Stores from one command

    Chrome Web Store, Edge Add-ons, and Firefox AMO, each through its own API.

  • 1

    a fork per browser3x the work
    apps/extensionone src dir

    Codebase for every browser

    Vite builds the chrome and firefox targets from the same source directory.

  • 0

    store outageskipped, not failed
    still publishedthe rest ship

    Releases blocked by one store

    Stores publish independently. A Chrome outage never holds back Firefox.

Feature packs to grow with

Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.

FeatureTeamsTeam workspaces with members, roles, icons, and email invitations on top of your starter.Team workspacesMember rolesFeatureBilling (Stripe)Stripe integration, subscriptions, billing flows, and an admin revenue widget.Stripe checkout & portalSubscription plansFeatureProjectsOrg-scoped projects with members, favorites, icons, and a navbar switcher.Project CRUDMembers & rolesFeatureWhiteboardA collaborative whiteboard: sticky notes, freehand ink, shapes, images, and layers on one infinite canvas, synced live.Infinite canvasLive multiplayer
See all 12 packs

Questions, answered

Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.

Be in the toolbar, not just the tab.

apps/extension is scaffolded with every new project, themed like the rest, and published with one command.

See the startersSee pricing

included with every project