Skip to content
CitexNode

Discord bots

Your bot keeps running once your machine is off

Point us at a repo, set the token, hit start. The bot no longer depends on your wifi or on a Raspberry Pi under the desk.

Start for freePricing

Ready to launch

  • node20
  • python312
  • java21

From repo to running bot

  1. Give us a repo or upload files

    On creation you enter a git URL and we clone it once onto the node. Without a repo you upload your code in the file manager.

    A later push does not deploy by itself. Shipping a new build means replacing the files.

  2. Token as an environment variable

    You set DISCORD_TOKEN and everything else in the dashboard. The values go into the database encrypted and reach the node only at start.

  3. Start, no configuration

    The template brings its own start command. You press start, we handle the process, restarts and limits.

  4. Follow the logs

    The stream shows stdout and stderr live, with history. Reading yes, typing no: a bot has no interactive console.

Your tokens stay encrypted

Every environment variable is stored sealed. No endpoint returns it in plaintext, not even to you: you can overwrite a value but never read it back. A database leak on our side would not be a token leak on yours.

  • Encrypted in the database, decrypted only at start
  • Not in lists, not in logs, not in a support ticket
  • Overwrite any time, read back never

Logs while they happen

No reload, no download. The stream runs as long as the page is open and shows you the crash exactly when it happens.

2026-08-18T21:04:11Z  info   logged in as CitexBot#4417
2026-08-18T21:04:11Z  info   serving 3 guilds
2026-08-18T21:07:52Z  warn   rate limited on /channels, retry in 1.2s
2026-08-18T21:07:53Z  info   command /ping handled in 41ms

Get your bot online

Create an account, upload the code, set the token, hit start. The rest is our problem.

Start for free