The local-first developer workspace.
80+ developer tools. API client. SQL. MongoDB. Redis.
Runs on your machine. No account. No server.
Developers shouldn't need a browser full of random utility websites, a separate API client, a database GUI, a JWT debugger, a JSON formatter, a regex tester, and a dozen other applications just to get through a normal engineering day.
MyDevTools brings those workflows together β as an application that runs on your computer.
It is a developer-focused toolkit built around one principle:
Your data never leaves your machine.
From formatting JSON to debugging APIs, inspecting JWTs, working with SQL/MongoDB/Redis, generating developer artifacts, testing regular expressions, and handling security utilities β MyDevTools is the toolbox that stays with the developer, and only with the developer.
π mydevtools.tech
JSON YAML SQL GraphQL Markdown CSV Regex Diff
- JSON Formatter & Visualizer
- JSON Schema Generator
- JSON to Code
- SQL Formatter
- GraphQL Formatter
- YAML Formatter
- Markdown Preview
- JSON / CSV / Excel conversion
- Diff & JSON Diff
- JSONPath Playground
- Regex Tester
REST HTTP WebSocket DNS cURL
- API Client
- cURL to Code
- Webhook Tester
- WebSocket Tester
- HTTP Status Codes
- DNS Lookup
- URL Parser
- IP / Subnet Calculator
- User-Agent Parser
- MIME Type Lookup
AES JWT HMAC Hashing TOTP PEM
- JWT Decoder
- Hash Generator
- HMAC Generator
- Encryption Playground
- Password Manager
- Bcrypt Generator & Checker
- TOTP / 2FA Generator
- Certificate / PEM Decoder
- SSH / RSA Key Generator
- Secret / API Key Generator
SQL MongoDB Redis S3 Docker
- SQL Client
- MongoDB / NoSQL Client
- Redis Client
- Database Explorer
- S3 / object-storage workflows
- Docker Compose Generator
These connect directly from your machine to your databases and buckets. Connection strings, credentials, and query results are never proxied through a MyDevTools server β because there isn't one.
UUID Base64 Cron Mock Data Images CSS
- UUID / ULID Generator
- Base64 Encoder / Decoder
- Timestamp Converter
- Unit Converter
- Mock Data Generator
- Cron Builder
.gitignoreGenerator- Markdown Table Generator
- Image Compressor
- SVG Optimizer
- Favicon Generator
- Code Screenshot
- CSS Generators
And more.
MyDevTools is not a cloud developer SaaS, and it is not trying to become one.
We removed the backend on purpose. There is no application server, no hosted database, and no account system. Privacy and speed stop being policies you have to trust and become properties of the architecture.
Every transformation happens on your machine. Not "usually." Not "for most tools."
βββββββββββββββββββββββββ
β Developer β
βββββββββββββ¬ββββββββββββ
β
βΌ
βββββββββββββββββββββββββ
β MyDevTools (desktop) β
β β
β Tools + Processing β
β + Local Storage β
βββββββββββββ¬ββββββββββββ
β
βΌ
βββββββββββββββββββββββββ
β Local Result β
βββββββββββββββββββββββββ
No round trip. No upload. No "we don't log your data" promise you have to take on faith.
Your workspace β tabs, snippets, saved requests, connection profiles, history, preferences β lives in a local data directory on your own filesystem.
That means you can work with sensitive:
- source code
- API payloads
- credentials
- tokens
- certificates
- database queries
- configuration
- generated data
without any of it touching infrastructure we control.
MyDevTools makes network requests in exactly three cases:
- You told it to β an API call in the API client, a DNS lookup, a database connection.
- Update checks β a version check against our release feed. Disableable.
- License validation β a one-time activation call. Disableable after activation.
No analytics. No telemetry. No crash reporting that ships your payloads somewhere.
Cloud sync exists as an opt-in add-on for developers who want their workspace on multiple machines. It is off unless you turn it on, it is not required for any tool to function, and the app is fully usable having never seen a network.
The project is built in the open so developers can inspect the implementation, verify the privacy claims above rather than believe them, contribute improvements, and build from source.
MyDevTools is a desktop application built with a web frontend and a native shell. The stack is deliberately small β fewer moving parts means fewer places for your data to go.
|
|
|
|
MyDevTools
β
ββββββββββββ΄βββββββββββ
β β
βΌ βΌ
Application Desktop Shell
β β
TypeScript Tauri / Rust
React / Next.js Native APIs
β β
ββββββββββββ¬βββββββββββ
β
βΌ
Local Data Directory
β
ββββββββββββ΄βββββββββββ
βΌ βΌ
SQLite OS Keychain
(workspace) (secrets)
ββ no server involved ββ
There is no
backend/service to deploy, scale, monitor, or breach. That is the point.
The most important architectural decision was deleting the server.
βββββββββββββββββββββββ
β MyDevTools UI β
ββββββββββββ¬βββββββββββ
β
ββββββββββββββββΌβββββββββββββββ
β β β
βΌ βΌ βΌ
Local Tools API Tools DB Tools
β β β
βΌ βΌ βΌ
In-process Your target Your database
computation endpoint (direct)
β β β
ββββββββββββββββΌβββββββββββββββ
β
βΌ
Local Data Directory
A JSON formatter doesn't need a backend.
A JWT decoder doesn't need a backend.
A regex tester doesn't need a backend.
A hash generator doesn't need a backend.
A developer should never have to upload sensitive data to a stranger's server simply because the tool they need happened to be hosted on the web.
| Speed | No network latency on any transformation. Operations are instant. |
| Offline | Works on a plane, in a SCIF, on an air-gapped machine. |
| Privacy | Nothing to intercept, log, subpoena, or leak. |
| Longevity | No shutdown risk. If we vanish tomorrow, your copy keeps working. |
| Compliance | Easier to clear with security teams β there's no data processor to review. |
Security-sensitive developer tooling deserves a different threat model.
We design around:
The strongest guarantee isn't encrypting data in transit. It's not transmitting it at all.
No server means no API to exploit, no database to dump, no session store to hijack, and no shared multi-tenant blast radius.
Credentials and connection strings go to the platform keychain (Keychain / Credential Manager / Secret Service), not to a config file in plaintext and never to us.
The easiest workflow should also be the safe workflow. Sync off, telemetry absent, local-only unless you say otherwise.
Developers should be able to understand where their data goes and why. Here the answer is short: nowhere.
Open source makes security review possible. Every claim in this README is checkable against the source.
Dependencies, build infrastructure, and release signing are treated as part of the application's attack surface β for a distributed binary, the pipeline is the threat model.
We treat MyDevTools as an engineering product, not a collection of utilities.
Commit
β
βΌ
Pull Request
β
βββ Lint
βββ Type checks
βββ Tests
βββ Dependency audit
βββ Cross-platform build
β
βΌ
Review
β
βΌ
Tagged Release
β
βββ macOS (signed + notarized)
βββ Windows (Coming Soon)
βββ Linux (Coming Soon)
Security and dependency checks fail closed rather than silently producing false-clean results.
Releases are published as signed, versioned artifacts on GitHub Releases. Builds are reproducible from source, so you can verify what you're running.
Because there is no production service, "operations" means shipping a binary that doesn't break:
- crash-safe local storage with migrations
- graceful degradation when offline
- opt-in diagnostics that stay on disk
- no forced auto-updates
Repositories are organized around clear responsibilities rather than one giant application.
mydevtools/
β
βββ app/
β βββ UI + tool surfaces
β βββ workspace state
β βββ local persistence
β
βββ shell/
β βββ native integration
β βββ filesystem + keychain
β βββ network + DB drivers
β
βββ tools/
β βββ formatters
β βββ generators
β βββ security utilities
β βββ API utilities
β βββ developer helpers
β
βββ build/
β βββ packaging
β βββ signing
β βββ CI/CD
β
βββ web/
β βββ static marketing + docs site
β
βββ docs/
βββ architecture
βββ development
βββ security
The exact repository boundaries may evolve as the platform grows.
We optimize for a short path from idea β implementation β useful tool.
A new utility should ideally be:
- Easy to understand
- Easy to test
- Runnable without a network
- Independent where possible
- Reusable
- Fast
- Consistent with the rest of the platform
We prefer composable primitives over tightly coupled features. If a tool needs a server to work, it probably doesn't belong here.
MyDevTools is released under AGPL-3.0.
We believe developer infrastructure should be inspectable and extensible.
Contributions are welcome across:
- π§° New developer tools
- β‘ Performance
- π¨ UI/UX
- π Security
- π§ͺ Testing
- ποΈ Architecture
- π¦ Packaging & distribution
- π Documentation
- βΏ Accessibility
- π οΈ Developer experience
A good contribution doesn't just add code β it improves the developer experience.
Before opening a PR:
git clone <repository>
cd <repository>
# install dependencies
# run the desktop app in development mode
# run tests
# verify lint/type checksPlease check the individual repository's README.md, contribution guidelines, and development scripts for the exact commands.
MyDevTools is evolving toward a broader developer operating workspace.
The long-term idea is not:
"Put 100 random tools on one website."
It is:
Build the local toolbox developers wish their operating system shipped with.
That means deeper workflows around:
Developer
β
βββ Code
βββ APIs
βββ Databases
βββ Security
βββ Infrastructure
βββ Data
βββ Productivity
β
βΌ
MyDevTools
β
βΌ
One local workspace
The number of tools matters less than how much context switching we eliminate.
| Traditional workflow | MyDevTools |
|---|---|
| Many browser tabs | One application |
| Separate utilities | Unified toolkit |
| Copy/paste between sites | Connected workflows |
| Paste secrets into a stranger's website | Everything stays local |
| Data uploaded to process | Data never leaves the machine |
| Account required | No account, no login |
| Breaks without internet | Fully offline |
| Vendor shutdown risk | Your copy keeps working |
| Closed tooling | Open source |
| Subscription treadmill | Own it |
If MyDevTools saves you time:
β Star the repositories
π Report bugs
π‘ Propose tools
π Report security issues responsibly
π§ Submit pull requests
π Improve documentation
π£ Share the project
Every contribution helps turn MyDevTools into a better open-source developer platform.
π Website: https://mydevtools.tech
π§° Developer Toolkit: https://mydevtools.tech/tools
π Documentation: https://mydevtools.tech/help
π Security: https://mydevtools.tech/security
MyDevTools
Built for developers who want fewer tabs, faster workflows, and full control of their data.
Open source Β· Local-first Β· Offline Β· No backend