Docs
How the panel works, how an app server deploys, and step-by-step tutorials for the games and software people run here.
Get started in the panel
The panel, screen by screen: ordering, the console, files, backups and the rest.
- Ordering a serverOrdering takes about a minute and happens in three screens: find what you want to run, pick a plan, and pay. Pay by card or PayPal and the server is set up the moment the payment goes through - you can watch it install in its console.
- The consoleLive output, a command line, power controls and the resource graphs. It is the server's own output rather than a filtered summary - if the game prints it, you see it.
- Files and SFTPA complete file manager with an editor in the browser, plus SFTP credentials for the tools you already use. Upload a modpack, fix a config, pull a world down to your machine.
- BackupsTake one before you try something. Restore it when the something goes wrong. Lock the ones that matter so they are not rotated away.
- DatabasesCreate a database from the panel and it comes with a host, a username and a password generated for it. Nothing is shared with anybody else's server.
- Subusers and teamsGive somebody the console without giving them your files, or the files without your billing. Three separate ideas, kept apart deliberately.
- Scheduled tasksRestart nightly, back up before the restart, announce it to players first. Tasks run in order with delays between them, so a schedule can be a small routine rather than one action.
- Git deploysFor application servers: connect a GitHub repository and branch, and the container pulls it on boot. Switch on deploy-on-push and it restarts itself when you push - and a stopped server is started, so the push goes live either way.
- Games needing a keyA few games want a credential their publisher issues to a person - a Steam game-server token, a Steam account that owns the server files, a Klei cluster token, a Cfx.re licence. We cannot create one and we never share one between customers.
Deploy an app
How an app server runs - the port, the folder, the boot order - and how to put your code on one.
- OverviewWhere your code lives, which port it must listen on, the order a server boots in, how GitHub deploys work, where .env goes and when a server restarts. The rules every RE:NODE app server follows.
- Node.jsHow a RE:NODE Node.js server starts your repository: the start script, the port from SERVER_PORT, Next.js, Vite and TypeScript builds, choosing the Node version, and the errors first deploys hit.
- PythonHow a RE:NODE Python server runs your code: the entry file on the Startup tab, requirements.txt, binding 0.0.0.0 on SERVER_PORT with a production server, and the errors first deploys hit.
- Static sites and web hostingHow RE:NODE web hosting serves your files: the web root, index.html at its root, committing built output, how GitHub deploys reach the folder, and why nothing is built or started.
- Discord and Telegram botsRun a Discord or Telegram bot on a RE:NODE Node.js or Python server: the start script or entry file, keeping the token out of git, surviving restarts, and why a bot needs no port.
- DatabasesThe two kinds of database on RE:NODE - database slots on app and web plans, and database hosting servers - where the host, port and password are shown, and how to connect from Node.js and Python without committing credentials.
- Custom domainsPut your own domain in front of a RE:NODE app or web server: the proxy slot, the A record, automatic certificates, Cloudflare settings, X-Forwarded-For, and why issuance fails.
- TroubleshootingWhy a RE:NODE server will not start, why its port cannot be reached, why the build is missing, why the wrong Node version runs, and why a push did not show up - with the fix for each.
- Using AI assistantsUse Claude, ChatGPT or any AI assistant to work on a RE:NODE server: the Connect AI link from the Console tab, connecting a whole account over MCP, what a Manage link may do, the pre-flight check, repository context, and what an assistant should know without the panel.
Tutorials
608 step-by-step guides for game servers, apps, databases and the web.
- Guides274
- Operations60
- Databases58
- Minecraft52
- App hosting49
- Networking35
- Sizing28
- Security21
- Web hosting20
- VDS11
Latest
Operations · 16 min readAI coding agents for server and DevOps work: help and harm
App hosting · 19 min readBun or Deno on a small server: which runtime to pick
Operations · 17 min readChoosing a hosting provider: what to look at, from the insideApp hosting · 18 min readDeploy a Go web service: net/http, chi and gin in productionAI setup
Working with Claude or ChatGPT?
Press Connect AI on your server and paste the private link: the assistant gets the runtime, port, code path, GitHub branch and databases - never a password or a token. Or connect Claude to your whole account.
Still stuck?
The questions asked most are answered in the FAQ, and a ticket reaches a person - most replies come the same day.