Onboarding

Create Your First Connection

Add remote host details, then install the generated public key so SQLitePilot can open the managed tunnel.

Last updated: Dec 8, 2025

Connections tell SQLitePilot where your database lives. When you save a connection, SQLitePilot generates a unique Ed25519 keypair for it and shows the public key you need to install on the server.

What to prepare

  • The server address, SSH username, and the full path to the .db file (for example /var/www/app/data.sqlite).

Step 1: Open the page

  1. Go to Connections.

Step 2: Start a new connection

  1. Select Add new connection.
  2. If you are on the free plan and already have one saved, you will see a blue notice explaining that you must delete the old one or upgrade before continuing.

Step 3: Fill in the details

  1. Name: choose something clear like “Production orders.”
  2. Server IP or hostname: the address you SSH into today.
  3. SSH username: the account that owns the database file (often root, user, or deploy).
  4. Database path: the full path to the SQLite file on the server (for example /home/deploy/apps/orders/db.sqlite or /root/data/analytics.db).
  5. Platform: leave the suggested option unless support told you otherwise.

The Save button becomes active once every field is filled out.

Step 4: Save and check the list

  1. Click Save.
  2. SQLitePilot returns a generated public key for that connection.
  3. Add that key to your server ~/.ssh/authorized_keys file.
  4. Click Test Connection in the setup panel to verify access.
  5. The dialog closes and the new connection appears in the table. Use the actions menu to edit or delete it later.

Step 5: Move to the dashboard

  1. Open the Dashboard.
  2. Select your new connection from the dropdown and click Connect to start browsing tables.

That is all it takes to give SQLitePilot a remote server to work with.