Questions, answered plainly

It depends on the plan, and every figure is printed on the plan before you pay. Frost is half off at $2.50, Snowfall 45% at $4.40, Drift 35% at $7.80, Glacier 30% at $11.90. Bots run 50% on Flurry, 35% on Whiteout, 25% on the two above it. It applies once, to your first server, and the renewal price is the one shown struck through. Flurry also has a seven-day free trial instead, if you would rather pay nothing up front: it needs a card, and it becomes a normal $3 a month subscription on day eight unless you cancel first.

The seven-day free trial on Flurry, for a Discord bot. It is the real thing, on the same machine as every other bot, with the full console and file manager. Nothing is charged for seven days, and cancelling before then costs nothing. If you would rather skip the trial, Flurry's first month is $1.50.

Today, Discord bots written in Python, JavaScript or Java, from $3 a month. The bot page has the plans. Minecraft servers are planned and the prices are published, but they are not on sale yet. Websites we do not offer, and have not built. If you are unsure whether what you want to run fits, ask us and we will tell you honestly.

Both. The company is Snow Servers and the domain is snowservers.com, written as one word because that is how domains work. You will see it spelled either way and they are the same people. If you are searching for us, snowservers.com always gets you here.

Yes, either way, and for bot plans you can do it yourself: ask for the billing email on the billing page and use its change plan link. You see what is due before confirming, and the server you already have gets the new limits straight away, so your files, settings and address all stay put. Moving up charges the difference for the rest of the period; moving down leaves a credit. Only catch going down is that your files have to fit in the smaller plan.

It runs to the end of the period you already paid for, then stops. Nothing is deleted straight away, so you get time to download your files and backups first.

Because it is the thing that decides whether your world feels smooth. Twenty times a second your server has to update everything at once, and it gets 50 milliseconds to do it. Miss that and you get the skating mobs and the hits that do not land. Extra memory cannot give that time back. A quicker processor can.

It does, just differently. Too little and your server stalls or crashes outright, and big modpacks genuinely need plenty. But once you have enough, more does nothing for smoothness. So we give each plan enough for what it is meant to run, and spend the rest on speed.

It depends which limit you hit, and the honest answers differ.

Memory: the kernel kills the server and it restarts. The limit is enforced by cgroups on the container, not by a setting inside the game, so raising -Xmx past your plan does not get you more memory, it just gets you killed sooner. The crash is in your console rather than hidden, and repeated ones usually mean a modpack that wants a bigger plan.

Processor: nothing is killed. You are throttled to your share, so the server keeps running and the tick rate drops. This is the one that feels like lag rather than a crash.

Storage: writes start failing and the server usually notices before you do. Clear old backups and world backups first; ask us if it is not obvious what grew.

None of this spills onto anybody else, which is the point of the ceiling. It is also why we would rather move you up a plan than let you sit against it.

Yes, at the network rather than from us. Traffic crosses our host's network before it reaches the machine, and volumetric floods get dropped there, which is where they have to be dropped — filtering a flood after it has already used up your connection does nothing. That filtering is standard at a serious datacentre and it is one of the reasons we use one.

What we will not claim: an attack aimed specifically at your game server, from inside the protocol rather than at raw volume, is a different problem, and no host solves that for you with a network filter. Keep your address private if it matters, use a domain you can repoint, and tell us if something looks targeted.

As many as you set. We do not cap slots, and nothing in our system counts your players. New servers start at 500 slots in server.properties, which you can change in Game settings; Minecraft's own default is 20, which is why we set it rather than leave it.

What actually limits it is the server: memory decides how much world and how many mods load at once, and processor decides how many people can move around in it before the tick rate suffers. Plain survival fits far more people than a heavy modpack on the same size.

Both, in the way every host that says 'unmetered' means it. There is no storage size you pay for and no charge for using more, and the number in the panel is a technical ceiling set well above what servers normally use. Reach it, ask us, and we raise it for free when the space is your server's own files. What it is there for is one server quietly filling the machine and taking everyone else down with it. The rule is written out in clause 5 of the terms.

Yes, if it is written in Python (3.10 to 3.14), JavaScript (Node.js 20, 22 or 24) or Java (17, 21 or 25). Always on, restarted if it crashes. Plans start at $3 a month for 1 GB, and Flurry is free for seven days. The bot page has the plans.

Deploy it from GitHub by pasting the repository link into the control panel, or upload it through the file manager or over SFTP. Packages install from requirements.txt or package.json. The first-bot walkthrough covers it step by step.

In the control panel, on your server's Startup tab, in the BOT_TOKEN box. Your code reads it with os.environ["BOT_TOKEN"] or process.env.BOT_TOKEN. Do not paste it into your code: anything in your files ends up in every backup and anything you share for help. More on keeping it safe.

Yes. Every plan includes a MySQL database of up to 1 GB on the same machine as your bot, copied into your server's files every night so your backups carry it. For most bots SQLite in the bot's own folder is simpler and works just as well. Using your MySQL database.

It restarts on its own, the console explains the usual causes in plain words, and it can message you in Discord with the reason. A bot that dies quietly at 3am and is still dead at lunchtime is the thing people are paying to avoid.

Yes. Put each extra bot in its own folder inside bots, with its token in a .env file there, and restart. They run side by side on the plan's memory, each with its own packages, and one bot crashing does not stop the others. Running several bots on one server.

