Renzom — how everything works

Renzom sells game server hosting: you choose a game, RAM, and player slots, pay online, and get access to a control panel where you start the server, upload files, and invite friends.

The marketing site (renzom.com) is where you browse games and prices. After purchase, order status lives in your customer panel. The actual game console and file manager live in the game panel (e.g. Pterodactyl) once your server is ready.

Create an account or sign in via the customer panel when ordering requires it — use an email you can access; Stripe receipts and linking orders to your panel rely on the same address.

Open the Games hub, pick a title, then go to Pricing and choose RAM and slots that match how you play.

Pay with the checkout shown on renzom.com (Stripe when enabled). After payment, keep the customer panel open: status moves from pending to ready when setup finishes.

When status is ready, use the link to your game panel to start the server, set a password or whitelist, and connect from the game client.

Each game page lists what we host today and what is planned. Cover art may be abstract until publisher-approved assets are available.

Requirements (mods, slots, RAM) vary by title. If you are unsure, ask on Discord before buying — we will tell you what is realistic for your mod pack or player count.

Plans show RAM, slots, and a monthly price. The price you confirm at checkout is what matters for your order.

Checkout happens on renzom.com with Stripe when configured. Invoices, cards, and subscription changes are handled in Stripe’s customer portal or emails from Stripe — not inside the game panel.

If a legacy external billing URL is enabled for your deployment, still use the same email as in the Renzom panel so orders can be matched automatically.

After sign-in you see your profile, shortcuts to support, and a list of orders linked to your account.

Use the header menu for Dashboard (this home), plans/pricing, game-panel help, and support. Admins see an extra admin entry when configured.

The panel is not the place to edit world files or run console commands — that is the game panel after the server exists.

Use panel.renzom.com to sign in. If you forgot your password, start from "Forgot password" and complete the reset link sent to your email.

If 2FA is enabled, you must enter either the current authenticator token or one of your recovery codes. Keep recovery codes offline and never share them in Discord.

New rows appear when a payment or webhook creates a hosting order tied to your email. Pending means automation is still installing or configuring the instance.

If pending lasts more than a few minutes, refresh the page, check spam for onboarding mail, then open a support ticket with your order reference from Stripe.

Failed means a human-readable error was stored — follow the hint on the row or contact support with the reference shown.

The game panel is the product you bought: power buttons, console, SFTP, schedules, and backups (if exposed by the egg and provider).

Each game uses an egg with Docker image, startup command, and variables. Plan RAM and slots are mapped into those limits where the egg supports it.

Mods, plugins, and worlds are usually installed from the game panel or via SFTP — not from the marketing pages.

Loader changes are done in the game panel and can trigger a reinstall workflow depending on your current setup. Always keep a backup before switching.

If switching fails, check the panel error message and then open support with your server id and timestamp. Technical backend errors can be traced quickly with that information.

Join discord.gg/renzom (or the invite shown in the site header) for announcements, quick questions, and community help.

Discord is great for informal troubleshooting; it is not a replacement for legal notices or formal account disputes — use email for those.

For account-related or formal topics, use the contact email published on the site. Include your panel email and any Stripe payment reference.

The support section of the panel may offer tickets when enabled — use that for issues tied to a specific order or server ID shown in your list.

Successful checkouts create Stripe objects you manage in the customer portal: payment methods, receipts, and cancellation rules follow Stripe’s UI.

To upgrade RAM or add another game server, start a new purchase from the pricing page unless your host documents a different upgrade path.

Cannot sign in: try a private window, clear cookies for this domain, and confirm Google OAuth redirect URLs match production (AUTH_URL, Google Cloud console).

Order missing in panel: verify the checkout email matches the account email; mismatches are the most common cause.

Game will not start: read the console in the game panel, verify ports and firewall rules, and check disk quota — then ask in Discord with screenshots.

Loader switch fails: verify the selected loader is configured for your panel and retry once; if it still fails, send the exact time and server id to support.

Egg — Pterodactyl template for a game (image, variables, install script).

Node — physical or virtual machine that runs your container.

External ref — internal idempotency key linking a payment to one server row.

Live state — optional poll of the game panel’s reported status for a ready server.