Qrulla Docs

Get started

Connections

Create, organize and share your connections; encrypt traffic with TLS or reach private servers through an SSH tunnel.

Create a connection

Click “New connection” in the tree (or “File → New connection…”), pick the engine and fill in:

FieldWhat it's for
NameHow you see it in the tree, for example “Sales production”.
Host and PortThe server's address. The port is filled with the engine's usual one.
User and PasswordThe database credentials.
DatabaseOptional: the database opened by default.
GroupOptional: groups connections in the tree.
EnvironmentLocal, Development, Staging or Production. Production turns on extra protections.

Click “Test connection” to check the details, then “Save”.

What each engine needs

  • SQLite: you pick a .db or .sqlite file that already exists. Qrulla doesn't create new files on its own.
  • Oracle: besides the server, the “Service” (for example FREEPDB1 or ORCLPDB1) and “Connect as”: Normal, SYSDBA, SYSASM (to manage ASM) or SYSOPER. It needs Oracle Instant Client.
  • MongoDB: the user is checked against the admin database. The database you pick is the one the editor opens; the tree shows them all.
  • Redis: the database is a number (0 to 15 by default). The user is only needed if the server uses ACLs; otherwise the password is enough.

Passwords

With “Save the password in the system keyring” checked, the password goes to your system's keyring (macOS Keychain, Windows Credential Manager or Linux's Secret Service), never to a text file. Unchecked, Qrulla asks for it each time you connect and doesn't keep it.

Scheduled backups need the saved password to connect on their own.

SSL / TLS encryption

In the “SSL” tab you pick the mode:

ModeWhat it does
DisabledNo encryption.
If the server offers itEncrypts when the server allows it.
RequiredRequires encryption, without checking the certificate.
Required, verify the CARequires encryption and a certificate signed by a trusted CA.
Required, verify CA and host nameThe above, and the certificate must be that server's. The safest.

If the server uses its own CA or asks for a client certificate, load the CA's, the client's and its key under “Certificates”.

Through an SSH tunnel, “verify CA and host name” fails because the connection reaches 127.0.0.1: use “verify the CA”.

SSH tunnel

For servers that can only be reached from another machine (a bastion), open the “SSH” tab and check “Connect through an SSH tunnel”. Type the SSH server and user and pick how to sign in: password or private key (with its passphrase if it's encrypted).

The first time, Qrulla shows you the SSH server fingerprint. Compare it with the server's before trusting it; on the server you see it with:

ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub

If the fingerprint changes later, Qrulla doesn't connect and warns you: the server may have been reinstalled, or someone may be intercepting the connection. Check with whoever runs it before clicking “Trust the new fingerprint”.

Organize

  • Groups: “File → New group…”, or drag a connection onto a group. Each group has its color.
  • Color: right-click the connection → “Color”. It helps tell production apart at a glance.
  • Duplicate: right-click → “Duplicate connection”, handy for the same server with another user.
  • Delete: removes the connection and its saved password. Your databases aren't touched.

Take your connections to another computer

“File → Export connections…” saves the ones you pick, with their groups, to a file. If you check “Include the saved passwords, encrypted”, type a key of at least 8 characters: the passwords travel encrypted with it.

On the other computer, “File → Import connections…”. They're added to the ones you have; none is changed or deleted, and a name that already exists comes in with a number, like “Sales (2)”. If you forgot the key, you can import them without passwords.

SSL certificates and SSH keys don't travel in the file, only their path: copy them separately.

Something missing or unclear? Write to support@qrulla.com.