01 · Deploy
Upload code, not server instructions.
Send a ZIP. Dependencies install in a temporary builder, then the release starts inside its own constrained runtime.
private beta · Discord bot hosting
Deploy your bot.
Know what it’s doing.
yellowhost turns a ZIP file into a monitored Python or Node.js workload—with encrypted secrets, clear logs, crash states and rollback built into one dashboard.
encrypted secretsisolated containersrelease rollbackclear limits
dashboard / bots / yellow-test
RUNTIMEyellow-test
RUNNINGCPU1.3%⌁⌁⌁⌁
MEMORY76 MB⌁⌁⌁⌁
UPTIME2d 14h
14:02:11 [yellowhost] release ready 14:02:13 [bot] connected to Discord 14:02:14 [bot] commands synced ● online
↶ rollback ready
secrets encrypted
ZIP deploymentsPython 3.12Node.js 22Live runtime metricsCrash detectionBuild logsAdmin controls
One workflow
Deploy. Observe. Recover.
Hosting should make failures easier to understand—not hide them behind a complicated control panel.
02 · Observe
See the process, not a mystery green dot.
CPU, memory, uptime, PIDs, restart count, exit code and separate build/runtime logs show what your bot is actually doing.
03 · Recover
Bad deploy? Go back.
Keep the previous release available and roll back from the dashboard when a change crashes your workload.
Built around failure
A crash should be information, not panic.
yellowhost reports the state that matters: running, restarting, stopped, crashed or suspended. When a process exits unexpectedly, you can see the exit code and restart history right beside the logs.
exit code 1restart count 5rollback available
runtime timelinecrashed
Running 14:17:28
Restarting 14:17:34
Restarting 14:17:39
Crashed exit 1
Designed with boundaries
Secrets and workloads stay separated.
Encrypted environment
Tokens and API keys live outside uploaded source and are encrypted server-side before storage.
Read-only app source
The runtime mounts your deployed app read-only and gives persistent writes a separate /data directory.
Runtime limits
Memory, CPU, PIDs and file descriptors are constrained by the worker rather than left unlimited.
Private beta first
Untrusted public uploads remain closed until network-level isolation is deployed on the production Linux node.
Private beta plan
Start free.
Keep it understandable.
One bot slot is included. Staff can grant additional slots to testers while beta capacity is available.
Get your accountIncluded per bot slot512 MB RAM1 GB storagePython 3.12 / Node.js 22Encrypted environment variablesRuntime + build logsRelease rollbackNo uptime SLA during private beta. Limits and capacity may change before public launch.
FAQ
Before you deploy.
Is yellowhost really free?
The current private-beta plan is free and includes one bot slot. Staff may grant extra beta slots while capacity allows.
Where should I put my Discord token?
Use the environment-variable manager and store it as DISCORD_TOKEN. Do not place tokens or API keys directly in your uploaded ZIP.
Can I host self-bots, spam or abusive automation?
No. Automated user accounts, spam, credential abuse, malware and other harmful workloads are prohibited by the Acceptable Use Policy.
Is this production-ready?
Not yet. yellowhost is in private beta. The product workflow works locally, while public untrusted hosting stays closed until the hardened Linux infrastructure is deployed.
yellowhost
Ship the bot.
Keep the visibility.
Join the private beta while the first production hosting node is being prepared.