Build a free Minecraft launcher with a web panel

Within the CentralCorp ecosystem, CentralCorp Launcher, CentralCorp Panel and CentralCorp Installer are available without a recurring CentralCorp software subscription. This guide explains what free Minecraft launcher software means in this ecosystem, which infrastructure may still cost money, and which license applies to each component.

Start the installation · Explore the Minecraft Launcher Panel

Software available without a subscription

The public repositories provide four connected parts:

• installation and configuration documentation;
• the customizable Electron launcher used by players;
• the self-hosted Laravel administration panel;
• the installer that checks hosting and downloads a panel release.

CentralCorp does not charge a recurring software subscription to download and self-host these repositories.

Infrastructure may still cost money

Free software does not mean cost-free infrastructure. The documented setup needs an Azuriom website and, for the standalone panel, separate compatible PHP hosting, a database, storage and a domain or subdomain. You may already own those resources or pay a hosting provider for them.

The CentralCorp Azuriom plugin and other third-party services may also have their own prices. Those costs are separate from the CentralCorp repositories.

Licenses differ by component

CentralCorp Launcher uses CC BY-NC 4.0. Its source code is available, but the license restricts commercial use and requires attribution. For that reason, the complete CentralCorp ecosystem should not be described as “100% open source.”

The panel is released under CC0 and the installer under MIT. The documentation repository currently has no license file. Always review the license text for the exact component you plan to use.

A self-hosted Minecraft launcher panel

CentralCorp Panel can run on compatible hosting you control without a CentralCorp panel subscription. You select the database, domain, file storage, backups and update process.

That control comes with operational responsibility: you maintain PHP, the database, HTTPS, backups and the security of the hosting environment.

Launcher customization

The desktop application identity is configured in your launcher fork before building. Routine settings come from the web panel, including the Minecraft version, Forge or Fabric loader, memory defaults, game directory, server, UI, maintenance, access lists, files and optional mods.

Use the launcher configuration guide and application preview to plan those changes.

Azuriom, Forge and Fabric

Player authentication relies on Azuriom. The panel also synchronizes servers, roles and users through its configured API. Administrators can select Forge or Fabric for a Minecraft version and pass that loader configuration to the launcher.

The current launcher targets offline-mode Minecraft servers connected to Azuriom. Microsoft online-mode servers are not supported.

Files, mods and updates

The panel file manager generates a manifest the launcher uses to verify and download game data. Mods can be documented and marked as optional for players. New launcher releases are generated by the GitHub workflow and consumed by the Electron update mechanism.

Create your launcher step by step

1. Prepare development tools and hosting.
2. Fork the launcher source code.
3. Configure the application and panel URL.
4. Install the self-hosted panel.
5. Configure Azuriom, files and mods.
6. Build the launcher distributions.

Frequently asked questions

Is CentralCorp completely free?

That wording would be misleading. CentralCorp does not require a recurring software subscription, but hosting and third-party services may cost money.

Can I use the launcher commercially?

The launcher's CC BY-NC 4.0 license restricts commercial use. Review the license and obtain appropriate guidance or permission for your specific situation.

Is the panel self-hosted?

Yes. CentralCorp Panel is designed to run on compatible web hosting administered by the operator.

Is the source code available?

Yes. The component repositories are public in the CentralCorp GitHub organization, under different licenses.