Yes, some of them in one step. The panel has a Bot library tab with open-source bots ready to set up: Discord Tickets, Modmail and Red. You fill in the token and a couple of IDs and it is installed on the next restart, in its own folder, alongside anything else you run. How the Bot library works.

Ask us. The plan is a Python, Node.js or Java process that stays running, so a scheduled task or a small worker fits fine. Each server has a public port for webhooks or a small dashboard over plain HTTP; web hosting with your own domain and HTTPS we do not offer.

On Drift and Glacier you can split the plan across more servers: Drift up to 2, Glacier up to 3. A proxy, a lobby and a survival world, say, without buying three plans. Open the Sub-servers tab in the panel, pick a name, a type and how much memory, CPU and disk it gets, and it is built in about a minute with its own console, files and port.

Nothing is added to the plan: whatever a sub-server gets, your main server gives up, and the main server always keeps at least 2 GB of memory and 1 vCPU. Taking memory from a running server restarts it, because Minecraft only sizes its memory at start. Each sub-server keeps one backup; the main server keeps three. Suspending or cancelling the plan applies to its sub-servers too.

Paper, Purpur, Fabric, NeoForge, Forge or Vanilla, at any version they support, picked on the panel's Software tab. The same tab installs a modpack from Modrinth in one click. Proxies such as Velocity or BungeeCord we set up on request, usually the same day. You can also upload a server jar yourself and run it.

Yes, from the panel's Mods & plugins tab. It searches Modrinth for plugins if the server runs Paper or Purpur, or mods for Fabric, Forge, NeoForge or a modpack, already filtered to your Minecraft version. Pick one and it is added with anything it needs; it loads the next time the server starts. Anything not on Modrinth you can upload to the plugins or mods folder in Files.

Yes. A live console with full command input, a browser file manager, and SFTP credentials. You can edit any config, tail logs, and upload or download whatever you need. Nothing is hidden behind a support ticket.

You can look round the panel before paying: the demo login opens a real server, read-only.

Yes, and most people do. Drag the world folder into the file manager, or push it over SFTP if it is large, then point the server at it and start. Plugin and mod folders come across the same way. If your current host will only give you a zip, upload the zip and unpack it in the file manager. Nothing here is a one-way door: you can take the whole thing out again the same way, whenever you like.

Yes, and it is worth doing. Point your domain at the address we give you and people join at something like play.yourname.com instead of a string of numbers.

Your whole world is copied once a day, automatically, on every plan, and the last three copies are kept. Rolling back is a single click and takes seconds, griefed spawn, bad plugin update, an experiment that went sideways, all fixable before anyone logs off. You can also take a backup yourself any time, and download it whenever you like.

Yes, one on every plan, up to 1 GB, for plugins that can use MySQL such as LuckPerms or CoreProtect. Create it on the Databases tab in the panel and copy the details into the plugin's config. It can only be reached from servers here, your sub-servers included, so a small network can share it. How the database works.

It is contained, but we will not pretend it is caught. Your server runs in its own container with its own filesystem, so a bad plugin or package can wreck your server and reach nothing else on the machine and nobody else's files. Two things help: a weekly scan of server files for known malware, and network rules that stop any server sending email or reaching our private network. Neither catches something malicious written for the occasion, because no scanner has heard of it yet. Stick to Modrinth, SpigotMC, CurseForge and PyPI packages you recognise, and take a backup before installing something you are unsure about.

No. Your server has its own container and its own storage, so nobody else on the machine can read your files or reach your world. On the processor, every server runs under a hard ceiling it cannot exceed, which is what stops one busy world dragging down the rest, it is a cap on each server rather than a reserved share held empty for you.

No. Once a week a virus scanner checks server files against a list of known malware. That is software comparing fingerprints, not a person reading your code or your configs.

Discord bots run on a virtual server we rent in Vienna, Austria. The hardware page lists exactly what it is. The machine for Minecraft is not chosen yet and will be named there before it opens. Backups are taken daily and kept on the same machine for now; a second copy held somewhere else is built but not switched on yet.

Yes. Get your personal link any time from snowservers.com/refer; it is also in your welcome email. A friend who signs up with it gets 20% off their first 3 months. Once they have paid $3, and two weeks have passed, you get $3 of credit, which comes off your next bill automatically.

The small print, stated plainly: your friend must be new to SnowServers (one offer per person, card and Discord bot), a card is needed, a referral code cannot be combined with the free trial, you cannot use your own code or your own card, you earn credit once you have paid us yourself, a refunded or disputed payment takes the credit back, and each account can earn up to 10 credits.

Paid plans are charged through Stripe, on whichever term you pick: one month, six months at 10% off, or twelve months for the price of ten. Longer terms are paid in advance. Card details are handled entirely by Stripe and never touch our servers.

Yes. Tell us within seven days of your first payment and we refund it in full, no questions and no form, whatever the reason. After that, cancel any time and you are not charged again; there is no minimum term. If we break something and cannot fix it, we refund the affected period without you having to ask twice. The refund policy has the detail, including annual plans and the fourteen-day right to cancel in the UK and EU.

We retry and email you. Your server keeps running through a grace period rather than dying the instant a card expires. Only after that does it suspend, and it is still not deleted straight away.