Everything the dashboard does for a server
belajarhosting.com watches your VPS and gives you a terminal and an assistant to work on it, from any browser. This page says what each part does, and where its limits are.
Connect a server with one command
You add a server in the dashboard, and it gives you a command to run on the VPS. That is the whole setup.
- The command works once and for an hour, so a copy of it is of no use to anybody else.
- It downloads the agent, checks it against its SHA-256 checksum, and runs it as a systemd service under a user of its own, without root.
- The agent only reports how the server is doing. It takes no commands from anybody.
- It adds one SSH key for the dashboard: for root where the server allows that, and otherwise for the user who ran the command.
- Tested with every change on Ubuntu 22.04, Ubuntu 24.04, Ubuntu 26.04, Debian 12, Debian 13, on amd64. An arm64 build is included and has seen less testing.
- Removing a server in the dashboard takes the agent and the key off it again. So does one command on the server itself.
See how every server is doing
The dashboard shows all your servers at once, and each of them in detail, updated as the reports come in.
- CPU, load, memory, swap, every disk, network traffic and the busiest processes.
- You choose how often a server reports: every 10, 30 or 60 seconds.
- Charts over the last hour, 6 hours, 24 hours, 3 days and 7 days, as far back as your plan keeps the history. Every chart can be read as a table too.
- A server that misses three reports in a row shows as offline, with when it was last heard from.
- Of a process, the agent sends its name, its user and what it uses. Never its command line, which can hold a password.
A terminal in your browser
A real shell on your server, opened from the dashboard. Nothing to install, and no key to carry around.
- You are logged in as the user the key was added for: root, or the user with sudo.
- Two terminals can be open on a server at the same time. One that is left alone for 30 minutes is closed.
- Before you open one you choose what is kept of it: the commands you enter, and a recording of the screen. Both are up to you.
- What the terminal does not show while you type, such as a password, is never written to the command log.
- Recordings are stored encrypted and deleted after 7 days. The list of sessions and their commands is kept for 90 days.
Look after what runs on it
Pages of their own for what you would otherwise look up in the terminal. They work on the server over SSH when you open them.
Services
What systemd runs and what starts with the server. Start, stop, restart and reload them, or switch them on and off for the next start. When one does not come up, you see the end of its log.
Processes
Everything that runs, with what it uses of the CPU and the memory, measured over one second. Ask a process to end, or end it at once.
Logs
The newest lines of the system journal, for one service or all of them and by how serious they are, and of the files in /var/log. Search them for a piece of text.
Files
Browse the server, edit text files in the browser, upload and download them (a folder as a .tar.gz), rename, move and delete them, and change their owner and mode. A file that changed on the server since you opened it is not overwritten.
Cron
The scheduled jobs of every user, said in words, added and changed without remembering the five fields of cron, and what the system itself schedules.
Firewall
Switch ufw on and off, choose what happens to traffic no rule is about, and add or delete rules by port and address. SSH is allowed before the firewall goes on, and after every change the dashboard logs in again: if it cannot, the server undoes the change by itself within a minute.
Websites
Install nginx, make a site for a domain that serves files or passes requests on to an app, switch it on and off, and get it a free HTTPS certificate of Let's Encrypt that renews by itself. Every change is checked by nginx first, so a mistake never takes the other sites down.
Databases
Install MariaDB or PostgreSQL, make databases and users, give a user a new password, and delete them. A password is made for you, shown once and not kept.
Backups
The folders you choose and every MySQL or PostgreSQL database, packed into one archive every day, every week or when you ask, and sent by the server straight to a bucket of yours at a storage that speaks the S3 API, such as Cloudflare R2, Amazon S3, Wasabi or Backblaze B2. The newest ones are kept and the older ones deleted. Download one, or unpack it into a folder on the server to take back what you need. Your secret key for that storage stays with the dashboard, stored encrypted. The server gets a link that is good for one archive only.
- SSH and the agent are not stopped from these pages, and the folders of the system and the SSH keys are not deleted. SSH is only restarted once its configuration has been checked.
- They are for developers, admins and the owner of a team, who could do the same in the terminal. Every change is noted in the history of the server.
An AI assistant that asks before it acts
Describe the problem in your own words. The assistant reads what it needs on the server, tells you what it found, and proposes what to do.
- It can look at the system, the metrics, the services, files and logs, run commands and write files.
- Ask about one server on its page, or about all your servers at once on the page of the assistant. There it compares them, and names the server for everything it does.
- A command runs on its own only when it is on a list of commands that read and change nothing, with options known to do the same.
- Everything else waits for you. You see the exact command, why the assistant wants it and why it was held back. Your approval is for that command alone, and it expires after 10 minutes.
- Reading a file that tends to hold secrets, such as a key or an .env file, waits for you too.
- Commands that wreck a server are refused outright. Nobody can approve them.
- The rules are applied by the dashboard, not by the AI. What the assistant reads on a server cannot talk it past them.
- One question costs one AI credit, however many steps it takes to answer it.
- To answer you, what the assistant reads on your server (files, logs, the output of commands) is sent to the provider of the language model. The privacy policy says what that means.
Know when something is wrong
Connect your Telegram account with one link, and the dashboard writes to you when a server needs attention.
- Four rules watch every server: it went offline, or its CPU, its memory or one of its disks is nearly full.
- The level is 90% to begin with. You can move it and switch each rule off, for all servers of your team at once.
- One message when a problem starts and one when it is over. A level that hovers around its limit does not fill your chat.
- Without Telegram the alerts still show in the dashboard.
A record of what was done
Every server has a history, so you can look up later what happened to it, and by whom.
- Every terminal session: who opened it, when, and for how long.
- The commands of a session and its recording, when you chose to keep them. A recording plays back in the browser.
- Every command the assistant ran, with whether you approved it, and every one that was declined or refused.
- Updates, reinstalls and removals of the agent, and changes of the SSH key.
- Services that were started, stopped or restarted, processes that were ended, files that were saved, uploaded, downloaded, moved or deleted, crontabs that were changed, every change of the firewall, websites and their certificates, databases and their users that were made or deleted, and backups that were made, restored, downloaded or deleted.
- The activity page of a team puts all of it together, for every server, with who joined and left the team.
Careful with the access you give it
Connecting a server gives the dashboard a way in, as root. This is how that is kept safe.
- Every server gets a key pair of its own. One key never opens two servers.
- Private keys are stored encrypted, each with its own key, under a master key that is kept outside the database.
- The dashboard remembers the host keys a server showed when it was connected, and refuses to connect when they change.
- You can replace the key of a server with one click. The old one only goes when the new one has proven to work.
- Passwords are stored as Argon2id hashes. Logging in is limited to a few attempts per account and per address.
- Two-factor authentication with an authenticator app, and recovery codes for when the phone is gone.
- You see every device your account is logged in on, and can log each of them out.
- The agent runs without root. Its token can be read by root and by the agent only.
Who else gets in
Invite the people you work with, each with the role that fits what they do there.
- Invite somebody by email. They join once they accept, with an account for that address.
- Four roles. The owner can do everything and pays for the plan. An admin adds servers and invites people. A developer uses the terminal, the assistant and the pages that look after a server, and sets a server up. A viewer looks without changing anything.
- A developer or a viewer can be given some servers only. The others do not exist for them: not in the lists, not in alerts, not in the terminal.
- What a role allows is checked by the dashboard with every request, not just hidden from the screen.
- Somebody who is removed loses access at once. A terminal they still have open is closed within a minute.
- One account can be in several teams, such as your own and those of your clients, and switches between them in the dashboard.
- Everybody in the team who connected Telegram gets the alerts of the servers they may see, with the name of the team in each.
- The owner can hand the team to another member, or delete it once its servers are removed.
What it is not
belajarhosting.com shows you your server and gives you the tools to work on it. It is not a hosting panel.
- It does not set up mail for you, or install your app. It makes the website and the database your app needs; putting the app on the server is up to you, in the terminal or with the assistant.
- It does not keep your backups. They go to a storage of your own, which you pay for there.
- It runs on Ubuntu and Debian servers with systemd. Other systems are not supported.
Connect your first server in a few minutes
Create an account, run one command on your VPS, and watch it show up in the dashboard. The Free plan needs no payment details.