Academy/Connections

SSH & SFTP connections

Connect Paralake.AI to Linux servers and SSH-enabled hosts (beta since 0.1.1): prepare the server, add a connection and confirm the host key, what the agent may do and what it asks, deploy with preview and rollback, staging vs production and backups.

Available Intermediate · 8 min · Version: 0.1.2 · Last verified: 2026-11-16

Prerequisites

  • Paralake.AI installed and signed in.
  • A server or host that offers SSH or SFTP, and a user you are allowed to connect as.
  • Preferably a key pair you created for this purpose (the private key stays on your computer).
  • A tested backup of the server's files and databases.
  1. Beta since version 0.1.1

    Beta. SSH and SFTP connections — browsing, reading and writing files, approved commands and the host key check — are available since version 0.1.1. Deploy, preview and rollback over SSH/SFTP are also in beta.

    No customer production deployment has been verified yet. Try everything on a staging server first, keep your own backups, and report anything unexpected to help@paralake.ai.

  2. What the access types mean

    AccessWhat it isNotes
    SSHAn encrypted remote terminal plus file accessIn Paralake.AI: files and commands
    SFTPFile transfer over SSHIn Paralake.AI: files only, no commands
    FTPSFTP with TLS encryptionNot supported as a Paralake.AI connection; use an FTP client
    FTPUnencrypted file transferAvoid — passwords and files travel in clear text
    Key-based loginYou log in with a key pair; the private key stays on your computerSafer than passwords
  3. Prepare your server

    • Use key-based authentication. Create a dedicated key for Paralake.AI so you can revoke it on its own.
    • Create a separate user with access only to the site or server folders — not root.
    • If you can, disable direct root login and password login once key login works.
    • Note the server's host key fingerprint, for example with the command below on the server, or from your host's control panel.
    • Know your paths (web root, FXServer folder) and how services are restarted.
    ssh-keygen -lf /etc/ssh/ssh_host_ed25519_key.pub
  4. Add the connection

    1. Open Connections in the sidebar and click New connection.
    2. Name — something you recognise, such as Staging web.
    3. Type — SSH (files + commands) or SFTP (files only).
    4. Host, Port (usually 22) and User.
    5. Environment — Development, Staging or Production. Production adds extra warnings and confirmations.
    6. Root folder on the server — the AI never goes outside it. Choose the site or server folder, not /.
    7. Permissions — Read files is always on. Tick Write files (with backup) and, for SSH, Run commands only if you need them.
    8. Sign-in — SSH key (preferred) or Password. Paste the private key or password only into this field of the connection form — never into the chat.
    9. Click Save and test.

    The key or password is stored encrypted on this computer (Windows DPAPI) and is never sent to paralake.ai or the AI model.

  5. Confirm the host key

    The first time you connect, Paralake.AI shows New server – confirm the host key with the server's fingerprint.

    • Compare it with the fingerprint from step 3.
    • Only if it matches, click Trust key and connect. Otherwise click Cancel.

    If you later see WARNING: the host key has changed, the server may have been reinstalled — or someone may be trying to intercept the connection. Only trust the new key if you know why it changed.

    After a successful test, the connection shows its host key, the measured capabilities (read, write, commands) and a Browse button for the files inside the root folder.

  6. What the agent may do, and what it asks

    ActionWhat happens
    List and read files inside the root folderWithout asking
    Write a fileAsks every time. Checks that the file hasn't changed since it was read, makes a backup and verifies the result
    Run a command (SSH with Run commands)Asks every time. Dangerous commands (formatting, raising privileges, shutting down, download-and-run and similar) are blocked and can never be approved
    Deploy or roll backAsks every time and can never be always allowed

    On a Production connection, writes and commands are marked as production on the approval card. Every operation names the connection it applies to, and everything the AI does on the server is recorded in the Security log under Settings.

  7. Deploy, preview and roll back (beta)

    The Deploy button appears when the connection has Write files permission.

    1. Click Deploy.
    2. Enter the local folder in the project (for example web/site) and the folder on the server, relative to the root folder.
    3. Click Preview. You see every new and changed file; unchanged files are skipped.
    4. On a Production connection, type the server's host name to confirm the destination.
    5. Click Deploy … file(s).

    Originals are backed up on the server in .paralake-backups before anything is overwritten, and every file is verified after upload. You get a Deploy ID, and Roll back this deployment restores changed files and removes new ones. .git, node_modules, .env and keys are never included.

    If the agent starts a deployment itself, it shows the destination and the file list on an approval card first.

  8. Staging vs production

    • Staging is a copy of your site or server where you test changes. Nobody depends on it.
    • Production is what your players or customers use.

    Set up a separate Staging connection, deploy there first, check the result, and only then deploy to Production. For FiveM, a separate dev server (different port and database) is your staging. For websites, a subdomain such as staging.example.com with its own database works well.

  9. Backups

    Before any remote work — by you, a colleague or an AI:

    • Take a full backup of files and databases, and confirm you can restore it.
    • Use your host's or server's snapshot/backup feature where available.
    • Keep at least one copy off the server.

    The backups in .paralake-backups only cover files that a deployment overwrote, and Paralake.AI's restore points only cover files on your computer. Neither replaces a full backup of the server.

