--- title: "Deploy Hermes AI Agent on a VPS: Step-by-Step Guide for 2026" description: Step-by-step tutorial for installing Hermes on a VPS, covering prerequisites, installation, settings, and the next steps for your hosting and Hermes setup. image: https://blog.ishosting.com/hubfs/Hermes%20on%20VPS/hermes-agent.png --- [VPS](https://ishosting.com/en/vps) [Dedicated hosting](https://ishosting.com/en/dedicated) [VPN](https://ishosting.com/en/vpn) [Storage](https://ishosting.com/en/storage) [About us](https://ishosting.com/en/about) [Client area](https://my.ishosting.com/en/account) [is\*hosting Blog](https://blog.ishosting.com/en) - [News](https://blog.ishosting.com/en/tag/news) - [VPS](https://blog.ishosting.com/en/tag/vps) - [Hosting](https://blog.ishosting.com/en/tag/hosting) - [Technology](https://blog.ishosting.com/en/tag/technology) - [is\*ai](https://blog.ishosting.com/en/tag/isai) - Other - [Marketing](https://blog.ishosting.com/en/tag/marketing) - [Security](https://blog.ishosting.com/en/tag/security) [News](https://blog.ishosting.com/en/tag/news) Categories [Search](https://blog.ishosting.com/hs-search-results) Hosting Services [About Us](https://ishosting.com/en/about) [Client Area](https://my.ishosting.com/en/account) [News](https://blog.ishosting.com/en/tag/news) [VPS](https://blog.ishosting.com/en/tag/vps) [Hosting](https://blog.ishosting.com/en/tag/hosting) [Technology](https://blog.ishosting.com/en/tag/technology) [is\*ai](https://blog.ishosting.com/en/tag/isai) [Marketing](https://blog.ishosting.com/en/tag/marketing) [Security](https://blog.ishosting.com/en/tag/security) [VPS](https://ishosting.com/en/vps) [Dedicated hosting](https://ishosting.com/en/dedicated) [VPN](https://ishosting.com/en/vpn) [Storage](https://ishosting.com/en/storage) 1. [Blog](https://blog.ishosting.com/en) 2. [How to](https://blog.ishosting.com/en/tag/how-to) 3. How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide How to # How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide Step-by-step tutorial for installing Hermes on a VPS, covering prerequisites, installation, settings, and the next steps for your hosting and Hermes setup. [Alex I.](https://blog.ishosting.com/en/author/alex-i) 26 May 2026 10 min reading ![How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide](https://blog.ishosting.com/hubfs/Hermes%20on%20VPS/hermes-agent.png) Table of Contents - [Step 1: Order a VPS](https://blog.ishosting.com/en/hermes-on-vps#order-vps) - [Step 2: Connect to Your Server via SSH](https://blog.ishosting.com/en/hermes-on-vps#connect-ssh) - [Step 3: Install Hermes Agent](https://blog.ishosting.com/en/hermes-on-vps#install-hermes) - [Step 4: Run Through the Setup Wizard](https://blog.ishosting.com/en/hermes-on-vps#setup-wizard) - [Step 5: Create a Telegram Bot](https://blog.ishosting.com/en/hermes-on-vps#create-telegram-bot) - [Step 6: Configure Telegram Gateway](https://blog.ishosting.com/en/hermes-on-vps#configure-telegram-gateway) - [Step 7: Install and Start the Gateway Service](https://blog.ishosting.com/en/hermes-on-vps#start-gateway-service) - [Step 8: Test Your Bot](https://blog.ishosting.com/en/hermes-on-vps#test-bot) - [Troubleshooting](https://blog.ishosting.com/en/hermes-on-vps#troubleshooting) - [Adding Other Users to Your Bot](https://blog.ishosting.com/en/hermes-on-vps#adding-users) - [Free Model Limits](https://blog.ishosting.com/en/hermes-on-vps#free-model-limits) - [What's Next](https://blog.ishosting.com/en/hermes-on-vps#whats-next) Your own AI assistant in Telegram, running 24/7 on a VPS using free models — $0 in API fees. The only thing you pay for is the VPS. Here's how to set it up from scratch, even if you've never touched a terminal. Hermes Agent is an open-source AI agent by Nous Research. It connects to Telegram (and Discord, Slack, WhatsApp — but we'll focus on Telegram), runs on any Linux server, and works with dozens of LLM providers, including free ones (we'll use OpenRouter). Think of it as your personal ChatGPT bot, but self-hosted and fully under your control. We tested the entire setup on an is\*hosting VPS. This guide documents every step, including the errors we hit and how we fixed them. ## What You'll Need - An is\*hosting VPS (Start plan or higher) - A Mac or Windows computer - A Telegram account - An OpenRouter account (free) - About 20 minutes (less if you pick the image with Hermes preinstalled) ## Step 1: Order a VPS Recommended minimum specs are: - **CPU:** Xeon 2x2.20 GHz, Xeon 3x2.60 GHz, or higher - **RAM:** 2-4 GB - **Storage:** 30-40 GB SSD - **OS:** Ubuntu 24 (or Hermes Ubuntu 24 — see below) - **Location:** Whatever's closest to you On is\*hosting you can start with: - [Start VPS](https://ishosting.com/en/vps/157_1y?city=chicago): $11.99/mo (or $10.19/mo on an annual plan). - [Medium VPS](https://ishosting.com/en/vps/158_1y?city=chicago): $24.99/mo (or $21.24/mo on an annual plan). The Lite plan (1 GB RAM) is too tight. Start, Medium and higher plans give comfortable margins. We tried Hermes on Medium VPS in this guide. ### Shortcut: Hermes Preinstalled On the order page, open the OS list and pick **Hermes Ubuntu 24** instead of plain Ubuntu 24. It's the same Ubuntu 24 with Hermes Agent already installed, so you can skip Step 3: connect via SSH (Step 2), run hermes setup, and continue from Step 4. [Deploy Hermes Agent on a VPS in one click](https://ishosting.com/en/vps/apps/hermes-agent) Want to install everything yourself? Choose plain Ubuntu 24 and follow Step 3 — the result is the same. After payment, you'll receive an **IP address** and **root password** via email. Save both. ###### Start VPS VPS configuration right for trying Hermes: 2 GB RAM, 30 GB SSD, and Hermes preinstalled on Ubuntu 24. [Get VPS](https://ishosting.com/en/vps/apps/hermes-agent) ## Step 2: Connect to Your Server via SSH **Mac:** Open Terminal (Cmd+Space → type "Terminal" → Enter). **Windows:** Download [Tabby](https://tabby.sh/) or use PowerShell. Type: ``` ssh root@YOUR_VPS_IP_ADDRESS ``` Replace YOUR\_VPS\_IP\_ADDRESS with the actual IP from your email. Example: ``` ssh root@37.252.10.8 ``` The first connection will ask: "Are you sure you want to continue connecting?" — type *yes* and press Enter. Then paste your password. **The password won't show on screen** — that's normal, it's a security feature. Just paste and hit Enter. When you see root@server:~# — you're in. ## Step 3: Install Hermes Agent **Ordered the Hermes Ubuntu 24 image?** Hermes is already installed. Run hermes setup to launch the Setup Wizard and go straight to Step 4. On plain Ubuntu 24, one command does everything — installs Python, Node.js, Git, and Hermes itself: ``` curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash ``` Wait for it to finish. The installer will show progress as it sets up the dependencies. **Important:** Use the official install URL from the [Hermes docs](https://hermes-agent.nousresearch.com/docs/), shown above. Some older guides list hermes-agent.org/install.sh — that URL is broken and will throw a syntax error near unexpected token error. Others pull the script straight from the *main* branch on GitHub; stick with the official URL instead. After installation completes, Hermes will automatically launch the **Setup Wizard**. If it doesn't, run hermes setup. ## Step 4: Run Through the Setup Wizard The wizard walks you through the configuration. Here's what to pick at each screen: ### Setup Type Select **Quick setup — provider, model & messaging** and press Enter. ![Setup Type](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/1Setup%20Type.png?width=1310&height=206&name=1Setup%20Type.png) ### Inference Provider Choose **OpenRouter (100+ models, pay-per-use)** from the list. ![Choose OpenRouter (100+ models, pay-per-use) from the list.](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/2%20Choose%20OpenRouter%20(100+%20models%2c%20pay-per-use)%20from%20the%20list..png?width=1312&height=806&name=2%20Choose%20OpenRouter%20(100+%20models%2c%20pay-per-use)%20from%20the%20list..png) ### OpenRouter API Key The wizard will ask for your OpenRouter API key. ![OpenRouter API Key](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/3OpenRouter%20API%20Key.png?width=630&height=76&name=3OpenRouter%20API%20Key.png) 1. Go to [openrouter.ai/keys](https://openrouter.ai/keys). 2. Sign up (Google login works). 3. Click **Create Key**. 4. Copy the key (starts with *sk-or-...*). Paste it into the terminal and press Enter. ### Model Selection The wizard shows a list of models with pricing. **Pick a free model.** Scroll down to find the options marked *free*. As of late September 2026, free models that support tool calling (which Hermes relies on) include: - nvidia/nemotron-3-super-120b-a12b:free — **recommended, tested and working** - nvidia/nemotron-3-ultra-550b-a55b:free — the bigger Nemotron, with a 1M-token context - qwen/qwen3.8-27b:free — also understands images - google/gemma-4-31b-it:free — also understands images - openrouter/free — a router that picks an available free model for each request You can also choose "Enter custom model name" at the bottom of the list and type the model identifier directly. ![Model Selection](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/4Model%20Selection.png?width=1296&height=822&name=4Model%20Selection.png) **Heads up:** Free models on OpenRouter come and go. During our testing, deepseek/deepseek-chat-v3.1:free returned a 404 error (removed from OpenRouter), and google/gemini-2.0-flash-exp:free also failed. Since then, z-ai/glm-5.1 has become a paid model and openrouter/owl-alpha has been removed. The Nvidia Nemotron model worked on the first try. If your chosen model fails, just switch it later with hermes config set model.default MODEL\_NAME ### Terminal Backend Select **Keep current (local)**. Your VPS runs commands directly, no containers needed. ![Terminal Backend](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/5Terminal%20Backend.png?width=1296&height=366&name=5Terminal%20Backend.png) ### Messaging Platform Select **Set up messaging now (recommended)**. ![Set up messaging now](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/6Set%20up%20messaging%20now.png?width=1302&height=222&name=6Set%20up%20messaging%20now.png) You can skip the Telegram setup entirely and jump to the finish screen. That happened to us. We'll configure Telegram manually in Steps 5 and 6. For now, continue through the wizard. ## Step 5: Create a Telegram Bot Before (or during) the setup wizard, you need a Telegram bot token: 1. Open Telegram, search for **@BotFather**. 2. Tap **Create a New Bot** (or send */newbot*). 3. Choose a display name (anything you want). 4. Choose a username (must end in *bot*, e.g., *myhermes\_bot*). 5. BotFather gives you a **token**. Copy it. Keep this token safe. Anyone who has it can control your bot. ## Step 6: Configure Telegram Gateway If the wizard asked for your Telegram token — great, you already did this part. If you skipped the step, run: ``` hermes gateway setup ``` This reopens the messaging configuration. Choose Telegram: ![Configure Telegram Gateway](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/8Configure%20Telegram%20Gateway.png?width=1298&height=810&name=8Configure%20Telegram%20Gateway.png) It will: 1. **Ask for your Telegram bot token** — paste the token from BotFather. 2. **Ask for allowed user IDs** — this restricts who can use your bot. To find your Telegram user ID: message **@userinfobot** in Telegram; it replies with your numeric ID. Enter your ID to lock the bot to yourself, or leave it empty for open access (you can restrict it later). 1. **Ask about home channel** — type *Y* to use your own chat as the notification channel. 2. **Show platform list** — select **Done** (no need to add Discord, Slack, etc.). ![Configure Telegram Gateway](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/9Configure%20Telegram%20Gateway.png?width=1186&height=780&name=9Configure%20Telegram%20Gateway.png) ## Step 7: Install and Start the Gateway Service The wizard will ask: **"Start the gateway now?"** — answer *Y* **"Start automatically on login/boot as a systemd service?"** — answer *Y* **"Choose how the gateway should run in the background"** — select **System service**. On a VPS, this is the right choice: the bot starts automatically when the server reboots. ![Choose how the gateway should run in the background](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/10Choose%20how%20the%20gateway%20should%20run%20in%20the%20background.png?width=1288&height=226&name=10Choose%20how%20the%20gateway%20should%20run%20in%20the%20background.png) **"Run the system gateway service as which user?"** — type *root* Done. The gateway is now running. ## Step 8: Test Your Bot Open Telegram. Find your bot by the username you created. Send "hi." ![Test Your Bot](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/11Test%20Your%20Bot.png?width=1032&height=314&name=11Test%20Your%20Bot.png) If everything works, the bot responds. ## Troubleshooting ![01check logs, verify config, fix, and restart](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/01.png?width=1534&height=448&name=01.png) Bad config, wrong model, garbage characters in YAML — none of these throw clear errors. The fix is always the same loop: check logs, verify config, fix, and restart. ### "The Model Provider Failed After Retries" The most common error. Your bot is running, but the LLM can't respond. ![Troubleshooting](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/12%20Troubleshooting.png?width=1042&height=286&name=12%20Troubleshooting.png) **Check the logs first:** ``` journalctl -u hermes-gateway -n 30 --no-pager ``` What the error codes mean: - *HTTP 404: No endpoints found for MODEL\_NAME* — the model was removed from OpenRouter. Switch models. - *HTTP 400* — bad request. It usually means the model field is empty or the provider config is broken. See "Config Corruption" below. - *HTTP 429* — rate limit. If you've hit the per-minute limit, wait a minute. If you've used up the daily free quota, switching to another free model won't help — the quota is shared across all free models on your account (see "Free Model Limits" below). A 429 can also mean one specific free model is overloaded; in that case, switching models does help. - *HTTP 401* — bad API key. Re-check your OpenRouter key. **Switch to a different model:** ``` hermes config set model.default nvidia/nemotron-3-super-120b-a12b:free sudo systemctl restart hermes-gateway ``` During our testing, we went through three models before finding one that worked: 1. deepseek/deepseek-chat-v3.1:free — 404, model removed from OpenRouter 2. google/gemini-2.0-flash-exp:free — failed after retries 3. nvidia/nemotron-3-super-120b-a12b:free — worked immediately Free models rotate. If yours stops working, check [openrouter.ai/models](https://openrouter.ai/models) and filter by "free." ### Config Corruption: Garbage Characters in config.yaml This one is sneaky. If you paste text into *nano* from certain sources, invisible UTF-8 characters can end up at the start of the file. Hermes tries to parse the YAML, fails silently on the corrupted section, and loads without a main model. Everything downstream breaks. **How to detect it:** ``` head -c 20 /root/.hermes/config.yaml | xxd ``` If the first bytes aren't *6d 6f 64 65 6c* (the word *model*), you have garbage. **How to fix it:** ``` sed -i '1s/^[^a-zA-Z]*//' /root/.hermes/config.yaml ``` Then verify with hermes config show — the *model:* block should be visible. **General rule:** After any manual edit to *config.yaml*, always run hermes config show to confirm Hermes actually parsed what you wrote. Visual inspection in nano isn't enough. ### api\_key\_env vs. Actual API Key In *config.yaml*, the *providers:* block has a field called api\_key\_envThis is the *name of the environment variable* that holds your key — not the key itself. **Wrong:** ``` providers: anthropic: api_key_env: sk-ant-abc123... # ← actual key, WRONG ``` **Right:** ``` providers: anthropic: api_key_env: ANTHROPIC_API_KEY # ← variable name, correct ``` The actual key goes in */root/.hermes/.env*. If you paste the raw key into *api\_key\_env*, Hermes won't throw an error; it'll silently fail to authenticate and fall through to another provider with no model configured. ### provider: auto Cascading Failures Hermes uses auxiliary models for internal tasks: skill management, session compression, triage, and approval. By default, these are set to *provider: auto*, which means "use whatever the main model uses." If your main model config is broken, *auto* cascades the failure to all auxiliary slots. You'll see HTTP 400 errors flooding the logs even after fixing the main model. **Fix by setting explicit models for auxiliary tasks:** ``` hermes config set auxiliary.compression.provider deepseek hermes config set auxiliary.compression.model deepseek-v4-flash ``` Repeat for other slots (*title\_generation*, *session\_search*, etc.) or edit *config.yaml* directly: ``` auxiliary: compression: provider: deepseek model: deepseek-v4-flash title_generation: provider: deepseek model: deepseek-v4-flash ``` ### Compression Model Warning If your main model has a large context window (e.g., Claude Sonnet at 500k tokens) but your compression model has a smaller one (e.g., Haiku at 200k), Hermes will warn on every session: "Compression model context smaller than threshold." **Fix:** ``` hermes config set compression.threshold 0.2 ``` This sets the threshold to 20% of the main model's context — well within the compression model's window. ### Terminal Backend Set to SSH-to-self If the setup wizard (or a bad config edit) set terminal.backend to *ssh* pointing at your own VPS IP, Hermes will try to SSH into itself to run shell commands. This breaks things in creative ways. **Fix:** ``` hermes config set terminal.backend local ``` ### Tirith Security Scanner Blocking Safe Commands Hermes has a built-in security scanner called Tirith that intercepts certain command patterns (like piping curl output into Python). Even with auto-approve enabled, Tirith can still trigger approval prompts. If your bot's tasks involve fetching data from APIs and you trust the endpoints: ``` hermes config set security.tirith_enabled false ``` **Note:** Tirith and the approval system are separate. Disabling one doesn't disable the other. ###### VPS More power, less cost. VPS with NVMe speed, 40+ locations, managed or unmanaged — your choice for Hermes. [Get VPS](https://ishosting.com/en/vps) ## Useful Commands Once Hermes is running, here's your daily toolkit: ``` sudo systemctl status hermes-gateway # check if gateway is running sudo systemctl restart hermes-gateway # restart after config changes journalctl -u hermes-gateway -n 50 # view recent logs hermes config set model.default MODEL # switch model hermes gateway setup # reconfigure messaging hermes update # update to latest version hermes doctor # diagnose issues ``` ## Adding Other Users to Your Bot ![How to add users to your bot](https://blog.ishosting.com/hs-fs/hubfs/Hermes%20on%20VPS2/02.png?width=1534&height=418&name=02.png) This is where Hermes gets confusing. There are two authorization systems, and which one actually controls access depends on your setup. ### Method 1: Allowlist in .env (The One That Works) The TELEGRAM\_ALLOWED\_USERS variable in /root/.hermes/.env is the real gatekeeper. If this variable exists and has values, it overrides anything in config.yaml. Check what's there now: ``` grep -i TELEGRAM_ALLOWED /root/.hermes/.env ``` To add a user, edit the *.env* file: ``` nano /root/.hermes/.env ``` Find TELEGRAM\_ALLOWED\_USERS and add the new ID: ``` TELEGRAM_ALLOWED_USERS=154220189,987654321 ``` Restart: ``` sudo systemctl restart hermes-gateway ``` To find the new user's ID: ask them to message the bot, then check logs. ``` journalctl -u hermes-gateway -n 30 | grep Unauthorized ``` ### Method 2: config.yaml (May or May Not Work) Some Hermes versions read allowed\_chats from config.yaml: ``` telegram: allowed_chats: '154220189,987654321' ``` But if *.*env has TELEGRAM\_ALLOWED\_USERS set, config.yaml gets ignored. Don't spend an hour editing YAML variants, wondering why nothing changes — check *.env* first. ### Method 3: Pairing Flow (Advanced) Hermes has a pairing system where new users message the bot, receive a code, and the owner approves with hermes pairing approve telegram \But pairing only works when there's *no* allowlist set. If TELEGRAM\_ALLOWED\_USERS has any value, pairing is disabled entirely. Pick one approach and stick with it. Allowlist in .env is the simplest. ### Where Hermes Stores Config (The Full Picture) Hermes has three config locations. The same setting can exist in multiple places. When something doesn't work, check all three: 1. **/root/.hermes/config.yaml** — model, provider, auxiliary settings, gateway config. 2. **/root/.hermes/.env** — API keys, Telegram tokens, allowed user lists. 3. **Hermes auth store** — registered providers (check with *hermes auth list*). ## Free Model Limits Running on free OpenRouter models means: - Up to 20 requests per minute - 50 requests per day in total — the limit is per account and shared across all free models, so switching to another free model doesn't reset it - 1,000 free-model requests per day once you've bought at least 10 credits ($10) on OpenRouter - Image recognition (vision) only on some free models, such as Qwen3.8 and Gemma 4 — Nemotron is text-only - Lower quality compared to Claude or GPT - Free models occasionally disappear or get rate-limited For casual use and experiments, that's absolutely fine. When you outgrow free limits, top up $10 on OpenRouter. That alone raises your free-model cap from 50 to 1,000 requests per day — often enough for a personal bot, so you can keep running free models. If you need better answers, switch to a paid model: ``` hermes config set model.default anthropic/claude-haiku-4.5 sudo systemctl restart hermes-gateway ``` Claude Haiku 4.5 costs $1/$5 per million tokens — a few dollars a month for typical personal use. ## What You've Built After following this guide, you have: - A VPS running 24/7 in a data center - Hermes AI Agent with a Telegram bot interface - A free LLM model ($0 in API costs) - Auto-start on server reboot - Access restricted to your Telegram account only The bot keeps running even when your laptop is off. ## What's Next Hermes is more than a chat interface. Once you're comfortable: - **Add skills** — Hermes can learn new capabilities from markdown files you write - **Set up cron jobs** — schedule automated tasks ("send me a daily summary at 9 AM") - **Connect more platforms** — Discord, Slack, WhatsApp, Signal - **Switch to stronger models** — Claude, GPT, DeepSeek for production-quality responses - **Use local models** — run Ollama on a GPU server for fully private AI Scale your VPS server anytime you hit the resource limits because of new skills or a full database. At is\*hosting, you can request it on [any VPS.](https://ishosting.com/en/vps)  Full documentation: [hermes-agent.nousresearch.com/docs](https://hermes-agent.nousresearch.com/docs/) ###### Worldwide is\*hosting works with the best data centers worldwide and HI-END class equipment. [See Coverage](https://ishosting.com/en/datacenters) Table of Contents - [Step 1: Order a VPS](https://blog.ishosting.com/en/hermes-on-vps#order-vps) - [Step 2: Connect to Your Server via SSH](https://blog.ishosting.com/en/hermes-on-vps#connect-ssh) - [Step 3: Install Hermes Agent](https://blog.ishosting.com/en/hermes-on-vps#install-hermes) - [Step 4: Run Through the Setup Wizard](https://blog.ishosting.com/en/hermes-on-vps#setup-wizard) - [Step 5: Create a Telegram Bot](https://blog.ishosting.com/en/hermes-on-vps#create-telegram-bot) - [Step 6: Configure Telegram Gateway](https://blog.ishosting.com/en/hermes-on-vps#configure-telegram-gateway) - [Step 7: Install and Start the Gateway Service](https://blog.ishosting.com/en/hermes-on-vps#start-gateway-service) - [Step 8: Test Your Bot](https://blog.ishosting.com/en/hermes-on-vps#test-bot) - [Troubleshooting](https://blog.ishosting.com/en/hermes-on-vps#troubleshooting) - [Adding Other Users to Your Bot](https://blog.ishosting.com/en/hermes-on-vps#adding-users) - [Free Model Limits](https://blog.ishosting.com/en/hermes-on-vps#free-model-limits) - [What's Next](https://blog.ishosting.com/en/hermes-on-vps#whats-next) ## Related articles ![How to Deploy OpenHuman on a VPS: Step-by-Step Guide](https://blog.ishosting.com/hubfs/blog/openhuman-on-vps/openhuman-on-vps.png) How to ### How to Deploy OpenHuman on a VPS: Step-by-Step Guide Step-by-step guide to installing OpenHuman on a VPS: Docker, Caddy, HTTPS, and connecting the desktop app. All errors... Alex I. 9 Jun 2026 7 min reading ![How to Set up a Linux VPS: a Step-by-step User Guide](https://blog.ishosting.com/hubfs/blog/how-to-set-up-linux-vps/configuring-linux.png) VPS ### How to Set up a Linux VPS: a Step-by-step User Guide A complete Linux VPS setup guide for beginners: connect via SSH, create users, configure a firewall, enable... Natasha M. 25 Jun 2024 9 min reading ![How to Host a CS2 Server, and When Do You Really Need It?](https://blog.ishosting.com/hubfs/blog/how-to-host-a-cs2-server/how-to-host-a-cs2-server.png) Hosting ### How to Host a CS2 Server, and When Do You Really Need It? Set up your own CS2 dedicated server on a VPS. Covers requirements, installation, configuration, and how to invite... is\*hosting team 15 Jan 2026 13 min reading ## Subscribe to Newsletter The latest news, profitable discounts, and informative articles - subscribe to the is\*hosting blog and be the first to receive a useful newsletter. - **Services** Services - [Virtual Private Servers](https://ishosting.com/en/vps) - [Dedicated Servers](https://ishosting.com/en/dedicated) - [Storage](https://ishosting.com/en/storage) - [VPN](https://ishosting.com/en/vpn) - [Special Offers](https://ishosting.com/en/special-offers) - --- - **Company** Company - [About Us](https://ishosting.com/en/about) - [Data Centers](https://ishosting.com/en/datacenters) - [Blog](https://blog.ishosting.com/en) - [Contacts](https://ishosting.com/en/about#offices) - --- - **Information** Information - [Knowledge Base](https://help.ishosting.com/en) - [Support](https://ishosting.com/en/support) - [Payments Methods](https://ishosting.com/en/payment-methods) - --- - **Account** Account - [Create Account](https://my.ishosting.com/en/register) --- © 2026 WEBRAIN OÜ, Harju maakond, Tallinn, Kesklinna linnaosa, Endla tn 4, 10142 - [![](https://blog.ishosting.com/hs-fs/hubfs/raw_assets/public/ishosting-theme/images/rating-sm.png?width=328&height=70&name=rating-sm.png) ![](https://blog.ishosting.com/hs-fs/hubfs/raw_assets/public/ishosting-theme/images/rating.png?width=421&height=70&name=rating.png)](https://hostadvice.com/hosting-company/ishosting-reviews/#main-info) --- - [Terms of Use](https://ishosting.com/en/terms-of-use) - [Privacy Policy](https://ishosting.com/en/privacy-policy) - [KYC Policy](https://ishosting.com/en/kyc-policy) - [SLA](https://ishosting.com/en/service-level-agreement) - [AUP](https://ishosting.com/en/acceptable-use-policy) - en - [en](https://blog.ishosting.com/en) - [ru](https://blog.ishosting.com/ru/hermes-on-vps) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "abstract" : "Step-by-step tutorial for installing Hermes on a VPS, covering prerequisites, installation, settings, and the next steps for your hosting and Hermes setup.", "alternativeHeadline" : "Deploy Hermes AI Agent on a VPS: Step-by-Step Guide for 2026", "articleSection" : "How to", "author" : { "@type" : "Organization", "name" : "Alex I.", "sameAs" : [ "https://www.linkedin.com/company/is-hosting", "https://twitter.com/ishostingcom", "https://www.instagram.com/is.hosting" ], "url" : "https://blog.ishosting.com/en/author/alex-i" }, "dateModified" : "2026-09-28T14:17:17.000Z", "datePublished" : "2026-05-26T11:27:22.000Z", "description" : "Step-by-step tutorial for installing Hermes on a VPS, covering prerequisites, installation, settings, and the next steps for your hosting and Hermes setup.", "headline" : "How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide", "image" : [ { "@type" : "ImageObject", "height" : 1348, "name" : "How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide", "url" : "https://25913237.fs1.hubspotusercontent-eu1.net/hubfs/25913237/Hermes%20on%20VPS/hermes-agent.png", "width" : 2396 } ], "inLanguage" : "en", "mainEntityOfPage" : { "@id" : "https://blog.ishosting.com/en/hermes-on-vps", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "address" : [ { "@type" : "PostalAddress", "addressCountry" : "EE", "addressLocality" : "Tallinn", "addressRegion" : "Harju maakond", "postalCode" : "10120", "streetAddress" : "Kesklinna linnaosa, Tuukri tn 19-315" }, { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "W1W 7LT", "streetAddress" : "85 Great Portland Street, First Floor" } ], "description" : "is*hosting is an IaaS provider since 2005. We provide VPS, VPN, dedicated servers and data storage to help you achieve your biggest dreams.", "email" : "sales@ishosting.com", "foundingDate" : "2005", "legalName" : "WEBRAIN OÜ", "logo" : { "@type" : "ImageObject", "height" : 26, "url" : "https://help.ishosting.com/hubfs/logo-ishosting.png", "width" : 138 }, "name" : "is*hosting" }, "thumbnailUrl" : "https://25913237.fs1.hubspotusercontent-eu1.net/hubfs/25913237/Hermes%20on%20VPS/hermes-agent.png", "timeRequired" : "PT10M", "url" : "https://blog.ishosting.com/en/hermes-on-vps", "wordCount" : 3357 } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en", "name" : "Blog", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en/tag/how-to", "name" : "How to", "position" : 2 }, { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en/hermes-on-vps", "name" : "How to Deploy Hermes AI Agent on a VPS: Step-by-Step Guide", "position" : 3 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Alex I.", "url" : "https://blog.ishosting.com/en/author/alex-i" }, "dateModified" : "2026-09-28T14:17:17.217Z", "datePublished" : "2026-05-26T11:27:22.000Z", "headline" : "Deploy Hermes AI Agent on a VPS: Step-by-Step Guide for 2026", "image" : [ "https://blog.ishosting.com/hubfs/Hermes%20on%20VPS/hermes-agent.png" ], "mainEntityOfPage" : { "@id" : "https://blog.ishosting.com/en/hermes-on-vps", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.ishosting.com/hubfs/logo-ishosting.png" }, "name" : "WEBRAIN OÜ" } } ```