Pelican Panel is an open-source game server management platform that enables gaming communities and hosting providers to deploy, configure, and operate multiplayer servers for titles like Minecraft, Palworld, and Counter-Strike within secure, containerized environments. Administrators can provision dedicated game servers in seconds using modular configuration eggs, allocating precise CPU cores, memory thresholds, and disk quotas to prevent resource contention across noisy neighbors. Players and server operators access an interactive web console featuring live terminal output, instant power state toggles, and direct command execution over secure WebSockets. An integrated file browser enables operators to upload server modifications, edit configuration scripts with syntax highlighting, and decompress archives without opening an external terminal. Built-in scheduling pipelines automate recurring tasks such as world backups, daily server restarts, and mod updates based on custom cron expressions. Multi-tenant permission controls allow guild leaders to invite co-administrators and grant granular privileges for restarting daemons, reviewing console logs, or managing database credentials without exposing the host system. Operators can also provision external SFTP endpoints, attach secondary IP allocations, and trigger webhook alerts whenever container health anomalies occur. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.

Picture your object storage scattered across a home server, a friend's rack, and a cheap VPS in another country, still answering S3 requests like nothing happened: that is exactly the deployment Garage was built for. Every object is replicated to three zones, so losing a node, a disk, or an entire site degrades the cluster instead of destroying your data. Applications talk to it with the standard S3 API: create buckets, upload objects in multiple parts, list and copy them, and hand out access keys that are scoped per bucket. A separate web endpoint serves static websites straight from buckets with CORS support, which covers personal sites, documentation, and release downloads without another server in the chain. The whole system ships as one dependency-free binary that asks for about a gigabyte of RAM and any x86-64 or ARM CPU from the last decade, second-hand hardware very much included. There is deliberately no consensus protocol to babysit: nodes gossip their cluster layout, tolerate 200-millisecond links, and keep serving reads while parts of the fleet are unreachable. Deuxfleurs runs it in production for their own hosting, and common pairings include restic or rclone backup targets, Matrix media storage, and Nix binary caches. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.