v1.0 shipped · Apache 2.0 · self-host

Kubernetes for Minecraft.

PrexorCloud orchestrates Minecraft servers across your fleet. Pool nodes, define groups, scale on demand — with mTLS daemons, signed releases, and zero-downtime drains.

mTLS by default Active-active HA Cosign + Rekor signed
prexorctl · live demo
What's distinctive

Three things you won't get elsewhere.

Most orchestrators stop at "manage a fleet". These three are the reason PrexorCloud exists at all.

Daemon-side modules

Layer 7 modules run on the daemon, not the controller. Hook every instance lifecycle event — onInstanceStarting, onStarted, onStopping, onStopped — without forking the daemon.

Read the spec →

Capability registry

Modules declare what they provide and what they require. The controller wires the graph at boot. Swap a webhook backend or a metrics sink without touching the consumer — it's contracts, not imports.

Read the spec →

Signed end-to-end

Every release artefact — controller, daemon, prexorctl, container images, modules — is cosign-signed with a Rekor transparency entry. Production daemons fail-closed on missing SETs.

Read the spec →
Templates

YAML you'd write yourself.

No DSL. No annotations. No magic. A group is twelve lines of plain YAML and behaves identically across local dev, staging, and production.

  • JSON Schema shipped — every editor gets autocomplete + validation for free.
  • Versioned in your repo. CI applies. The cluster is the truth.
  • Layered composition: base → base-paper → group → user.
groups/lobby.yaml
# 4 lobby instances on Paper 1.21.4
apiVersion: prexor.cloud/v1
kind: Group
metadata:
  name: lobby
spec:
  platform: paper
  version: '1.21.4'
  template: lobby-base@v7
  scaling:
    mode: dynamic
    min: 2
    max: 12
    target:
      playersPerInstance: 150
  resources:
    memory: '4Gi'
    jvmArgs: ['-XX:+UseG1GC']
Receipts, not numbers

Every claim links to its source.

We don't ship aspirational metrics. Every promise below is a workflow you can run, a log entry you can verify, or a file you can read.

If you're already running CloudNet or SimpleCloud

What changes when you switch.

Three rows where PrexorCloud is meaningfully different. The full feature matrix is in the CloudNet and SimpleCloud pages.

Capability PrexorCloud CloudNet 4 SimpleCloud V2
Module signing cosign + offline Rekor SET, fail-closed in production Modules unsigned by default Droplets unsigned
Active-active controller Two controllers behind a Valkey lease, second-scale failover Single-node controller architecture "Only one controller running at a time" (docs)
Per-instance daemon hooks DaemonModule with onInstanceStarting/Started/Stopping/Stopped ~ Wrapper-side modules — no per-instance lifecycle SPI ~ Droplet protocol — no per-instance lifecycle SPI
Ready when you are

Spin up your first cluster in 5 minutes.

One binary, one config file, one command. We'll stay out of your way.