DiscordCraft
bot-tutorial

How to Keep Discord Bot Online 24/7 for Free (No Credit Card)

Learn proven, credit-card-free methods to host your Discord bot 24/7 — using Replit, Railway, and GitHub Codespaces. No payment required!

June 25, 2026 · 378 views

Keeping your Discord bot online 24/7 is a common hurdle for beginners — especially when most hosting platforms ask for a credit card upfront. 🚫💳 Whether you're building a moderation bot, a music player, or a custom slash-command utility, keeping your Discord bot online 24/7 for free is absolutely possible — and we’ll walk you through exactly how, step-by-step, with zero financial risk.

In this comprehensive guide, you’ll discover reliable, beginner-friendly hosting options that don’t require billing info, understand common pitfalls (like sleep timeouts or token leaks), and learn how to monitor uptime like a pro. We’ll focus on three battle-tested, credit-card-free platforms: Replit, Railway, and GitHub Codespaces, each with real-world setup instructions and pro tips. Bonus: we’ll also cover essential best practices — from environment variable security to heartbeats — so your bot stays stable, scalable, and safe. 💡

Let’s get your bot running — and staying up — without opening your wallet.

Why Your Bot Keeps Going Offline (and Why It’s Not Your Code)

If your bot disconnects after a few hours or goes offline when you close your laptop, it’s almost certainly a hosting issue — not a bug in your code. Local machines (like your personal computer) aren’t designed for 24/7 uptime: they sleep, restart, lose internet, or shut down unexpectedly.

Discord bots rely on a persistent WebSocket connection to the Discord API. If that connection drops and isn’t automatically reestablished (or if the process itself terminates), your bot goes offline. Hosting platforms solve this by keeping your bot process alive in the cloud — but many services gate their free tiers behind credit card verification.

Good news: the tools we’ll cover don’t require one. ✅

✅ Method 1: Replit — Easiest Free Hosting (No CC Required)

Replit is ideal for beginners: browser-based, instant setup, built-in console, and — crucially — no credit card needed for its free tier. As of mid-2026, Replit still offers unlimited runtime for public repos and generous CPU/memory allowances for hobby projects.

Step-by-Step Setup

  1. Create a new Python repl at replit.com → Click “+ Create” → Choose “Python”.
  2. Install required packages: In the shell, run: 
    pip install discord.py python-dotenv
  3. Upload your bot files: Drag & drop your main.py (or bot.py) and .env file — but wait! ⚠️ Don’t commit raw tokens to Replit’s file system. Instead:
    • Go to Secrets (shield icon in the left sidebar)
    • Add DISCORD_TOKEN = your_actual_bot_token_here
  4. Modify your code to read the token safely: 
    import os
import discord
from discord.ext import commands

TOKEN = os.getenv("DISCORD_TOKEN")

bot = commands.Bot(command_prefix="!", intents=discord.Intents.all())

@bot.event
async def on_ready():
    print(f"✅ {bot.user} is online and ready!")

bot.run(TOKEN)
  5. Prevent sleep: Replit free instances sleep after 5 minutes of inactivity — but you can ping your repl every 5 minutes using UptimeRobot (free plan). Create a simple /health endpoint with Flask (add flask to pip), then configure UptimeRobot to GET it every 4.5 mins.

💡 Pro tip: Use keep_alive() (a lightweight Flask server) alongside your bot in the same repl — many developers combine both in one script. DiscordCraft’s Replit Bot Starter Template includes this preconfigured.

[Image: Replit interface showing Secrets tab and Shell with pip install command]

✅ Method 2: Railway — Powerful Free Tier (No CC Needed)

Railway.app offers $5/month in free credits — no credit card required to start. You get ~500 hours/month of compute (enough for one small bot 24/7), PostgreSQL, Redis, and seamless GitHub integration.

Setup Steps

  1. Sign in with GitHub (no email/password or card).
  2. Click “New Project” → “Deploy from GitHub” → connect your bot repo.
  3. In your repo, ensure you have:
    • A requirements.txt file (discord.py==2.3.2)
    • A Procfile (create it in root): 
      web: python main.py
    • A .env file only locally — never commit it! Instead, set environment variables in Railway’s dashboard under Variables.
  4. Set DISCORD_TOKEN in Railway’s Variables UI (🔒 secret toggle ON).
  5. Click “Deploy”. Railway auto-builds and launches your service.

