Organize logins into Projects → Environments → Credentials. Autofill with one click. Never syncs, never uploads.
activeTab, scripting, storageNot a vault. Not a sync service. A surgical tool for the credentials you juggle every day.
Projects contain environments. Environments contain credentials. The mental model already lives in your head — Gupt just stops you from reinventing it in a Notes file.
Fuzzy matching maps. Works with all controlled inputs out of the box.
Lives in chrome.storage.local. No network code anywhere in the source. Audit it
yourself — it's a few hundred lines of plain ES modules.
Each project declares which fields it stores — built-ins (Email, Mobile, Password) plus your
own custom labels like Name, City, or License key.
Back up everything as a single file. Move to a new machine, share a project with a teammate, or commit your test logins to a private repo.
Follows your OS. Manual override remembered. Both themes hand-tuned for legibility.
Admin, viewer, premium-trial, expired-card, enterprise-tier-3 — keep every role one click away.
One project per tenant, environments for staging vs prod. No more "which login is this again."
Tag the role label (demo-fresh, demo-loaded) and Gupt fills the right one instantly.
Spin up throwaway credentials per project. Export and rotate when you move on.
No onboarding wizard. No first-launch tour. Open the popup and start typing.
Name it after the app. Pick the fields you want to store — built-in or custom.
Staging, production, QA — separate buckets per environment. Switch with one click.
Each gets a role label (admin, qa, premium). The form only asks for the fields you declared.
Open the login page, click Fill, watch the fields populate. Works with React/Vue.
Gupt has no servers, no analytics, no sync, no accounts. Audit the source — there are zero network calls. The only thing it asks of you is to install it.
chrome.storage.local
// The entire surface area Gupt asks for
"permissions": [
"activeTab", // fill the page you're on
"scripting", // inject the fill routine
"storage" // keep data on your device
]
// No "host_permissions". No remote fetch.
// No background sync. Ever."I have 18 test accounts across staging, prod, and three QA stacks. Gupt is the first thing I install on a new machine."
"I stopped trusting cloud password managers with disposable dev logins. Gupt keeps them where they belong — on my laptop."
"My demo logins used to live in a Slack DM to myself. Now they live one click away, organized by tenant. Zero context switches."
Those are great general-purpose vaults built around sync and team sharing. Gupt is the opposite — purpose-built for dev workflows where you juggle many test accounts across environments, and where syncing test logins to a cloud is a liability rather than a feature.
No, and that's intentional. Sync requires a server, and a server is a third party that holds your credentials. Use the Export to JSON action to move data to another machine yourself.
Storage uses chrome.storage.local, protected by your browser profile's security model. There is no additional Gupt-specific encryption layer. If your threat model requires that, keep export JSONs in an encrypted volume.
Yes — any Chromium-based browser that supports Manifest V3 extensions. Same install flow.
The entire extension is plain HTML/CSS/JS — no minification, no build step. Every behavior you see is in a file you can read.
A software engineer with a decade of experience, building practical tools for real workflows.
Email: arpit.engghelp@gmail.com
Free up to 5 projects. No account. No card. No sync.