Start, stop, restart and manage everyday server controls from the game panel.
The full server stack.
Runic Hosting is building the boring-but-important hosting tools too: off-node backups, memorable addresses, subusers, schedules, metrics, safe upgrades, trial access, shared payments and a clear path for deeper server management after launch.
Automatic production backups are designed to leave the game node instead of living beside the workload they protect.
Move an existing world or save where the game supports portable data and Runic Hosting has validated the path.
Minecraft is first priority; supported mod, plugin and Workshop workflows are validated game by game.
Troubleshooting starts with the game, version, recent changes and relevant logs.
Invoices, renewals, RAM changes and service lifecycle stay authoritative in Paymenter.
Player count and workload affect the RAM recommendation instead of RAM being guessed in isolation.
One eligible shared-server trial can run without a payment method. Unconverted trials suspend at 24 hours and cancel at 48.
DDoS protection included on all IPs
What has to work before paid hosting is ready.
These are commitments for the paid-launch build, not claims that the current preview already has a live node behind it. Each item stays a launch gate until the real VPS, Paymenter, Pterodactyl, Wings and storage path are connected and tested.
A defined resource allocation instead of an uncapped-memory label. Owner: Paymenter + capacity gate + Pterodactyl.
Change RAM without opening a provisioning ticket. Owner: Paymenter + capacity gate + Pterodactyl.
Know the storage included with the service and when an expansion is needed. Owner: Capacity policy + Pterodactyl.
Direct access to the server instead of waiting on support for routine file work. Owner: Pterodactyl.
Automate routine restarts and supported recurring server jobs. Owner: Pterodactyl.
A node-disk failure does not automatically take the recovery copy with it. Owner: Pterodactyl + S3-compatible storage.
Take a safety copy before updates, download a portable copy where supported and restore without a support ticket. Owner: Pterodactyl + S3-compatible storage.
Bring an existing compatible world instead of starting over. Owner: Runic support + SFTP / panel.
Share a memorable hostname instead of only an IP address. Owner: Runic DNS automation.
Common customization should not require hand-building every server. Owner: Pterodactyl + validated game workflows.
Give a co-admin only the access they actually need. Owner: Pterodactyl.
See whether the server is actually under load before guessing at an upgrade. Owner: Pterodactyl + Runic read-only summaries.
Run supported plugins/mods that need a database without sourcing one elsewhere. Owner: Pterodactyl database hosts.
See exactly what is happening after purchase instead of wondering whether the order is stuck. Owner: Paymenter + Pterodactyl + Wings + Runic.
Choose a location using measured latency and real availability rather than a vague region list. Owner: Runic storefront + production capacity data.
Solve common setup and troubleshooting tasks without waiting for a ticket response. Owner: Runic support content.
Attach useful troubleshooting context to a ticket without manually hunting through every log, and get a plain-language read on what likely broke and the safe next step. Owner: Runic support + read-only server telemetry.
Protect billing and server-control access beyond a password alone. Owner: Paymenter / Pterodactyl / staff auth.
Test the real server before committing payment information. Owner: Paymenter extension + Pterodactyl.
Friends can help fund a shared world without sharing the billing account. Owner: Paymenter extension.
The quality-of-life layer does not stop at launch.
These are the competitor-parity and differentiation features planned after the core paid-hosting lifecycle is stable. They are intentionally not presented as live launch features.
Check or restart a server from Discord without exposing dangerous actions. Owner: Runic integration + Pterodactyl.
Handle common player administration without memorizing every server command. Owner: Runic game-specific tooling.
See what changed and when instead of troubleshooting blind. Owner: Runic read-only event mirror.
Change common server settings from a safe form instead of hand-editing raw configuration files. Owner: Runic settings engine + Pterodactyl file access.
Maintain separate vanilla, modded or alternate-world setups without destroying the previous one. Owner: Runic orchestration + Pterodactyl storage.
Repurpose a service without treating the old world as disposable. Owner: Runic orchestration + Paymenter + Pterodactyl.
Console, files, backups and schedules should feel like one product.
The panel is where the server lives. Runic Hosting keeps billing in Paymenter and server control in Pterodactyl instead of creating a second half-working control panel.
[INFO] Starting game server...[INFO] Server is ready for connections[INFO] Player joined the game[INFO] Automatic off-node backup queued...Browser files plus SFTP.
Use the panel for quick edits or SFTP when you need to move larger world, configuration or supported server files directly.
Backups belong away from the game disk.
The production design uses independent S3-compatible storage so a game-node disk failure does not automatically destroy the recovery copy too.
owner + scoped subuserSeparate permissions instead of shared passwords.Give people only what they need.
Panel subusers and 2FA are part of the launch-security target. Contributors to an invoice never receive server access automatically.
Clear limits are part of the product.
Runic Hosting assigns a defined RAM amount to each shared service. Shared hardware still has finite capacity, so we would rather stop selling when safe capacity is gone than rely on an unlimited-sounding memory label.
Production recovery is designed around off-node storage and tested restores, but customers should still keep independent copies of irreplaceable worlds and saves.
A mod or plugin can be outdated, conflict with another component or change resource use. Runic Hosting only advertises a workflow after testing it.
The launch network includes DDoS protection, but filtering or temporary disruption can still occur during large or unusual attacks.
Contributing money toward another customer’s invoice does not grant account ownership, server ownership, SFTP access, panel rights or refund control over that service.
Panel access for friends or staff uses individual scoped permissions rather than shared owner credentials.
Runic Hosting will not make a switch-game button that blindly overwrites a world. The post-launch design requires a safety snapshot and favors saved instances.
Status and safe power actions can be convenient in Discord. Wipe, reinstall, delete and billing actions stay inside authenticated management surfaces.
One source of truth per job.
Games, builder, customer summaries, safe integration surfaces and service information.
Orders, invoices, recurring service, PayPal, trial conversion, RAM billing changes and provisioning trigger. Split-cost contributions are implemented here rather than in a second billing database.
Console, files, SFTP, backups, schedules, settings, power actions, databases and scoped panel subusers.
Wings executes isolated game workloads on the dedicated node. Independent object storage holds production recovery copies.
Los Angeles, CA
1 Gbps unmetered · Up to 10 Gbps port · DDoS protection included on all IPs. Machine-level specifications are not published on the storefront.
Get the checkout email when hosting opens.
Pricing and the Los Angeles launch location are published now. Join for the checkout email and supported-game updates. No payment details are collected here.