Ship Chrome extensions
without fighting the review process.
Extention packages, validates and reviews your extension against Chrome Web Store policy — then publishes it to your own developer account via OAuth. Pay ₹19 per submission or subscribe for a monthly quota.
- No shared publisher account
- Automated malware & AST scanning
- GST-compliant invoicing
Your items
6 extensions · 1 in review
Weekly users
152.6K
Avg rating
4.8
Quota left
7 / 10
12,400+
Packages processed
98.2%
Pass automated pre-review
< 6 hrs
Median review turnaround
₹19
Per submission, no lock-in
How it works
Four stages from zip to live listing
Every submission runs the same deterministic pipeline. You always know which stage your extension is in and exactly what is blocking it.
Platform
Built for teams that publish regularly
The tooling a serious extension team needs — without giving up ownership of the developer account.
Guided submission wizard
Seven steps mirroring the real developer dashboard: package, listing, graphic assets, privacy, distribution, payment, submit.
Dynamic permission justifications
Every sensitive permission detected in your manifest generates its own required justification field, checked against your declared single purpose.
Versions & staged rollout
Ship new versions, control rollout percentage, and roll back to any previous package from one timeline.
Install & rating analytics
Weekly installs, active users, and rating movement pulled from the Chrome Web Store API into one dashboard.
Durable artifact storage
Packages, screenshots, promo tiles and video land in S3/R2 with signed URLs — never on ephemeral disk.
Full audit trail
Every review action, status transition and payment event is logged with actor and timestamp for compliance.
Security & compliance
Your developer account is never at risk
Reseller-style publishing under one shared account means a single policy violation can take down every extension on the platform. We refuse that architecture. Extention is an automation and review layer — you remain the publisher of record.
Read the security modelYour account, your token
Publishing always uses the submitting developer's own OAuth credentials. There is no shared platform developer account to suspend.
Tokens encrypted at rest
Google access and refresh tokens are encrypted in the database and never exposed to the browser.
PCI-safe payments
Card data never touches our servers. Razorpay and PayPal hosted checkout handle every transaction, confirmed only by signed webhooks.