ARVICA / DOCUMENTATION
SSH and remote development
Connect only after instance access details are confirmed.
Register a public key
Add an SSH public key in the workspace. Arvica accepts supported Ed25519 keys and RSA keys of at least 2048 bits. Keep the private key on your device; never upload it as a public key.
Use recorded connection details
Open the instance detail page for the confirmed host, port and username. Verify the host fingerprint through a trusted channel. If no host is recorded, the instance is not yet ready for connection; do not invent an address.
Editor and notebook access
Remote editors use the same approved SSH destination. For notebook tools, agree the authentication and network-access method before exposing a service. An SSH tunnel avoids directly publishing a development port when supported by the instance configuration.