Sign In Download Free
Getting Started

First Connection

Connect Sutido to your first database — any of the five supported engines.

Creating a Connection

Open the Connection Manager (the gear button above the sidebar, or the + on the Welcome tab) and click New Connection. Pick your engine first — MongoDB, PostgreSQL, SQL Server, Aerospike, ClickHouse or Elasticsearch — and the form adapts to what that engine needs.

The fast way: paste a URI

If you already have a connection string, paste it into the Import URI field and the form fills itself in. Sutido understands all five schemes: 

mongodb://user:pass@localhost:27017/mydb
mongodb+srv://user:pass@cluster0.abc.mongodb.net/mydb
postgresql://user:pass@localhost:5432/mydb
mssql://sa:pass@localhost:1433/mydb
aerospike://localhost:3000
clickhouse://user:pass@localhost:8123/mydb

See Connection URIs for the full reference.

The manual way

  1. Give the connection a name — it appears in the sidebar
  2. Enter host and port (defaults: MongoDB 27017, PostgreSQL 5432, SQL Server 1433, Aerospike 3000, ClickHouse 8123, Elasticsearch 9200)
  3. Fill in credentials if your server requires them — see Authentication & Secrets for the per-engine options
  4. Optionally set a default database

Test before you save

Click Test connection to verify Sutido can reach the server with the settings you entered. If the test fails, the error message tells you whether it's a network problem, an authentication problem, or a TLS problem.

Engine-specific options

  • MongoDB: replica set support with multi-host lists, replica set name, and read preference (primary, secondary, nearest, and friends). Legacy servers 3.6 and 4.0 work out of the box — Sutido ships a dual driver and negotiates automatically.
  • SQL Server: SQL logins or Windows authentication, plus configurable encryption and trust-server-certificate options.
  • Aerospike: optional username/password; the sidebar browses namespaces and sets.
  • ClickHouse: talks native SQL over HTTP; user/password as configured on your server.

Which one is production

On the form's front page, three things say what kind of place a connection is:

  • Environment — development, staging or production. Shown as a badge on the sidebar row and beside the shell's Ready line. On a production connection, any run that is not provably a read asks first — the same dialog a destructive statement gets, headed for what it is.
  • Colour — one of eight, as a bar on the sidebar row and under the tab. A tag picks one until you do: production red, staging amber, development green.
  • Read-only — enforced, not decorative. Only statements Sutido can prove are reads run here, from the shell, the grid and the MCP proxy alike; everything else is refused before it reaches the server.

Connecting

Click a connection in the sidebar to connect. The dot next to the name turns green, a version badge shows the server version, and the tree expands to the databases and objects that engine exposes. Connections group by engine in the sidebar, so a mixed setup stays organized.

Tip: In Settings you can have Sutido reconnect to your last-used connection automatically on launch.

Managing connections

Back in the Connection Manager you can edit, duplicate and delete connections. The Export URI field shows the connection as a shareable string (without touching your stored secrets).

Next Steps

Get to know the interface, or jump straight into the query editor.