Free for public repositories

Push to GitHub,
get a jar and a page

FadeHost builds your Minecraft plugin or mod on every push and puts each build on a public page with its log and its jar. One link always downloads the newest build. No Jenkins to run, no Actions workflow to write, no release to cut.

One public repository per account, free. Already have an account? Open Builds in the panel.

Three steps, then it runs itself

1

Connect the repository

Sign in to the panel, open Builds and paste the GitHub URL of a public Gradle or Maven project. Connecting GitHub takes one click; the App only needs to read public code.

2

Push

Every push to the branch you chose compiles inside a capped container on FadeHost's build box: the right JDK, the wrapper your project ships, the dependency cache warm from last time. Or press Build now.

3

Share the page

Your project gets a public page listing every build with its commit, its log and its jar, plus a link that always downloads the newest one and a badge for the README.

What every project gets

๐Ÿ“„

A public build page

fadehost.com/builds/you/plugin lists every build, newest first, with status, commit, log and files. The Jenkins page every plugin used to need, without the Jenkins.

๐Ÿ”—

A link that never goes stale

One URL always serves the newest successful jar. Paste it once into your README, your Discord, your wiki, and never update it again.

๐Ÿท๏ธ

A README badge

build: passing, failing or building, rendered by us and cached by GitHub. Two lines of Markdown, copied from your page.

๐Ÿงพ

Full build logs

Every attempt keeps its log, so a contributor who broke the build sees why without asking you, and so do you from your phone.

๐Ÿ—‚๏ธ

Older builds stay

Every successful build keeps its files. A player on an older Minecraft version can still fetch the build that matched it.

๐Ÿ–ฑ๏ธ

Install into a server

FadeHost customers install any build straight into a server from the panel: the jar lands in plugins or mods, ready for the next restart.

Two lines in your README

The badge follows your newest build and the link always fetches the newest jar. Copy both from your project page; they never need updating.

[![Build](https://api.fadehost.com/api/public/builds/you/plugin/badge.svg)](https://fadehost.com/builds/you/plugin/)

[Download the latest build](https://api.fadehost.com/api/public/builds/you/plugin/latest/plugin.jar)

Toolchains ready to go

  • Gradle
    your wrapper, or 8.4, 8.10, 9.2 and 9.5 without one
  • Maven
    3.9, with the usual -DskipTests package
  • Java
    Temurin JDK 8, 11, 17, 21 and 25, picked from your build files
  • Targets
    Paper, Spigot, Bukkit, Velocity, BungeeCord, Fabric, Forge and NeoForge projects all build the same way

Free, and the add-on

One public repository builds for free on every account. The Builds add-on, $2 a month, adds private repositories, ten projects per unit and a place ahead of free builds in the queue.

FreeBuilds add-on
Repositories1 public10 per unit, public or private
Builds per project per day1010
Time per build10 minutes10 minutes
Memory and CPU4 GB, 2 cores4 GB, 2 cores
Files per build200 MB200 MB
Queuein orderahead of free builds

Questions, answered

Why is it free?

Every README that links to a FadeHost build page introduces us to server owners, which is exactly who we host for. One public repository per account costs us cents a month to build and store, so it is free without ads or surveys. Private repositories and more projects are the paid part.

What can I connect?

Any public GitHub repository that builds with Gradle or Maven and produces a jar: Paper, Spigot and Bukkit plugins, Velocity and BungeeCord plugins, Fabric, Forge and NeoForge mods, and libraries. Monorepos work too: name the subdirectory when you connect.

How is my build isolated?

Each build runs in a fresh container with no credentials of any kind, capped at 4 GB of memory, two CPU cores and ten minutes. Your build scripts never see a token; the jar is uploaded afterwards by a separate step that never runs your code.

Do I need a FadeHost server?

No. A FadeHost account is enough. If you also run a server with us, you get the one-click install on top.

What about private repositories?

The Builds add-on ($2 a month) lets you connect private repositories and up to ten projects per unit, with a place ahead of free builds in the queue. Install the FadeHost GitHub App on the repository so we can clone it; the token stays in a trusted clone step, never in the build container.

Can I keep the page private?

Yes. Turn the public page off in the project settings and the page, the badge and the stable link answer 404 while you still see everything in the panel.

How long are builds kept?

As long as the repository stays connected. Disconnecting removes its builds and files.

Connect your repository

Free for one public repository. No card, no server required.