Connections

Connection URIs

The connection string formats Sutido understands — one per engine.

URIs In, URIs Out

Paste a connection string into the Import URI field of the connection form and Sutido fills in host, port, credentials and database for you. The Export URI field shows any saved connection as a string you can share.

MongoDB

mongodb://[username:password@]host[:port][/database][?options]
mongodb://user:pass@localhost:27017/shop
mongodb://user:pass@host1:27017,host2:27017/shop?replicaSet=rs0

Atlas and other DNS-seed-list deployments use the SRV form — TLS is implied:

mongodb+srv://user:pass@cluster0.abc123.mongodb.net/shop

PostgreSQL

postgresql://[username:password@]host[:port][/database]
postgresql://app:secret@localhost:5432/warehouse

Microsoft SQL Server

mssql://[username:password@]host[:port][/database]
mssql://sa:Secret1!@localhost:1433/warehouse

For Windows authentication, leave the credentials out of the URI and pick Windows auth in the connection form instead.

Aerospike

aerospike://host[:port]
aerospike://localhost:3000

ClickHouse

clickhouse://[username:password@]host[:port][/database]
clickhouse://reader:secret@localhost:8123/analytics

Elasticsearch

http://[username:password@]host[:port]
http://elastic:secret@localhost:9200

No invented elasticsearch:// scheme — this is the URL you would paste into a browser. https:// is refused rather than quietly downgraded: a connection cannot carry a TLS scheme yet, and accepting one would send the password above in the clear.

Special Characters in Passwords

If your password contains URI-reserved characters (@, :, /, ?, #), URL-encode them in the string — p@ss becomes p%40ss — or skip the URI entirely and type the password into the form field, where no encoding is needed.

Tip: Exported URIs are for sharing connection settings — your stored passwords stay in Sutido's encrypted secret store and are never written into exported strings unless you put them there.

Next Steps

Server behind a bastion host? Set up SSH tunneling.