Productivity extensions
Buttons, panels, and shortcuts added to the web apps your users spend their day in.
Browser extension development for the tabs your users live in.
Velvy builds Chrome extensions on Manifest V3: content scripts that work inside the pages your users already use, popups and side panels, and the backend for accounts, sync, and payments. We add AI features through the OpenAI and Anthropic APIs without exposing keys in the extension, and prepare the permissions and listing for Chrome Web Store review.
Spec/services/browser-extension-development
Best-fit engagement
Milestone-based hourly
Per milestoneBuilt with
- Chrome Extensions (Manifest V3)
- TypeScript
- React
- Node.js
- PostgreSQL
- Supabase
- Stripe
- OpenAI API
- Anthropic API
- Cloudflare
Working
Deployed to production
Tested
Automated tests and evals
Observable
Logs, traces, and alerts
What we build
Extensions that meet users where they already work.
AI assistants in the browser
Summarize, draft, extract, or fill forms on the current page, with model calls routed through your backend.
Capture and research tools
Data captured from pages into your CRM or database in one click, with clean structure and duplicate checks.
Internal team extensions
Private extensions that connect your team’s browser to internal systems without building a whole app.
Accounts, sync, and payments
Sign-in, settings that follow the user, and subscriptions through Stripe, backed by a real API.
Store listing and review
Minimal permissions, a clear privacy disclosure, and the listing assets Chrome Web Store review expects.
How we build it
Least permission, most usefulness.
The stack
- Chrome Extensions (Manifest V3)
- TypeScript
- React
- Node.js
- PostgreSQL
- Supabase
- Stripe
- OpenAI API
- Anthropic API
- Cloudflare
01
Design around the host page
We study the pages the extension runs on, because their markup changes and the extension has to cope.
02
Ask for little
The smallest set of permissions that does the job, which helps users trust the install and smooths store review.
03
Keep secrets server-side
API keys and AI calls live on your backend, never in the extension bundle.
04
Ship and update
Store submission, staged rollouts, and a release process for quick fixes when host sites change.
How to engage
Start with Milestone-based hourly.
Extensions suit milestone-based hourly: a working build on your machine first, then backend, payments, and store release as later milestones.
We start with paid discovery, never an unpaid test project, so the plan rests on your real requirements.
Milestone-based hourly
Per milestoneHourly work organized into agreed milestones, each with clear acceptance criteria.
Also fits
AI Feature Sprint
4–6 weeksAdding an AI feature to an extension you already ship? That is an AI Feature Sprint.
Common questions
Browser extension development, answered.
Something else on your mind? Ask us directly at hello@velvy.ai, or book the intro call below.
What is Manifest V3?
The current extension platform for Chrome. It replaces long-running background pages with service workers and tightens what extensions can do, which shapes how background work and network handling are built. New Chrome extensions are built on it.
Will the extension work in other browsers?
Chromium-based browsers such as Edge and Brave can usually run Chrome extensions. Firefox and Safari use different stores and some different APIs, so supporting them is a separate piece of work we assess with you.
Can an extension use AI safely?
Yes, when the model calls go through your backend. That keeps API keys out of the extension, lets you control cost and rate limits, and means you decide what page data is sent and stored.
How long does Chrome Web Store review take?
Review times vary and are set by Google. Narrow permissions and a clear privacy disclosure make review smoother, so we design for both from the start.
Can you build an extension for internal use only?
Yes. A private extension can be distributed to your team without a public listing, which suits internal tools that connect to your own systems.
Get started
Bring the messy problem. Leave with a plan.
Book an intro call. Tell us what you’re trying to build or automate, and we’ll tell you plainly whether we’re a fit and what a first engagement would look like.
Prefer email? hello@velvy.ai