As a software engineer, my daily workflow always felt fragmented.
In any given hour of building a feature, I was constantly context-switching between:
- An HTTP client to test REST endpoints and verify response headers.
- A database GUI to inspect database tables and run quick SQL/NoSQL queries.
- Multiple terminal tabs and
.envfiles to manage API keys and credentials.
I wanted a single, lightweight tool that brings these three daily essentials together in one clean, offline-first workspace with zero telemetry.
So I built Bapu Studio.
π What is Bapu Studio?
Bapu Studio is a free, open-source developer desktop application designed to streamline daily engineering workflows:
1. π API Studio
- Full HTTP/REST client supporting all methods (GET, POST, PUT, DELETE, etc.).
- Dynamic variable interpolation (
{{API_URL}},{{AUTH_TOKEN}}). - Pre-request and test assertion scripting engines.
- Instant code snippet generation in cURL, JavaScript
fetch, Pythonrequests, and Go.
2. ποΈ Database Studio
- Multi-engine SQL & NoSQL query console: PostgreSQL, MySQL, MongoDB, and SQLite.
- Schema browser with dynamic table column extraction.
- One-click CSV exports and query history auditing.
3. π Scoped Secrets Matrix
- Manage environment variables (
Local Dev,Staging,Production) with secret masking. - Export seamlessly to standard
.envformats.
4. π 100% Local & Privacy-First
- Operates completely offline on your local machine.
- No mandatory accounts, no cloud sync required, no tracking.
π¦ Try It Out
Bapu Studio is 100% free and open-source under the GNU AGPLv3 license.
Pre-built binaries are available for macOS (Apple Notarized), Windows, and Linux:
- π GitHub Repository: github.com/joravar/bapu-studio
- π₯ Download Releases: github.com/joravar/bapu-studio/releases
I'd love to hear your feedback, feature ideas, or thoughts from fellow developers! β
Top comments (1)
Local-first is a good fit for this category, especially when secrets and database access are involved. The hard part is usually not building one cockpit, but making every boundary legible: which data stays local, which integrations can call out, and what gets written to disk. That trust layer is the product.