Software · Desktop and consumer
Browser extensions
Extensions that add your tools to Chrome, Edge, Firefox and Safari, right where people already work.
An extension puts your product inside the pages people already use, from email to CRMs to shopping sites. We build Manifest V3 extensions with the narrowest permissions that do the job, test them across browsers, and take them through Chrome Web Store, Edge Add-ons, Firefox and Safari review.
What we build
- Content scripts that add buttons, panels and data to third-party web pages
- Side panels and pop-ups that connect to your product through its API
- Productivity tools for clipping, form filling, tab management and research
- Internal company extensions deployed through Chrome or Edge policies
- Safari web extensions packaged with Xcode for macOS and iOS
- Ports of Manifest V2 extensions to Manifest V3 service workers
DemoInteractive · sample data
Try it live.
A working sample with made-up data. It runs in your browser; nothing is sent anywhere.
{
"manifest_version": 3,
"name": "Quote Clipper",
"version": "1.4.0",
"permissions": ["storage", "sidePanel"],
"host_permissions": ["https://*.example.com/*"],
"background": { "service_worker": "background.js" },
"side_panel": { "default_path": "panel.html" },
"content_scripts": [{What it does well
Least privilege
Permissions cover only the sites and APIs the extension needs, which also eases review.
One codebase
WebExtensions APIs let one project build for Chrome, Edge, Firefox and Safari.
Side panel UI
A persistent side panel keeps your tool open beside the page without covering it.
Checked messaging
Content scripts, the service worker and your backend exchange data through validated messages.
Store publishing
Listings, privacy disclosures and permission justifications are prepared for each store.
Managed rollout
Company-wide installs and settings are pushed through browser enterprise policies.
Questions
What changed with Manifest V3?
Background pages became service workers that start and stop as needed, remotely hosted code is no longer allowed, and network blocking moved to declarative rules. Older extensions need their background logic and request handling reworked, which we plan and test before submission.
How long does store review take?
It varies by store and by the permissions requested, from hours to several days, and broad host permissions draw closer review. We keep permissions narrow and write clear justifications for each one, which helps review go smoothly.
Can the extension stay private to our company?
Yes. Chrome and Edge let administrators force-install an extension from an unlisted store entry or your own update server through group policy or device management, so it never appears publicly.