✅ Railway automatically restarts crashed processes and scales to zero only after 15 mins of full inactivity — unlike Replit, it won’t sleep mid-session. Your bot stays connected unless Discord temporarily rate-limits or your code throws an unhandled exception.

✅ Method 3: GitHub Codespaces — Dev-Friendly & Secure

Codespaces gives you a full VS Code–powered Linux dev environment in the browser — and yes, it’s free for 60 active hours/month (more with GitHub Student Pack). While not designed as a production host, it works brilliantly for low-traffic bots when paired with a simple keep-alive script.

How to Run Your Bot There

  1. Open your bot repo on GitHub → click “Code” → “Open with Codespaces” → “Create codespace”.
  2. In the terminal, install dependencies: 
    pip install -r requirements.txt
  3. Set your token securely: 
    echo "DISCORD_TOKEN=your_token_here" >> ~/.bashrc && source ~/.bashrc
    (Never store tokens in plaintext files!)
  4. Launch your bot in the background using nohup: 
    nohup python main.py > bot.log 2>&1 &
  5. To prevent timeout: open a second terminal tab and run while true; do sleep 300; printf '.'; done — this keeps the session alive.

⚠️ Note: Codespaces auto-suspend after 30 mins of inactivity unless you’re actively connected. For true 24/7, pair it with a cron job via GitHub Actions (see Pro Tips below).

🔐 Critical Security & Stability Best Practices

A bot online 24/7 is useless if it’s insecure or unreliable. Here’s what top developers do:

  • Never hardcode tokens — always use environment variables or secrets managers.
  • Add error handling & auto-reconnect logic: 
    @bot.event
async def on_error(event, *args, **kwargs):
    print(f"❌ Error in {event}: {args}")
  • Use discord.py’s built-in reconnect: bot.run(token, reconnect=True) (default since v2.0).
  • Log uptime & errors to a file or service like Sentry (free tier available).
  • Validate intents in your Discord Developer Portal — mismatched intents cause silent disconnects.

Also: rotate your bot token regularly (Settings → Bot → Reset Token), especially after sharing code publicly.

🚀 Quick Tips for Maximum Uptime

  • ✅ Test locally first: Use ngrok or localtunnel to verify slash commands/webhooks before deploying.
  • ✅ Add a /ping command so you can manually verify liveness.
  • ✅ Monitor with uptime bots: Invite UptimeRobot or use DiscordCraft’s free Bot Health Dashboard to track response time and disconnect events.
  • ✅ Use asyncio.sleep() instead of time.sleep() — blocking calls crash event loops.
  • ✅ Set intents.message_content = True only if needed, and enable it in your Discord app settings — missing this is the #1 cause of AttributeError: 'NoneType' object has no attribute 'content'.

❓ FAQ: Your Top Questions Answered

Q: Will Replit/Railway ban me for running a bot 24/7?
A: No — all three platforms explicitly allow long-running processes for bots, scrapers, and automation, as long as you stay within fair-use limits (e.g., <1GB RAM, no crypto mining).

Q: Can I host multiple bots on one free plan?
A: Yes — but be mindful of resource limits. Railway lets you run multiple services in one project; Replit requires separate repls (still free). GitHub Codespaces counts total hours across all spaces.

Q: What if my bot gets rate-limited or banned?
A: That’s almost always due to excessive API calls (e.g., sending 100 embeds/sec). Use @commands.cooldown() and respect Discord’s API rate limits. DiscordCraft’s Rate Limit Cheatsheet breaks this down visually.

Q: Do I need a verified Discord account or server?
A: No — but your bot must be added to a server with bot scope and proper permissions. Use OAuth2 URL generator tools (like DiscordCraft’s OAuth2 Builder) to avoid permission errors.

Final Thoughts: You’ve Got This! 🌟

Keeping your Discord bot online 24/7 for free isn’t magic — it’s about choosing the right tool, configuring it carefully, and following reliability fundamentals. Whether you pick Replit for speed, Railway for scalability, or Codespaces for development flow, you now have everything you need to launch confidently.

Remember: uptime is just the foundation. What makes your bot truly valuable is how well it serves your community — whether that’s auto-moderating spam, playing nostalgic tunes, or rolling epic D&D dice. 🎲✨

And if you ever hit a wall? The DiscordCraft Community Server is packed with friendly devs who’ll help debug your on_ready() handler — no judgment, no credit cards, just good vibes and better bots.

Happy coding — and may your WebSocket stay forever open! 🌐⚡