How to Claim Your Free Kerit Cloud Server in Three Minutes
A step-by-step walkthrough for claiming a free Kerit Cloud server — joining Discord, registering on the panel, creating the server and getting your bot online.
On this page
Kerit Cloud’s free plan gives you a real server — 256 MB of RAM, 30% of an AMD EPYC core and 2 GB of NVMe storage — that runs your bot 24/7 with no sleep mode and no card required. Getting one takes about three minutes. This walkthrough covers each step and the small things that make the first deploy go smoothly.
Before you start
Have these ready:
- Your bot’s code, working locally.
- A dependency file —
package.jsonfor Node.js,requirements.txtfor Python, or a built JAR for Java. - Your bot token, which you’ll add as an environment variable rather than keeping in the code.
- A Discord account, because signup and support happen in the Kerit Cloud Discord server.
If your token is currently written into your code, move it to an environment variable first. It takes two minutes and protects you from the most common way bots get hijacked — see keeping your bot token safe.
Step 1: Join the Discord
Open the invite link from the free hosting page and join the Kerit Cloud Discord server. This is where you’ll find the panel link, announcements and support from the team and community. If you get stuck at any point, ask there.
Step 2: Register your account
Use the panel link shared in the Discord to create your account. There’s no credit card, no billing page and no email verification loop — just the details needed to log in. Once registered, you’ll land in the control panel.
Step 3: Create your server
In the panel, create a new server and:
- Select the Free plan.
- Choose your runtime — Node.js (16–22), Python (3.9–3.12), Java (11, 17 or 21), Go, Bun or Deno. Match the version you use locally; a bot written for Node.js 20 can fail on 16.
- Create it. The server is ready in seconds, running in Virginia — Discord’s primary gateway region — for sub-18 ms WebSocket latency.
Step 4: Upload your code
Open the server’s file manager and upload your project, or connect with an SFTP client like FileZilla or WinSCP using the credentials shown in the panel (here’s how).
Upload:
- your source files,
- your dependency file (
package.jsonandpackage-lock.json, orrequirements.txt), - any config or data files the bot needs.
Don’t upload node_modules/, a Python virtual environment (venv/, .venv/) or your .env file. Dependencies install automatically on the server, and secrets go into environment variables.
Step 5: Set environment variables
In the panel’s startup or variables section, add your token — for example DISCORD_TOKEN or BOT_TOKEN, matching whatever name your code reads — plus any API keys. Environment variables are stored encrypted and never printed in your logs.
Check the start command too. Common values:
| Runtime | Start command |
|---|---|
| Node.js | npm start or node index.js |
| Python | python -u main.py |
| Java | java -XX:MaxRAMPercentage=75 -jar bot.jar |
| Bun | bun run index.ts |
| Deno | deno run --allow-net --allow-env main.ts |
For Python, the -u flag makes log output appear in the console immediately instead of being buffered.
Step 6: Press Start
Open the console and start the server. You’ll see dependencies install, then your bot’s startup output. When you see your “logged in” or “ready” line, check Discord — your bot should be online.
If something goes wrong, the console shows the error. The most common first-deploy issues:
- Missing token. The variable name in the panel doesn’t match the one in your code.
- Missing module. A package isn’t listed in your dependency file.
- Wrong version. The runtime is older than the one you developed on.
- “Used disallowed intents”. Your code requests a privileged intent that isn’t enabled in the Discord Developer Portal.
If your bot crashes later, a watchdog restarts it within seconds, and the error stays in the console so you can fix it.
Step 7: Stop your local copy
If the bot is still running on your computer, stop it. Two copies with the same token cause duplicate replies on Discord and 409 Conflict errors on Telegram. Your free server now keeps the bot online around the clock — your PC can sleep.
Make the most of the free server
A few habits keep a free bot healthy:
- Watch the memory graph. 256 MB fits most single-purpose bots, but caches grow as your bot joins servers. What fits in 256 MB shows how to keep usage low.
- Use the included database. The free plan comes with a shared MySQL database — much safer than JSON files that can corrupt on a crash. See using the shared MySQL database.
- Keep it active. Active servers stay forever. Only servers that have been stopped and untouched for an extended period are reclaimed, and you’re warned on Discord first — details in keeping your free server active.
- Test before announcing. Try every command in a private server before inviting the bot anywhere public. See testing your bot on free hosting.
When you’re ready to grow
The free plan is free forever, not a trial. When your bot needs more — more servers, more features, backups or an SLA — upgrade with one click from the panel. The server resizes in place; files, database and environment variables all stay. Paid plans start at $0.67/month on the Discord bot plans page, with a 3-day money-back guarantee.
Summary
Join the Kerit Cloud Discord, register on the panel with no card, create a server on the Free plan with the right runtime, upload your code without node_modules or secrets, set your token as an environment variable, and press Start. In about three minutes your bot is online 24/7 — and when it outgrows 256 MB, upgrading takes one click.