Self-hosted · multi-tenant · open source stack

Run a fleet of Minecraft bots
from one control panel.

NativeLaunch spawns each bot as an isolated process, streams its console live, routes it through your own SOCKS5 pool and lets every account manage only what it owns. Built on Node and mineflayer, with a Next.js panel.

Open the panel Self-host in minutes

nativelaunch / bots / miner_01live

Statusrunning

Egress45.12.8.3:1080

Session2h 14m

09:41:02[panel] Bot "miner_01" spawned (pid 48213)

09:41:05[🍌] Connecting to play.example.net as miner_01...

09:41:08[🍌] Bot successfully spawned!

09:41:11[🍌] 🦴 Bone Collector: STARTED

09:41:14[🍌] Waiting 15s...

09:41:17[panel→bot] !stats

09:41:20[INFO] HP: 20/20 | Food: 18/20

09:41:23

What you get

Everything the fleet needs. Nothing decorative.

Nine screens share one data model, one keyboard grammar and one live event spine.

Isolated bot processes

Every bot is its own Node process with its own config, data directory and scripts. One crash never takes down another bot or the panel.

Live consoles over SSE

Console output, status, inventory snapshots and module state stream to the browser as server-sent events. No polling, no refresh button.

SOCKS5 proxy pool

Import provider lists in any format, health-check endpoints against a real exit, and auto-assign bots with a hard cap of three per proxy.

Multi-tenant by design

Each account owns its bots, proxies, aliases, scripts and schedules. Admins see everything; users only ever see their own credentials.

Scripts, aliases, modules

Interval loops and chat triggers hot-reload into running bots. Modules such as bone collector or chat games toggle from the panel or in game.

Schedules and broadcasts

Queue start and stop runs for later, or send one command to the whole fleet with a configurable stagger. Both run server-side and survive a restart.

How it works

Four steps from an empty panel to a running fleet.

Import proxies

Paste a provider list. NativeLaunch parses host:port, user:pass@host:port and socks5:// forms, then tests each endpoint.

Add bots

Roll verified usernames, pick a server and let auto-assign spread the batch across your pool. Bots start staggered.

Automate

Arm modules, save aliases, write interval or trigger scripts. Everything pushes live to running bots.

Observe

Watch consoles, inventories and shard counts stream in. Broadcast a command or schedule a stop for later.

Module registry

Behaviour is composed, not hard-coded.

Every bot reports its live module state to the panel. Toggle modules per bot, save their settings, or arm them so they start with the bot.

Economy

Bone Collector
Bone Dropper
Mine and Sell
PV Candle Dropper

Combat

TP Killer
Crystal Trap
Fight
BoxPVP Miner

Movement

Follower
Go To
Auto Home

Maintenance

Inventory Cleaner
Chat Games
Anti Stuck
Auto Auth

Integration

Discord Bridge
Payout Bridge

Self-hosted

Your server, your data, your proxies.

NativeLaunch is a small Node project you run yourself. There is no hosted tier and no telemetry: the only outbound calls are to the Minecraft server, your proxies, Mojang for username checks, and any webhook you configure.

terminal

git clone <your fork> nativelaunch && cd nativelaunch
npm install
cp .env.example .env         # set NATIVELAUNCH_ADMIN_PASSWORD
npm start                    # control service on 127.0.0.1:3000
npm run build:web && npm run start:web   # panel on 127.0.0.1:3318

Node.js 20+ control service, plain http module
Next.js 16 and React 19 panel with Tailwind 4
mineflayer bots, one child process each
JSON files on disk; no database to run
PBKDF2 password hashing, HttpOnly sessions
AES-256-GCM for stored bot credentials

Questions

Straight answers.

Headless Minecraft clients built on mineflayer. The control service spawns each bot as a child process, feeds it a config, and parses structured markers from its stdout for inventory, status, module state and events.

Run a fleet of Minecraft bots from one control panel.