Security

  • Never paste passwords, private keys, API tokens or panel credentials into the Paralake.AI chat or a support ticket. Keys and passwords go only into the connection form, where they are stored encrypted on your computer.
  • Use a dedicated key and a limited user, not root. Revoke the key on the server if a computer is lost.
  • Only click Trust key and connect when the fingerprint matches the server's.
  • Choose a narrow root folder and only the permissions you need.
  • Deploy is in beta: test on staging first and keep your own backups.

Troubleshooting

Save and test fails

Likely causes: Wrong host, port or user. · The server only accepts keys, or the key isn't in the user's authorized_keys. · The root folder doesn't exist or isn't readable for the user.

  1. Check host, port and user with your provider, and try the same login with your usual SSH or SFTP client.
  2. Check that the public key is installed for that user on the server.
  3. Check the root folder path and its permissions.

Contact support if: The same login works in another SSH/SFTP client but fails in Paralake.AI — include the error text, never the key. Support

WARNING: the host key has changed

Likely causes: The server was reinstalled or moved. · Someone may be trying to intercept the connection.

  1. Click Cancel and ask your provider or server admin whether the key changed.
  2. Only click Trust key and connect after the new fingerprint is confirmed.
There is no Deploy button, or the agent can't write

Likely causes: The connection doesn't have Write files permission. · The user has no write access to the root folder on the server.

  1. Click Edit on the connection and tick Write files (with backup).
  2. Check the measured capabilities after Save and test; fix folder permissions on the server if write shows as unavailable.
Commands can't be run on the server

Likely causes: The connection type is SFTP, which gives file access only. · Run commands isn't ticked. · The command is blocked because it is classed as dangerous.

  1. Use type SSH and tick Run commands if you need commands.
  2. For blocked commands, ask the agent for a safer alternative, or run it yourself after checking it carefully.

Contact support if: An ordinary, harmless command is blocked. Support

A deployment went wrong

Likely causes: Wrong local or server folder. · The site needs a build step or database change that wasn't done.

  1. Click Roll back this deployment (or ask the agent to roll back using the Deploy ID).
  2. Check the folders in Preview before deploying again, and test on staging first.

Contact support if: Roll back fails — include the Deploy ID and the error text. Support

FAQ

Can I sign in with a password?

Yes, Password is an option. An SSH key with a limited user is the safer choice.

Will the agent get root access?

You decide which user it connects as and which root folder it can use. Use a limited user and a narrow folder.

Where is my key stored?

Encrypted on your computer with Windows DPAPI. It is never sent to paralake.ai or the AI model. Deleting the connection removes the saved key from the computer.

Is it safe to deploy to production?

Deploy is in beta, and no customer production deployment has been verified yet. Deploy to staging first, check the result, and keep your own backups.