SFTP and MySQL in One Desktop Client

Maintaining a website often means opening three disconnected tools: a transfer client for files, a terminal for commands and a database application for data. Each tool stores another copy of the host, username, key or password. Each switch also makes it easier to act on the wrong customer or environment.

Naucturne takes a site-centred approach. The same encrypted connection inventory can open remote files, an SSH shell and the databases associated with that server. It does not make SFTP and MySQL the same protocol; it keeps them in one operational context.

What “SFTP and MySQL in one client” actually means

The benefit is not merely fewer windows. A labelled site groups the technical context needed for one intervention. Teams can organise hundreds of connections into folders and shared vaults instead of rebuilding the same inventory in each utility.

Three ways to reach MySQL and MariaDB

1. Direct connection

Use a direct connection when the database service is deliberately reachable from the operator’s network. Naucturne connects with the configured host, port, username and database.

Direct exposure should not be created only for convenience. Restrict the network path, use a dedicated account and grant only the privileges required for the job.

2. SSH tunnel

An SSH tunnel is appropriate when MySQL listens on localhost or a private network behind an SSH server. Naucturne uses the SSH path to carry the database connection without publishing the database port to the internet.

This is a common VPS and dedicated-server configuration: the same server access used for SFTP can provide the tunnel, while the database remains private.

3. Temporary PHP gateway

Shared hosting creates a different constraint. The host may offer FTP or FTPS and phpMyAdmin but no SSH access and no remotely reachable MySQL port. A normal desktop SQL client cannot connect.

For compatible PHP hosting, Naucturne can upload a small gateway with a random filename and secret token. Requests run against MySQL locally on the hosting server and return structured results. The gateway is removed when the connection closes.

A typical website maintenance workflow

1. Open the site

   Select the customer or project from the personal or team vault. The server profile supplies the transfer and SSH context.

2. Inspect the files

   Browse local and remote folders side by side, download the file to change, or edit it through the Monaco-based remote editor.

3. Check the database

   Open the linked MySQL or MariaDB profile, browse the schema and run a targeted SQL query without recreating the site in another application.

4. Apply and verify

   Upload the file, inspect the affected rows and use the terminal or DNS view if the change requires another server operation.

The database workspace supports database and table browsing, column and index inspection, paginated data, a Monaco SQL editor, inline row editing and SQL export. These capabilities cover routine development and support work without claiming to replace every specialist DBA feature.

One workspace does not mean one unrestricted credential

Convenience should not flatten security boundaries. A web account, SSH account and database account can remain distinct. Naucturne stores connection records in an AES-256-GCM encrypted vault derived from the user’s master password. Team access uses a team key sealed individually for authorised members.

Permissions can also separate capabilities by member. Someone may need file access without database or DNS access. The security architecture and team permissions describe those controls in detail.

SSH host fingerprints still need verification. Database accounts still need least privilege. A desktop client cannot compensate for a public root account, weak hosting permissions or an unpatched endpoint.

Who this workflow is for

This combined workspace fits:

• agencies maintaining many customer websites;
• developers working across files, SQL and SSH during the same task;
• support teams that need a shared, organised connection inventory;
• shared-hosting users who cannot connect a traditional SQL client;
• operators who want fewer plaintext credential copies across desktop tools.

Choose separate specialist tools when advanced database modelling, performance profiling, replication administration or infrastructure-as-code automation is the primary job. Use CI/CD rather than manual uploads for repeatable deployments.

Limitations to understand

The integrated database client supports MySQL, MariaDB and PostgreSQL. PHP gateway mode remains for MySQL/MariaDB on compatible PHP hosting and should stay temporary. Naucturne is a desktop operations client, not a database server, managed transfer service or privileged-access-management platform.

For the transfer side alone, compare the best SFTP clients by workflow. For the wider consolidation case, see how to replace FileZilla, phpMyAdmin and a DNS panel.

Product references

• Dual-pane SFTP, FTP and FTPS transfers
• MySQL and MariaDB access modes
• DNS and outbound email management
• End-to-end encrypted vault

The practical value is continuity: start with the remote file, move to the query or shell command, and finish the intervention without losing which server, customer or environment you are operating on.