Desktop UI
Investigate directly
Send a request, open a terminal, or query the database yourself. Return to the saved project setup when you need it again.
Start with a workspaceLocal-first · Backend / DevOps
From a failed API request to a verified fix.
Unfour combines API testing, SSH, and database queries in one local-first desktop workspace. Flow saves repeatable checks as local runbooks.
Connect Codex or Cursor through MCP to investigate and check fixes with the same saved resources.
Core tools free · No subscription required Apache-2.0 source Free vs Pro
Shared project context
Keep one project context for you and your coding agent.
Save requests, SSH and database connections, and environment variables around the same backend. Use them directly or through MCP; Flow runbooks reuse these resources for repeated troubleshooting and operational checks.
MCP connection
Bring your coding agent into the investigation
Connect Codex or Cursor to reuse saved requests, connections, and environments. Workspace MCP policies govern the tools it can call.
Connect Codex or CursorAvailable · Free core
Move your whole workspace, not just API requests.
Bring API definitions, SSH/DB connection settings, environments and variables, Saved SQL, SSH Tasks, and Flow definitions together. Spend less time rebuilding your project setup.
Share definitions or keep a password-encrypted local backup with optional saved credentials. Preview imports into an independent workspace; your existing workspaces stay intact.
Read the workspace export and backup guideOne troubleshooting workflow
Follow the evidence from a failed request to a fix.
API request → SSH logs → Database state → fix/verify. You choose the evidence and the fix; Unfour keeps the investigation in the same project context.
-
Reproduce
Send the failing API request and inspect its response.
-
Inspect logs
Check SSH/server logs around the same time window.
-
Check data
Query the database records tied to the request.
-
Fix / verify
Review the evidence, make a fix, then repeat the request and relevant checks.
See it in action
Watch a backend investigation in Unfour.
See the requests, server logs, and database queries used to investigate one bug and check the fix.
Investigate once. Keep the checks you reuse.
API, SSH, and Database support the investigation. Flow turns known steps into a local runbook.
01
API Client
Send and save API requests, use environment variables, and inspect response bodies, headers, and timing.
Explore API Client02
SSH Terminal
Open terminal sessions, inspect server logs, transfer files over SFTP, and run reusable SSH tasks.
Explore SSH Terminal03
Database Explorer
Manage database connections, browse schemas and table rows, and run SQL to inspect the data behind a request.
Explore Database Explorer04
Flow
Save repeatable API, SSH Task, and SQL steps as a user-defined local runbook. Flow V1 does not use Cloud Sync.
Explore FlowFrom code changes to backend checks
Let Codex and Cursor investigate your running backend.
Codex and Cursor use Unfour’s local MCP server to inspect API responses, SSH logs, and database state with your saved connections. Their own coding tools apply reviewed changes; Unfour supplies the runtime checks.
Explore MCP capabilities and safetyBefore a change: gather evidence from requests, server diagnostics, and queries.
After a change: re-run the failing request and relevant checks against the selected environment.
Through Flow: manage and execute the same local runbooks and inspect their run history.
You choose the workspace and MCP policy; those policies control available tools and risky actions.
Local-first
Your workspace starts on your device.
Your workspace is stored locally. Pro adds optional Cloud Sync for supported data, enabled per workspace. SSH and database credentials stay device-local; Flow V1 definitions and run history are excluded from sync.
✓ Local desktop app
✓ Device-local SSH and database credentials
✓ Saved project context
✓ Optional per-workspace Cloud Sync
Open source
Free core. Open code.
The core desktop tools are open source under Apache-2.0. Inspect the code on GitHub, see what has shipped, and review how Unfour handles data and permissions.
Before you download
Using Unfour on your own, with an agent, or across devices.
What is Unfour?
Unfour is a local-first workspace for Backend and DevOps developers. Its API client, SSH terminal, and database client share project context for tracing a failed request through logs and data to a verified fix. MCP connects Codex and Cursor; Flow saves repeatable checks as local runbooks.
How is Unfour different from using Postman, a database client and an SSH client separately?
Unfour keeps saved requests, SSH and database connections, and environments in one project workspace. You can follow API → logs → database without rebuilding context across separate apps, and MCP clients can use the same resources. It does not claim every specialized feature of those tools.
Can Codex or Cursor use my Unfour connections?
Yes. Unfour’s local stdio MCP server exposes approved workspace resources to Codex and Cursor under workspace policy. Flow tools also manage and execute the same local runbooks. Review the target and tool output; access does not grant automatic root-cause detection.
What is Unfour Flow?
Unfour Flow is the fourth core module: a user-defined local developer runbook combining API requests, SSH Tasks, and Database queries with Condition, Wait Until, and run history. It is not a general workflow or agent platform.
Is Flow cloud synced?
No. Flow V1 definitions and run history stay local and are excluded from Cloud Sync, including with Pro. Flow belongs to the free core; Pro still adds only Cloud Sync for supported workspace data.
Which databases does Unfour support?
Unfour supports SQLite, PostgreSQL, and MySQL; compatible MariaDB servers use the MySQL connection path. openGauss uses PostgreSQL-protocol connections with table browsing and structure/data export support.
Is Unfour local-first?
Yes. The desktop workspace is stored locally and core tools do not require a subscription. Remote API, SSH, and database operations still use the network. Optional Pro sync covers supported workspace data; Flow V1 definitions and run history remain local-only.
Do I need a coding agent to use Unfour?
No. API testing, SSH / SFTP, database browsing, and SQL work directly in the desktop UI. MCP is optional and lets a compatible coding agent use supported tools with the same saved workspace resources.
Can I use Unfour without a subscription?
Yes. API Client, SSH / SFTP, database tools, Flow, MCP, and local workspaces are free and open source. A subscription is only needed for Pro Cloud Sync.
What does Pro add?
Pro currently adds Cloud Sync for supported workspace data across your devices. Upgrade and sign in to the same Unfour app to enable it. Core tools remain free.
How much of troubleshooting is automated?
You define the investigation and expected results. Flow runbooks repeat the steps you save; MCP calls remain subject to workspace policy and required confirmations. Unfour does not automatically correlate requests, logs, and rows or find and fix the root cause on its own.
Which platforms can I download?
Windows x64 and Apple Silicon or Intel Macs. Linux x64 AppImage is also downloadable but remains Experimental. The standalone Windows installer is unsigned; macOS packages are unsigned and not notarized. The Download page includes installation notes.
Try your next investigation in Unfour.
Start with one request and the connections you need. Add your coding agent when it helps. Core tools and MCP are free.
Download Free