Running Javis OS on a laptop is convenient for trying it out. But if you want Javis to work in the background all night, send reports through Telegram at 7 a.m., or be accessible from your phone anywhere, it needs a place to run 24/7. A small VPS is enough.

This guide takes the quickest route: a Hostinger VPS with Docker Manager built in. You do not need to type installation commands or buy a domain, and you still get your own HTTPS link.

Why do you need HTTPS?

Javis supports voice conversations. Browsers only allow microphone access on HTTPS pages (or on your own computer). If you open Javis at an address like http://<ip-vps>:7777, the microphone is always blocked, with no way to enable it manually.

The good news is that Hostinger gives every VPS a hostname like srvXXXX.hstgr.cloud and automatically issues HTTPS certificates for its subdomains. That hostname is all you need.

What you need

  • A Hostinger VPS with Docker Manager. If you do not have one, rent a Hostinger VPS here for an extra 20% off through the Javis OS referral link, then come back to continue.
  • Your VPS hostname: find it under VPS in hPanel. It looks like srv1234567.hstgr.cloud.
  • A strong password for the Javis administrator account.

Step 1: Paste the Compose URL

In hPanel, open your VPS, go to Docker Manager, choose Compose, select URL, and paste this URL:

https://raw.githubusercontent.com/blogminhquy/javis-os/main/docker-compose.hostinger.yml

Step 2: Fill in three Environment fields

The Compose template only has a few fields to fill in:

  • DOMAIN_NAME: set it to javis.<hostname-vps>, for example javis.srv1234567.hstgr.cloud. If you have your own domain, enter it and remember to point its A record to your VPS IP address.
  • JAVIS_ADMIN_USER: your username. Leaving it as admin is fine.
  • JAVIS_ADMIN_PASSWORD: a strong password of your choice.
  • JAVIS_AUTO_UPDATE (optional): set it to true if you want Javis to update itself every day. Leave it blank to update using the button in the app.

Do not leave the password blank. Javis runs AI with full access to the machine. If no administrator account exists, whoever opens the link first can create it. Setting the password in advance takes you straight to the login screen when you open the app.

Step 3: Deploy and wait a few minutes

Click Deploy. Hostinger downloads the latest version of Javis and starts it. Wait about 1-3 minutes for the system to issue an HTTPS certificate, then open:

https://javis.srv1234567.hstgr.cloud

You will see the login screen. Sign in with the account you just configured.

Do not know your hostname yet? Deploy first, open Javis at http://<ip-vps>:7777, and go to Settings → Domain: Javis detects it automatically and shows a ready-to-use DOMAIN_NAME=... line with a copy button.

Step 4: Your first steps after signing in

  1. Enable two-factor authentication (2FA) on the Account page. Javis has full access to your VPS, so the account needs strong protection.
  2. Sign in to a brain on the Models page: choose Claude Code, ChatGPT, Grok, or an API provider. The article on choosing a brain for Javis OS will help you decide.
  3. Connect Telegram to ask Javis questions from your phone and receive reports. See connecting Javis OS to Telegram.

Will updates erase your data?

No. Notes, the brain, settings, and brain login sessions all live in a separate Docker data volume. Restarts and version updates preserve them.

For extra peace of mind, enable brain sync to GitHub on the Self-learning page: your entire brain is backed up to a private repository you own.

A note about subscriptions

If you use a Claude Pro/Max subscription to run Javis background tasks 24/7, be aware that this plan is intended for ordinary personal use. Continuous background work on a VPS falls outside that scope and carries a risk of account suspension, although Javis has not recorded any cases so far. For peace of mind, run Claude Code with an API key, or choose another provider as the background task model.

The full guide, including installation on VPS providers other than Hostinger, is in the Javis OS deployment documentation.