YOUR PRIVATE DESTINATION
Open your
SoLoAgent.
Enter the HTTPS address of the SoLoAgent companion running beside your Hermes installation.
Your service address
Saved in this browser only. No account or agent data is sent to this hub.
Only enter a service you trust. Sign-in happens on that service, not here.
No service yet? Get the desktop app to run SoLoAgent on this computer, or install it on a server.
NEW HERE? START WITH THE DESKTOP APP · RECOMMENDED
SoLoAgent
on your computer.
The quickest way to start. The app installs Hermes for you, helps you sign in to your AI provider and runs everything on this computer, with voice, camera and screen sharing, a tray menu and secure sign-in storage. No domain, reverse proxy or password needed. It can also pair with your own SoLoAgent server, like the Android app.
ADVANCED · ALWAYS-ON SERVER SETUP WIZARD
Install SoLoAgent
on your Hermes host.
For an always-on service you can reach from anywhere. Choose your host, prepare sign-in and networking, then install a verified download. Test builds are available separately from stable releases. Just want it on this computer? Use the desktop app.
Prepare your setup below. Install commands become available after the selected release download is verified. JavaScript is required to check downloads and generate commands.
Choose your Hermes host and sign-in
Run the companion on the computer or server that runs Hermes Agent, under the same user account.
For a test build, use a separate test account or machine from your private SoLoAgent installation.
First install Hermes Agent, configure your model provider, and verify a normal chat. The companion installer checks the runtime, writable profile, credentials, model endpoint and gateway before installing.
Checking download availability…
Password sign-in needs no cloud account. Existing services can continue using their configured OIDC provider; this installer sets up password sign-in.
✓ Store these credentials in your password manager. You will use them to sign in on your domain.
Connect Your Companion (Domain or No-Domain)
SoLoAgent needs an address to connect to. If you have your own domain, configure it below. If you do not have a domain, choose one of our 100% free zero-domain options!
Enter the full hostname you are pointing to this server (e.g. mc.sololink.cloud).
mc.example.com). Paths, sign-in details, query strings and fragments are not allowed.
💡 Should I enter a subdomain (like mc.sololink.cloud) or root domain?
Most users should use a subdomain (such as mc.sololink.cloud or hermes.yourdomain.com):
- If you enter just
sololink.cloud, your reverse proxy will expect all traffic for your entire root website to route to SoLoAgent. - Using a subdomain like
mc.sololink.cloudkeeps your main website completely separate and unaffected.
| Record Type | Host / Subdomain | Points To (Value) | TTL |
|---|---|---|---|
| A | mc | <Your Server's Public IP> | Auto (or 1 min) |
Point this to where Hermes is hosted: This A-record must point to the public IP address of the machine running Hermes. If running on home Wi-Fi or behind a router, ensure ports 80/443 are forwarded or use Cloudflare Tunnel. Verify DNS before opening your service.
Choose Reverse Proxy
Choose your reverse proxy, then apply its configuration from the Step 3 Proxy Reference tab after installing the companion. Review your existing proxy configuration before reloading it.
Caddy automatically obtains and renews free Let's Encrypt SSL certificates. After installing the companion, apply the separate Caddy configuration shown below and reload Caddy.
View raw Caddyfile syntax
Routes traffic securely through Cloudflare without open firewall ports. After installing the companion, apply the separate tunnel configuration shown below.
View raw tunnel commands
Provide a valid TLS certificate and key for your service domain. Replace the certificate paths in the Step 3 reference, then validate and reload Nginx before opening your HTTPS address.
View raw Nginx server block
Cloudflare provides free on-demand HTTPS tunnels for anyone. Just install cloudflared on your server and run one command. It gives you a public HTTPS URL ending in trycloudflare.com.
Install cloudflared for your host using the official Linux, macOS and Windows instructions, then run the command below.
# With cloudflared installed for your host, run a tunnel to port 8080: cloudflared tunnel --url http://localhost:8080
The command outputs your unique URL (e.g. https://alpha-beta-gamma.trycloudflare.com). Paste that URL below:
sslip.io is a free public DNS service that maps any IP into a valid hostname. For instance, if your server IP is 51.81.202.92, accessing 51.81.202.92.sslip.io routes directly to your server! Caddy can issue a 100% free Let's Encrypt SSL certificate for it automatically.
Your companion domain will become: your-ip.sslip.io
If Hermes is running on the computer you are currently using, you don't need any domain or proxy! SoLoAgent accepts http://localhost:8080 directly.
ssh -N -L 8080:localhost:8080 user@your-server-ip
Then you can open http://localhost:8080 directly in your browser.
Deploy Companion on Your Server
Install commands appear when the selected release has a verified download for your host. Copy them into an interactive terminal on that host; the password is entered at a hidden prompt. Configure your reverse proxy separately using the reference tab.
Optional reverse proxy reference for an already installed native companion. Review and adapt it to your own host before use.
Verify & Open Your SoLoAgent
A reachable web service is not proof that gateway controls or chat work. The test below checks connectivity only; authenticate and verify a real chat reply before relying on an installation.
Ready to access SoLoAgent?
Click below to open your companion dashboard. Sign in using the credentials you configured in Step 1.
Need to remove an existing companion? Use the native installer's uninstall procedure for that specific user and installation. Review the affected service and files first; this hub does not provide a blanket deletion command and never removes your Hermes home or unrelated proxy configuration.