# Admin-approved in 5 tabs: how an unreviewed Chrome extension quietly got installed on 86k computers

> Source: https://stringers.io/en/ext/chrome_kkgepplhedkjieiomjhibinmdflaceje.html (Stringers / 什么值得做, generated 2026-11-15)
> Stringers tracks which small products suddenly took off each day, investigates why one by one, and distils playbooks from them. Numbers come from 15 databases we collect daily, each with source and date.
> For agents: these investigations and the underlying databases (verified revenue, App Store / Google Play charts, ad libraries, GitHub, Product Hunt…) are queryable live over MCP — tools feed (daily breakouts) / plays (playbooks) / hot / products / data. Setup: https://github.com/komako-workshop/stringers (the user signs in with Google at stringers.io/en/start.html to get a personal URL). Site index: https://stringers.io/llms.txt

> Chrome Enterprise has never had a "tab limit" policy, and rival extensions that limit plugins leave the cap for users to change themselves. This one hard-codes the cap, splits it into several entries by tier, and uses names admins actually search for, so one push reaches thousands of machines. The 5 tab version isn't growing on its own. The 10 tab version is (+30k since September).

[Chrome extension](https://stringers.io/en/ext/index.md) · written 11-14

Chrome Tab Limiter - 5 Tabs · jumpingjackflash1978

# Admin-approved in 5 tabs: how an unreviewed Chrome extension quietly got installed on 86k computers

**What it is** A Chrome extension that allows only 5 tabs per window. The cap is hard-coded, with no settings, and company admins force-install it on employees' computers.

**Why it took off** Chrome Enterprise had never offered a "limit tab count" policy, and rival extensions that limit tabs left the cap for users to change. This one hard-codes the cap, splits it into several entries by tier, and uses the exact terms admins search for, so one push can reach thousands of machines. The 5-tab version itself isn't growing; the 10-tab version is (+30k since September).

**C** **How to ride it:** Stop building tag-limiters. Look at what this product looks like, then find other controls that are missing from Chrome enterprise policy and that IT forums keep asking about. Build them as hardcoded, zero-permission extensions split into tiered entries, then sell a paid configurable version to MSPs.

Grade C: the entry itself isn't growing, and the tab-limiting niche is already taken. Its 86k installs all came from admins pushing it for free, with no evidence of any money collected. The approach is worth learning, but following it directly isn't worth much. Few people know about it yet.

10,000 users · rating 5.0 (1)

Chrome Tab Limiter - 5 Tabs is an extension that does one thing: it allows 5 tabs per window and closes any extra. It has no settings page, the cap is hard-coded and users can't change it, and it's built for enterprise IT to force-install on employees' computers via Group Policy. Over six years it has gathered 10k users and isn't growing recently. What's worth watching is that the same author released separate versions capped at 5, 10, and 20 tabs, totaling 86k users, with no promotion spent and no money collected.

### A remote desktop server with Chrome eating all its memory

Back on Jan 18, 2019, a sysadmin named mink posted on Spiceworks (the US IT admin forum): the company's remote desktop server kept running out of memory and crashing. Every time he logged in, he found users with more than 15 tabs open in Chrome, and Chrome alone was eating two-thirds of the 16GB of RAM.

> "I've dug through the registry, Chrome policies, and extensions. As an admin, there seems to be no way to limit how many tabs users can open. The extensions I've seen have to have their limits set manually for each user and each session, and as soon as I disconnect, they can raise the limit or delete the extension."

Someone replied that you can use Group Policy to force-install the extension; another responded: "I know that, but users can still go into the extension settings and change it." The thread was viewed 4,300 times, and the best answer was: "Tell them not to do it, or their tickets go to the back of the queue."

Nine months later, in Oct 28 of 2020, a Chrome extension called "Chrome Tab Limiter - 5 Tabs" showed up in the Chrome Web Store. Its description was just two sentences:

> "Chrome extension designed for use with Active Directory Group Policy. Enforce a maximum limit of 5 tabs in Google Chrome Enterprise."

It filled the gap this thread described.

### What it actually does

Takes a few dozen lines of code: each time you open a new tab, it counts how many are in the current window. Once it hits 5, the new tab closes and a message asks you to close one first. No options page, no permissions, declares no data collection, and the store page carries two badges: Featured and "Follows recommended practices." Last updated 2026 Apr 26.

The publisher is a personal gmail account, and the description calls itself Mission Labs. There is a call-center software company called Mission Labs in Manchester, UK, acquired by Gamma in 2021. Whether this extension was an internal tool built for agent desktops that was later published publicly can't be verified, but the scenario fits well: call-center agents, remote desktops, school computer labs, where dozens of people share one server's memory, and when one person opens lots of tabs, everyone slows down.

The limit is per window, so opening a new window gets around it. In February 2026 the author released a "1 Window, 5 Tabs" version, probably to close that gap (inference).

### Numbers: 10k users, 1 reviews

| Version | Launched | users | Reviews | Latest |
|---|---|---|---|---|
| 5 Tabs (the one covered here) | 2020-10 | 10k | 1 | No change for 30 days |
| 10 Tabs | 2023-05 | 70k | 1 | About 40k in September, ~70k in mid-November |
| 20 Tabs | 2024-10 | 5,000 | 3 | No change |
| 1 Window, 5 Tabs | 2026-02 | 1,000 | 0 | No change |
| 1 Window, 10 Tabs | — | 10 | 0 | — |

Sources: Chrome Web Store page (11-15), extension stats sites extops.dev and extensiontracker.

5 Tabs: the Chrome Web Store user count showed 20k from Nov 11 to 14, then dropped back to 10k on 15, and extops recorded "no change" for 30 days. The store shows user counts in tiers, so this looks like it was just bouncing between two tiers, not actually growing. What's growing is the 10 Tabs version: up 30k since September.

The most telling signal is the review count. A typical utility extension gets one review for every 100 to 200 users. Here, 10k users have 1 reviews, and 70k users also have 1 reviews. These users didn't install it themselves. An administrator added the extension ID through Group Policy or the Chrome Enterprise console, and it was pushed to whole fleets of machines. Employees can't remove it and don't bother to review it (inference, high confidence). A user count that jumps by thousands at a time also looks like one organization rolling it out to thousands of machines at once.

### Where users come from: one administrator's search

There is no website and no ads, and nobody on X, Reddit, or TikTok seems to mention it. The likely path: an administrator runs into a problem like mink's and searches Google or the store for "chrome tab limiter group policy." The extension's name and description match those words, so they click through, copy the ID, and push it company-wide. In the store, the 5, 10, and 20 variants are linked to each other under "Related extensions," so anyone who finds one sees the others. Aggregator sites like Softonic and chrome-stats also generate pages automatically that get indexed, but the author didn't create them.

Each install is a single administrator's decision, and one decision can cover hundreds or thousands of machines. Once installed, very few people ever uninstall it.

### Why this one

There are dozens of tab limiter extensions in the store, so this category is far from scarce. This one got installed because of a few things others didn't do:

- **Chrome itself never shipped this policy.** In January 2017, someone filed a request in Chromium titled roughly "too many tabs exhaust terminal server memory." It was later merged into another request and still isn't implemented. Google's optimization advice for virtual desktops amounts to "open fewer tabs, install fewer extensions."

- **Competitors leave the limit in the user's hands.** The older xTab (listed in 2014, 40k users) and Tab limit (10k users) let users set their own limit in an options page. An admin can push them, but users can change the setting back, so the push accomplishes nothing. This one hardcodes the limit, so pushing it means it actually applies.

- **Tiers are sold as separate products.** Chrome does support letting admins pass parameters to extensions through policy, but this one doesn't use that. It publishes a separate listing for 5, 10, and 20 instead. Admins don't have to write any configuration. They pick the number in the name, and each name is itself a search term.

- **Zero permissions make it easy to pass security review.** Enterprises have to vet extensions before deploying them. An extension that requests no permissions, collects no data, and has been featured by the store is unlikely to get blocked.

### Who it's competing with

| Competitors | Scale | Difference |
|---|---|---|
| Tab and Window Limit | 10k users | The closest match: first listed in September 2023, hardcodes 10 tabs + 2 windows. The description also mentions Group Policy, but it only has this one tier. |
| xTab, Tab limit, and similar | 10k to 40k | The user sets the limit. Good for individuals trying to cut down on tabs, not for administrators. |
| OneTab, Tab Wrangler, and various tab-suspender extensions | OneTab 2M | Collapse tabs or suspend them to save memory, with no limit on the count |
| Chrome's built-in memory saver | All users | Saves memory but has no tab count limit |
| Full lock-down software like Citrix | — | Requires purchasing and deployment, much heavier than an extension |

Among extensions that admins can push and users can't change, this series and Tab and Window Limit are the only few in the store.

### What it doesn't do

None of this is monetized. There's no website, no paid version, and no in-app purchases. Whether the author takes money privately elsewhere can't be found. Installs on 86k corporate machines haven't brought in a single dollar so far.

### If it were you

**C. Don't build another tab limiter. That space is already taken, and install count doesn't mean money. What's worth taking away is the approach: find an admin control missing from Chrome's enterprise policies that IT forums keep asking about, and build an extension that admins can push and users can't override.**

**Good fit for:** people who have worked in enterprise IT, desktop support, or as an MSP (a managed service provider that runs computers for small businesses) and know what admins complain about every day; indie developers who want to build installs first and a channel they can sell to businesses.

**Not a fit for:** anyone hoping to earn money directly from the extension. Users of this kind of extension are employees, and the buyer is the administrator, who in this case paid nothing. To make money, you'd have to go to MSPs or call centers and sell seats. That's sales work, not coding.

**How to do it:** Use the same shape with a different control, such as allowing only certain websites, blocking certain file downloads, keeping a page permanently open, locking an exam or agent screen, or hiding a particular button. Hardcode each one, request zero permissions, and name it with the phrase admins would actually search for, with one listing per parameter tier. To charge, build a paid, configurable version next to the free hardcoded one: admins pass parameters via policy, use site allowlists, and get usage reports, sold per seat to MSPs.

**How to get users:** No ads needed. Title and describe it as "xxx for Group Policy / Chrome Enterprise." Look for unanswered old threads on Spiceworks and r/sysadmin, and link back to the extension. The store's "Related" section will connect the tier listings to each other.

**When to move:** No rush, but each admin control has a deadline: the day Chrome builds that policy into enterprise, the matching extension becomes useless. Before starting, check the Chrome enterprise policy list and confirm it's missing and not on the roadmap.

**Signs you've misread it:** ① The 10 Tabs version flatlines around 2027k into early 70, suggesting the enterprise rollout wave is over and demand is smaller than it looks; ② a "maximum number of tabs" policy appears in Chrome enterprise; ③ the store takes down this kind of per-tier listing as duplicate content; ④ your paid, configurable version has been live for three months and not one seat has sold, which would show admins only want the free option.

[Chrome store page ↗](https://chromewebstore.google.com/detail/chrome-tab-limiter-5-tabs/kkgepplhedkjieiomjhibinmdflaceje)

**Research notes: competitor table, acquisition evidence, full research report**

Competitors

| Name | Where | Launched | Scale | How it differs from this one |
|---|---|---|---|---|
| Chrome Enterprise policy | Big-company features | — | full range | No "maximum tabs" policy; the 2017 Chromium request (41294137 → 40637273) remains unimplemented |
| xTab | Chrome | 2014-03 | 40k users / 131 rating | The limit is set by the user in the options page, and users can change it even if an admin forces the extension |
| Tab limit(3arry.dev) | Chrome | 2022-05 | 10k / 20 rating | Personal focus tool, user sets the limit |
| Tab and Window Limit | Chrome | 2023-09 | 10k / 4 rating | Closest: also hardcoded and mentions GPO, but only one tier of 10 tabs + 2 windows |
| Limitador de Tabs 10 | Chrome | 2023-07 | 576 | Spanish, hardcodes 10 tabs, very small scale |
| Tab Limiter (multiple with the same name) | Chrome | 2023-2026 | 4k / 3k / a few hundred | For personal use, limit adjustable |
| OneTab / Tab Wrangler / Tab Suspender types | Chrome | 2010-2026 | OneTab 2M, Tab Suspender 100k, Tab Wrangler 50k | Saves memory by collapsing, suspending, or auto-closing idle tabs, without a hard limit |
| Chrome Memory Saver / automatic tab discarding | Big-company features | 2022 | full range | Saves memory but has no tab count limit |

Where users come from

- Inferred **Enterprise admin GPO / Admin console forced install** : the description says it's for AD Group Policy and Chrome Enterprise; 10k users but only 1 ratings (10 Tabs version: 70k users vs 1 ratings); user counts jump in 10k steps

- Inferred **Store search (the name is the search term) + IT forum pain points** : Spiceworks 2019 thread (4.3k views): admins complain that users can still change a forced limiter's settings; similar r/sysadmin threads; the threads don't mention it directly

- **Verified** **Store placement** : the store page carries the Featured badge; the 5/10/20 tiers link to each other under "Related"

- **Verified** **Passive SEO from aggregator sites** : Softonic, crx4chrome, chrome-stats, and ExtScope have auto-generated pages

- Inferred **Ads / social / website** : none found. No website; x-radar shows no relevant content for 90 days; Exa returns only store pages and stats sites

## Why Chrome Tab Limiter - 5 Tabs (kkgepplhedkjieiomjhibinmdflaceje) turned up

### Bottom line first

- This entry **isn't actually running** . It was pulled in by extops' "fastest-growing this week" chart, rank #28 (2026-11-14, "+10k, from 10k"), but that's store user counts bouncing between the 10k and 20k marks: our snapshot went from 11-11 to 11-14 at 20k, then back to 11-15 at 10k. The store page shows 2026-11-15 10,000 users, and extops and ExtScope both list it as "unchanged / Flat" for 30 days. Its 10k users are six years of accumulation since it launched on 2020-10.

- The thing worth noticing is the **matrix** it sits in and the pattern behind it: the same personal gmail account (jumpingjackflash1978, which calls itself Mission Labs in its description) has one listing for each tier of a tab limiter with hardcoded caps, no settings and zero permissions: 5 / 10 / 20 tabs, 1 windows, and so on, all pushed to corporate IT for force-install via AD Group Policy. 10 Tabs, the 70k-user version, is up 30k since Sep 1, and it's the one in the matrix that's actually growing.

- Why it took off: Chrome's enterprise policies still have no "max tab count" setting. **No** such policy has been added in 2017 years, even though people have been asking for it on Chromium since then. Existing tab-limit extensions (xTab, Tab limit, etc.) let users change the cap themselves, so even if an admin force-installs one, the user can change it back. This one does the reverse: the cap is hardcoded and comes in a few fixed tiers, so an admin just picks one and pushes it. That's the differentiator, and it's the reason it gets installed.

- No website, no pricing, no promotion, 1 ratings. Almost nobody knows about it yet.

### 1. What it is

- Store page (2026-11-15 reads): "Mission Labs tab limiter - limits the maximum number of open tabs to 5. Chrome extension designed for use with Active Directory Group Policy. Enforce a maximum limit of 5 tabs in Google Chrome Enterprise." Version 1.4,2026-04-26, last updated 127 KiB, English (UK), developer email jumpingjackflash1978@gmail.com, not a trader, declares no data collection. The page carries a **Featured** badge and a "Follows recommended practices" badge. Source: [chromewebstore.google.com/detail/chrome-tab-limiter-5-tabs/k…](https://chromewebstore.google.com/detail/chrome-tab-limiter-5-tabs/kkgepplhedkjieiomjhibinmdflaceje)

- chromestore library: MV3, manifest permissions empty `[]`, no in-app purchases, no website; published 2020-10-28.

- Behavior (ExtScope code analysis): when a new tab opens, it counts the tabs in the current window. At 5 tabs it closes the new tab and shows a prompt asking the user to close one first. [extscope.org/extension/kkgepplhedkjieiomjhibinmdflaceje](https://extscope.org/extension/kkgepplhedkjieiomjhibinmdflaceje). The cap is per **window** , so opening a new window gets around it. That's probably why 2026-02 later shipped a "1 Window, 5 Tabs" version (inferred).

- Mission Labs: a UCaaS / cloud contact-center software company in Manchester, UK (Amazon Connect apps, CircleLoop, SmartAgent), acquired by Gamma in 2021-03. [gammagroup.co/resources/news/gamma-acquires-mission-labs/](https://gammagroup.co/resources/news/gamma-acquires-mission-labs/), [uk.linkedin.com/company/missionlabs](https://uk.linkedin.com/company/missionlabs). The extension was published from a personal gmail account, unrelated to the company account. Whether it was an internal tool Mission Labs built for its contact-center clients and later made public is **unverified** , but it's plausible: agent desktops on RDS / Citrix shared desktops are exactly where tab limits matter most.

### 2. Data

| Item | Date | users | Score | Recent changes |
|---|---|---|---|---|
| Chrome Tab Limiter - 5 Tabs (this entry) | 2020-10-28 | 10,000 | 1 | 30 days unchanged (extops); snapshots 11-11~11-14 read 20k, then 11-15 back to 10k |
| Chrome Tab Limiter - 10 Tabs | 2023-05-27 | 70,000 | 1 | Since 9/1 +30k, over 30 days +10k (extops); extensiontracker 9-27 60k → 10-28 70k |
| Chrome Tab Limiter - 20 Tabs | 2024-10-09 | 5,000 | 3 | Unchanged |
| Chrome Limiter - 1 Window, 5 Tabs | 2026-02-06 | 1,000 | 0 | Unchanged |
| Chrome Limiter - 1 Window, 10 Tabs | — | 10 | 0 | — |
| Heart Rate Simulator (unrelated) | 2026 | — | — | — |

Sources: chromestore library item / item_snap (2026-11-01~11-15), extops_list (2026-11-14 trending_fastest, rank 28), [extops.dev/extensions/kkgepplhedkjieiomjhibinmdflaceje](https://extops.dev/extensions/kkgepplhedkjieiomjhibinmdflaceje), [extops.dev/extensions/mcgcfdbfmellkobfighckmhminaijjbo](https://extops.dev/extensions/mcgcfdbfmellkobfighckmhminaijjbo) (publisher total 6 listings, 86k users), [extensiontracker.com/extension/mcgcfdbfmellkobfighckmhminaij…](https://extensiontracker.com/extension/mcgcfdbfmellkobfighckmhminaijjbo).

A few ways to read it:

- 10k users but only 1 ratings (10 Tabs has 70 ratings from 1 users, about 0.001%). Typical utility extensions get a rating rate of about 0.5–1%. A rate this low basically rules out voluntary installs. It points to admin force-installs (ExtensionInstallForcelist), where end users neither chose the extension nor bother to rate it.

- User counts jump in steps (10 Tabs adds about +10k each time), which fits "one organization rolls it out and thousands of machines get it at once." The granularity is too coarse to tell which organizations.

- 5 Tabs is the strictest tier. It suits kiosks, agent desktops, and exam rooms, a narrower use case than 10 Tabs, so it has fewer users and isn't growing.

### 3. Competitors: who else does the same thing

| Name | Where | Launched | Scale | How it differs |
|---|---|---|---|---|
| Chrome / Chrome Enterprise policies themselves | Big-company features | — | — | **No** "max tabs" policy exists. Chromium issue 41294137 (2017-01, "Too many tabs kills terminal server RAM") was marked as a duplicate, moved to 40637273, and never built. Google's VDI optimization docs only advise keeping fewer tabs open and installing fewer extensions. [issues.chromium.org/41294137](https://issues.chromium.org/41294137), [support.google.com/chrome/a/answer/9303118](https://support.google.com/chrome/a/answer/9303118) |
| xTab | Chrome (open source) | 2014-03 | 40k users, 131 rating | The user sets the cap on the options page and can choose whether to close the oldest tab or block new ones. It's aimed at individuals. techdirectarchive showed admins how to force it via GPO 2024 years ago, but users can still change the settings. |
| Tab limit(3arry.dev) | Chrome | 2022-05 | 10k, 20 rating | User sets the cap; individual focus |
| Tab and Window Limit(carpiusdetricksiuprac) | Chrome / Edge | 2023-09 | 10k, 4 rating | **Closest peer** : hardcodes 10 tabs + 2 windows, and the description also says "Can also integrate to Windows Server GPO." Only one tier. |
| Limitador de Tabs 10 | Chrome | 2023-07 | 576 | Spanish-language, hardcodes 10 tabs, very small |
| Tab Limiter (several with the same name: denis.oleshkevich / VodzhaevIvan and others) | Chrome | 2023–2026 | 4k / 3k / a few hundred | Individual focus, user-adjustable |
| OneTab, Tab Wrangler, various Tab Suspenders | Chrome | 2010–2026 | OneTab 2M, Tab Wrangler 50k, Tab Suspender 100k | They solve "too many tabs eat memory" another way: collapse, sleep, or auto-close idle tabs, with no hard cap. |
| Chrome's built-in Memory Saver and automatic tab discarding | Big-company features | From ¥2022 | full range | Saves memory but doesn't limit the count. Some enterprises even install extensions specifically to turn it off (No-Tabs-Auto-Discard, 6k users). |
| Browser lockdown / kiosk software (Citrix, kiosk browsers, etc.) | Other | — | — | Full lockdown is far heavier than a single tab limit and requires procurement (not checked individually) |

Bottom line: tab limiters are not scarce. There are dozens in the stores. But only this series and Tab and Window Limit can do what matters: **let an admin force the limit so users can't change it** . Big tech left the gap open: Chrome hasn't shipped this policy in nine years.

### 4. How users arrived

- **Admin force-install (main channel, strong inference)** : the description is written directly for AD Group Policy and Chrome Enterprise. The rating rate is about 0.001%, and user counts jump in steps of 10k. Admins enter the extension ID in GPO or the Admin console, and the whole fleet installs it automatically. End users can't remove it.

- **IT forum pain point → store search** : a Spiceworks thread from 2019 years ago (4.3k views) has admins complaining that Chrome tabs eat RDP server memory, and that "the extension has to be set per user, and users can raise the limit or remove it once disconnected." Someone replied "you can force-install extensions via GPO," and the original poster said "even after forcing it, users can still change the settings." That's the gap this fills. [community.spiceworks.com/t/anyone-know-how-to-set-a-limit-on…](https://community.spiceworks.com/t/anyone-know-how-to-set-a-limit-on-number-of-tabs-a-user-can-have-open/693446). There are similar threads on r/sysadmin too (Firefox / RDS tab limits). None of these threads **name** it directly. Admins most likely found it by searching "chrome tab limiter group policy": the name matches that query exactly.

- **Store traffic on its own** : the Featured badge, and the "related" panels on the other tab limiters link to 5 / 10 / 20 tiers.

- **Aggregator SEO (passive)** : auto-generated pages on Softonic, crx4chrome, chrome-stats, and ExtScope show up in search. The developer didn't build these.

- **Nothing found** : no website, ads, or discussion on X / Reddit / HN / TikTok. x-radar found nothing for "tab limiter" in the last 90 days, and Exa only returns store pages and stats sites.

### 5. Why it took off

1. The platform left a gap it hasn't filled in nine years: Chrome's enterprise policies have no tab count cap. The request has been open since 2017 (Chromium 41294137 → 40637273).

2. Other products have the wrong shape: existing limiters leave the cap to the user, so when an admin pushes one, it's effectively unset (Spiceworks 2019). This one hardcodes the cap with no options page, so it takes effect as soon as it's pushed.

3. Tiers as SKUs: it doesn't offer a config option (MV3 managed storage could have let admins set the cap through policy, but it doesn't). Instead it lists one entry per 5 / 10 / 20 / 1 window. Admins don't have to write JSON; they just pick the number in the name, and each entry's name is itself a search term.

4. Zero permissions, no data collection, Featured: with an empty manifest permission list, it passes security review (Koi, IT security teams) easily, and enterprise allowlists don't block it.

5. Demand concentrates on shared desktops: RDS / Citrix / VDI, contact-center agents, school computer labs. When tabs pile up, everyone on the server slows down together. Mission Labs' contact-center background fits this use case (unverified).

### 6. Differentiation, and whether that's why it took off

The differentiator is "**set by the admin, users can't change it** ": the cap is hardcoded, there's no settings UI, it needs no permissions, it's split into tiers as separate entries, and it plugs straight into AD GPO force-installs. The feature itself is a few dozen lines of code with no technical moat. The moat is **positioning** : it's one of the few in the store that explicitly says "for Group Policy," its name matches admin search terms exactly, and it works as soon as it's installed. That's why it gets installed: each jump in users is an admin at some organization making the call, not a user choosing it.

### 7. Visibility / copycats

- Almost nobody knows about it yet: no website, no pricing, no press or X coverage, 1 ratings. Only auto-generated pages on extension stats sites.

- Peers: Tab and Window Limit (2023-09, hardcodes 10 tabs and 2 windows, mentions GPO), Limitador de Tabs 10 (2023-07, hardcodes 10). All launched after the 5 Tabs version (2020-10). Whether they copied it is unverified. All have a single tier, and all are under 10k users.

### 8. What others can learn

- **"Policy push" extensions** : find admin controls that Chrome's enterprise policies don't offer but that IT keeps asking about on forums (limiting tabs or windows, blocking certain file downloads, forcing a site to stay open, locking down agent or exam machines, hiding a button). Build them as hardcoded, zero-permission extensions, name them with the terms admins actually search for, and split them into parameter tiers as separate entries. The buyer is the admin. One deployment covers hundreds or thousands of machines, and once installed they rarely get removed.

- Monetization: this series has none so far. You could offer a "free hardcoded version + paid configurable version" (managed-storage config, more tiers, usage reports, domain allowlists) and sell per seat to MSPs and contact centers. You could also give the free version away for reach and sell VDI optimization consulting alongside it.

- Watch out: if Chrome ships this policy someday, these entries lose their value. Also, a matrix of tiers could be flagged as "duplicate listings / spam" by the store, so you'd need to guard against that.

### 9. Still unclear

- Who the actual installers are (which organizations, which industries) is too coarse to tell. The relationship to Mission Labs / Gamma is unverified.

- Since September the 10 Tabs version has added +30k. Can't tell whether that's one or two large organizations rolling it out or many small ones adopting it gradually.

- The 5 Tabs version read 20k across snapshots 11-11~11-14. Can't tell whether real users briefly crossed a threshold or the store data just fluctuated. Either way, it's not sustained growth.

- Whether the developer has collected money elsewhere (privately, through MSP channels) can't be checked.

This article was written by AI from public data and the data we collect daily. Numbers are sourced, and inferences are labeled.
