The RAM solution for Minecraft servers. Blink puts a server to sleep when nobody plays and gives its memory back; when someone joins, they are back in the world within a second. Paper, Fabric, Forge or vanilla: for a server with friends, a server at home, or a whole BungeeCord or Velocity network.
Measured on our server (6 vCPU VPS, Paper 26.3). Yours depends on your hardware; the scripts to measure it are in the repo.
A Minecraft server only has to run while someone is playing. The rest of the day it keeps gigabytes of RAM and ticks an empty world for nobody. Blink puts it to sleep in those hours and wakes it the moment a player joins: nobody notices, and the memory and CPU are free for everything else.
You play a few hours in the evening; the server sits there the other 21 hours, holding gigabytes. With Blink it saves and freezes 30 seconds after the last player leaves, and wakes up the moment someone joins. A smaller VPS does the job, or the same one runs more.
Green: awake while you play. Blue: asleep, 0 % CPU, a few MB of RAM.
An empty Minecraft server still ticks all day and keeps its memory. Frozen, it uses no CPU at all and hands its RAM to your games, browser and everything else: Windows and macOS compress it and give it back when someone joins. Linux, macOS and Windows, no admin rights needed.
| Process | CPU | Memory |
|---|---|---|
| Your game | 18 % | 4.1 GB |
| Browser | 3 % | 1.6 GB |
| Minecraft server (asleep) | 0 % | compressed |
| Blink | 0 % | 1.5 MB |
Lobby, survival, creative, minigames: put a Blink in front of each backend server. Only the servers people are on stay awake. A player who types /server survival wakes it up and is in the world in about a second; the proxy just sees a server that answers.
Personal worlds, private islands, event maps, a test server per builder: give everyone their own server without paying for all of them all day. A world sleeps until its owner comes back, then it is there in a blink, exactly as they left it.
Run servers for friends, a community or customers? Sleeping servers take a fraction of their memory, so one machine fits far more servers that are rarely full at the same time. Try your own numbers:
Average over a day, 7 MB per sleeping server after 10 minutes (our measurement). When everyone plays at once you still need the full amount.
A sleeping server is not only cheaper. An empty Paper server still ticks 20 times a second, all day: we measured about 3 % of a CPU core for an empty world. Frozen, it uses nothing. And the bigger win is for hosts: servers are packed onto machines by RAM, and a server asleep for 10 minutes needs 7 MB instead of 3 GB, so the same players need far fewer machines running day and night.
An estimate, not a promise: real hosts differ in machines, power and how players spread over the day. The one thing we measured ourselves: 3 GB to 7 MB per sleeping server, and 3 % of a core to 0.
Blink, one small program, owns the public port. The server list, the MOTD and the icon always answer, and a join is let through as soon as the server is there.
A normal Paper server. Blink only passes on the connection, with the players' real IPs.
30 seconds after the last player leaves, the server saves and is paused. Its memory is compressed, and after 10 minutes moved to disk: 7 MB. A join continues it.
After a reboot, an update or a day frozen, the server starts from scratch: Paper with Java's AOT cache, in a few seconds.
Wake: from clicking Join until the player is in the world (the server itself takes the join after 0.1 to 0.4 s). After 10 minutes asleep the memory comes back from the swap file: about 3 s. Proxy: one BungeeCord or Velocity with five servers, real logins. Cold start: Paper with Java 26.
Blink is built on lazymc by Tim Visée. Same machine, same Paper 26.3 server; lazymc 0.2.11 is its latest release.
A paused JVM keeps all its state, so waking it is instant. Blink saves first and moves the paused server's memory out of RAM: compressed at first (back in under a second), to disk after 10 minutes: 7 MB instead of 3 GB.
Paper's launcher loads the server in its own class loader, which Java's AOT cache can't store. Blink starts the server directly.
On Java 25 Minecraft's method type table is too big for the cache; Java 26's streamable AOT objects make the full cache fit. 13 s becomes 4 s.
1.5 MB of RAM instead of 5.7 MB, one static file, about 1 GB/s of player traffic on one thread.
One command. Stop your server, make a backup, go to its folder (paper.jar, a Fabric or vanilla jar, or Forge's run script) and paste this:
curl -fsSL https://raw.githubusercontent.com/kylianxdev/blinkmc/main/install.sh | sudo bashCopy
Full install: a service, plus swap and zswap so a sleeping server leaves RAM. Needs root.
Players join on the same address as always. Your world stays as it is; Blink moves the server to a port of its own and raises Paper's watchdog (everything it changes), and blink restore or --uninstall puts it back. Read the installer first? install.sh, install.ps1. Networks: a Blink per backend server, see the README.
No. It is a normal Minecraft server for them. The only thing they may notice is a different MOTD while the server sleeps.
Yes: a Blink in front of each backend server. Tested with one proxy, a lobby and four personal worlds, with bots that log in and switch: 0.3 to 1.7 s to a sleeping world (about 3 s on the first visit after a server restart), and five sleeping servers use about 1 GB together.
Blink saves the world (save-all flush) before every freeze and checks that nobody joined meanwhile. Stopping it thaws the server first and lets it save and shut down normally. Nothing in your world is changed. Still: try it with a fresh backup first.
The server's port in server.properties (Blink takes yours, the server moves behind it), Paper's watchdog and its PROXY protocol setting, and on Linux with the full install a service, swap and zswap. blink restore puts back only what Blink set, --uninstall removes the rest. The full list.
No. Your server needs the Java its Minecraft version needs. Java 26 makes a cold start of Paper fast (4 s instead of 13, with Java's AOT cache); waking a frozen server is just as fast on any Java.
No. Without one anyone can wake the server, also new players; a bot that does only keeps it awake until the next freeze. With the whitelist on, only whitelisted players can wake it.
Only the full Linux install: a service, a swap file and zswap. The portable install (Linux, macOS) and the Windows install change nothing outside your server folder.
Blink runs next to your server, so you need a machine where you can run your own programs: a VPS, a dedicated server or your own PC. Most shared Minecraft hosting plans don't allow that.
Once a day it downloads a 1 byte file from Blink's GitHub releases; GitHub counts the downloads. Nothing is sent. Off with usage_stats = false or DO_NOT_TRACK=1.
Yes. blink init and the installers recognise Paper, Purpur, Fabric, Quilt, Forge, NeoForge and vanilla, and sleeping works the same for all of them. The fast cold start (Java's AOT cache) is for Paper and its forks; real player IPs need a PROXY protocol mod on Fabric and Forge.