We've been thinking about password security for years. Like most people, we know we should use unique passwords everywhere. We know we should change compromised ones immediately. We know that reusing passwords is dangerous.
And like most people, we've accumulated years of technical debt in our password vaults.
The numbers are sobering: 80% of hacking-related breaches involve weak or stolen passwords (IBM Security Report, 2024), and 85% of people reuse passwords across multiple sites (Bitwarden, 2024). The average person spends nearly 11 hours per year just entering and resetting passwords (Ponemon Institute).
Today, we're launching Dosel—an AI-powered desktop application for macOS that automatically changes your passwords across hundreds of websites while keeping your credentials 100% local on your device.
Who this is actually for
If you're already using a password manager with unique, randomly-generated passwords for every site, and none of them have appeared in breaches—congratulations, you're in great shape. Modern security guidance says routine password rotation isn't necessary for strong, uncompromised credentials.
But that's not most people's reality.
This tool is for people who:
Have years of password reuse from before they started using a password manager properly
Have passwords that appeared in breaches and need to be changed across multiple sites
Have 100+ accounts with the same or similar passwords that would take hours to fix manually
Keep putting off the tedious work of cleaning up their password hygiene
If you're in the Bitwarden subreddit already using unique passwords everywhere—great, you're ahead of most people. But many of us have a backlog of old accounts from 2015 that still use MyDog2019! on a dozen different sites.
How it actually works (being honest about the AI)
We want to be transparent about the architecture, because we've seen confusion about what "local" means.
What stays on your device
Your actual passwords - The text strings of your credentials are never sent anywhere
The password manager CSV - Imported locally, processed locally, deleted after use
The browser automation - Playwright runs locally on your machine
What goes to the cloud
- Screenshots and DOM data - The AI needs to see what's on screen to navigate. This data is sent to OpenRouter (which routes to Gemini 2.5 Flash) so the AI can decide where to click next.
This is an important distinction. The AI sees your screen to navigate—it can see that you're on Netflix's password change page, it can see the form fields, it can see button labels. But it never sees the actual password values.
Here's how that works technically:
# AI receives screenshot/DOM and decides actions
AI: "I see a password field. Call enter_password() to fill it."
# Local engine handles the actual credential
Local: inject_credential("YourActualPassword123") # Never sent to AI
The AI calls a function, but the function's parameter (your password) is filled in locally. It's like giving someone directions to a safe but not the combination.
Is this perfectly private? No. The AI service can see your browsing activity during the password change. But your actual credentials—the thing that would let someone log in as you—never leave your machine.
The CSV import concern
Several people have asked: "Isn't uploading a plain text CSV risky?"
Here's the thing: that CSV never leaves your computer. You export it from Bitwarden/1Password/whatever, the app reads it locally, uses it to fill in forms, and then you delete it. At no point is the file uploaded anywhere.
Is having your passwords in a plain text file on your desktop ideal? No. But it's the same file you'd have if you exported from your password manager for any other reason. The app just automates what you'd do manually: open the file, read a password, type it into a website, repeat.
Getting started: low-stakes first
When you first use the app, start with low-stakes accounts—streaming services, shopping sites, forums, social media. Get comfortable with how the automation works before moving to sensitive accounts.
Once you've seen the app successfully change passwords on 10-20 accounts and you trust the process, then consider running it on more important accounts like email or financial services.
For your most critical accounts (banking, healthcare, primary email), some people prefer to do those manually even after using the app for everything else—and that's totally reasonable.
The goal is to clean up the bulk of your password debt efficiently. At 2-3 minutes per site manually (find settings → security → change password → generate new → save to password manager → verify), 200 accounts would take 6-10 hours. The automation handles that tedious work so you can focus your attention on the accounts that matter most.
What about deleting old accounts instead?
This is actually great advice we saw in feedback. If you have stale accounts you don't use anymore, delete them rather than updating the password. Less attack surface is better than a stronger password on an account you'll never use.
Dosel is for accounts you want to keep but need to secure.
The technical stack
For those curious:
Frontend: Electron (TypeScript + React)
Backend: Python with Playwright for browser automation
AI: Gemini 2.5 Flash via OpenRouter
Security: Secure credential injection, memory clearing, comprehensive log redaction
Pricing
There's a free tier. You can change up to 5 passwords per month at no cost—enough to try the app and see how it works for you. No credit card required.
If you have a larger backlog, paid plans start at $2.99/month for unlimited password changes. Most people won't clean up all 200 passwords in one sitting anyway. They'll do 20, then come back next week, then find more breached passwords in a few months. The subscription supports ongoing development and gives you flexibility to use it when you need it.
Try it yourself
If you're someone with a backlog of password debt—old reused passwords, credentials that showed up in breach notifications, accounts you've been meaning to secure "someday"—the free tier lets you change 5 passwords per month to see how it works.
Frequently asked questions
Does Dosel store my passwords?
No. Dosel does not store, sync, or transmit your passwords to any server. Your credentials exist only in memory during the password change process and are cleared immediately after. The app works alongside your existing password manager (1Password, Bitwarden, LastPass, etc.)—it's not a replacement.
How does the AI change passwords without seeing them?
The AI receives screenshots and DOM data to navigate websites, but passwords are injected locally through a separate secure channel. When the AI identifies a password field, it calls a function like enter_password(). The actual password value is filled in by the local engine on your Mac, never sent to the AI service.
What password managers does it work with?
Dosel works with any password manager that can export to CSV format, including:
1Password
Bitwarden
LastPass
Dashlane
Keeper
NordPass
Google Password Manager
Apple Passwords (iCloud Keychain)
And many more
Is Dosel available for Windows or Linux?
Currently, Dosel is available exclusively for macOS. Windows and Linux versions may be considered in the future based on demand.
What happens if the AI gets stuck on a website?
The app includes automatic error handling and will skip sites it can't process. You can also watch the browser in real-time (visible mode) and stop the process at any time. Failed password changes are logged so you can handle them manually.
How much does Dosel cost?
Free tier: 5 password changes per month, 1 device, no credit card required
Monthly: $2.99/month for unlimited password changes
Annual: $27.99/year (save 22%)
Is it safe to export my passwords to a CSV file?
The CSV export is a standard feature in all major password managers. The file stays on your local computer—it's never uploaded anywhere. After importing, you can delete the CSV file. This is the same process you'd use to migrate between password managers.
Isn't password rotation outdated advice?
You're right—for strong, unique, uncompromised passwords. Modern security guidance says routine rotation isn't necessary for secure credentials. This tool is specifically for cleaning up weak, reused, or compromised passwords, not for routine rotation of already-secure ones.
Could the AI learn my passwords?
No. The AI never receives your password text. It receives screenshots and DOM data to navigate websites, then calls a function like enter_password(). The local engine fills in the actual password value. Even if OpenRouter logged every request (they don't, but hypothetically), they'd see enter_password() was called, not what was entered.
Does this violate security best practices?
Dosel follows several security best practices: credentials are never transmitted to third parties, passwords are cleared from memory after use, and there's no persistent storage of sensitive data. The AI sees your screen to navigate but never sees the actual password values.
Why isn't Dosel open source?
Fair question. The core automation logic and security model could be audited if open sourced. This is something we're considering for the future.
Download Dosel → — 5 free automated password changes per month, no credit card required.
Have questions or concerns we didn't address? We want to hear them. Email us at hello@dosel.app.