A real Linux box, and a domain to call your own.
A shell is your own always-on Linux machine: SSH in, host websites, run Node, Python, Go and containers, and deploy straight from GitHub — with the system kept up to date for you. Pick a name and your site lives at <name>.4evr.sh. Run your IRC client in tmux, run a bot in a container, learn the command line.
Put anything online.
A blog, a bot, an API or a whole Compose project. Each one can have its own address under your domain, with HTTPS, and you manage them all from the portal.
Deploy from GitHub
Connect a repo and every push to your branch is pulled, built and restarted for you. Its settings go in a .env that stays in your shell — never committed or sent to GitHub.
Containers in your shell
Rootless Podman, run as your own user, so docker and docker compose work as usual. Run a bot or an API, or tick boxes for ready-made services like Postgres, Redis and Uptime Kuma.
One-click apps
WordPress, Grav, DokuWiki, FreshRSS, Hugo and Zola, installed and wired to a database for you. Or drop your own HTML and PHP in a folder.
Web addresses
Any name under your domain, like blog.you.4evr.sh or api.you.4evr.sh, can point at a website, a program or a container. HTTPS is automatic.
Everything you run, in one place
Websites, programs and containers sit in one list, each with its own page: addresses, deploys, logs, settings, and its CPU and memory use.
A guide for each way
The portal's Guide walks through putting something online — from GitHub, a one-click app, your own files, or a command — with a screenshot of every step.
Modest by design. Enough to be genuinely useful.
Shells run on shared machines, so resources are fair-shared rather than guaranteed. Plenty for a client, a few scripts and some learning.
| What you get | Details |
|---|---|
| Access | SSH by public key as <you>@<you>.4evr.sh · a web console in the portal · SFTP (off until you turn it on) |
| Your machine | Ubuntu 24.04, isolated from everyone else's, with your own userland and services |
| Your domain | Pick a name — your site lives at <name>.4evr.sh |
| Web hosting | As many sites as you like — static files, PHP, or your own app on a port. Give any name under your domain, like blog.<name>.4evr.sh, to a website, a program or a container, HTTPS included |
| One-click apps | WordPress · Grav · DokuWiki · FreshRSS · Hugo · Zola · Adminer — installed and wired to a database for you |
| Database | Your own MariaDB or PostgreSQL server, kept apart from the shell so it survives a rebuild |
| Containers | Rootless Podman with Compose — turn it on in the portal, then build a project by clicking, bring your own compose.yml, or deploy a GitHub repo on every push |
| Portal | portal.4evr.sh — console, file editor, apps, web addresses, databases, containers, metrics and a step-by-step guide in your browser |
| Toolchain | Node (with pnpm & yarn) · Python · Go · PHP · Rust · GCC · Tcl · git · tmux & screen · Vim & nano · mosh |
| IRC tooling | irssi · WeeChat · eggdrop, scaffolded with the mkbot helper — or run any bot in a container |
| Resources | 1 GB RAM + 1 GB swap · up to 2 CPU cores, fair-shared · 5 GB for your files (the system doesn't count against it) |
| Upkeep | We patch the system and update the toolchain every week. There's no root — install your own tools in your home |
| Uptime | Best-effort, provided as-is — keep your own backups |
Prefer a browser? Do it all from the portal.
Everything your shell can do, without an SSH client or FTP app: sign in at portal.4evr.sh to manage your apps, web addresses, files, databases and more.
Pick a starting point.
Always-on IRC, the DIY way
Run WeeChat or irssi inside tmux and you get bouncer-like persistence with full control: your config, your scripts, your logs. Detach, walk away, reattach later — it's all still there.
Request a shell in chat.
Each shell is a real machine of its own, so there's a light human check — one per person — and accounts go to real people who'll use them.
Ask in #IRCForever
In #IRCForever, type !shell <name> <email> — your site becomes <name>.4evr.sh. One per person.
Add your SSH key
Once you're approved, we email you a link to add your SSH public key. Your shell is built right after.







