Infrastructure for
schedulesfleets
that never sleep.
NativeLaunch is the control plane for autonomous Minecraft fleets. Spin up hundreds of workers, route them through isolated proxies, and watch every packet land in real time.
nativelaunch / fleet / live
live24
Bots running
18
Proxies healthy
1.2k
Events / min
09:41:02fleet.boot - 24 workers online
09:41:03proxy.pool - 18 endpoints verified
09:41:05module.load - BoneCollector attached
09:41:07schedule.run - nightly-sweep queued
09:41:09bot.hive-07 - authenticated
09:41:11fleet.status - all systems nominal
09:41:12
The platform
Everything the fleet needs.
Nothing it does not.
Six surfaces, one mental model. Every screen shares the same glass language, the same keyboard grammar and the same real-time spine.
Fleet orchestration
Spawn, restart and retire hundreds of isolated bot processes. Each worker forks with its own config, credentials and lifecycle.
Proxy network
SOCKS5 pools with health checks, automatic assignment and a hard capacity ceiling of three workers per endpoint.
Live telemetry
Server-sent events push status, logs and shard health into the console with sub-40ms latency.
Script engine
Author, version and hot-reload behaviour scripts without restarting a single worker.
Schedules
Cron-style jobs that fan out across the fleet and report back per-bot results.
Command palette
Cmd K from anywhere. Navigate, search and fire fleet-wide commands without lifting your hands.
How it works
Four steps from
zero to fleet.
Provision
Add an account, pick a target server and attach a proxy endpoint. The worker forks in under two seconds.
Compose
Toggle modules, bind aliases and drop in a behaviour script. Everything hot-reloads without a restart.
Schedule
Queue recurring jobs that fan out across the fleet and report per-bot results back to the activity log.
Observe
Stream every log line, status change and inventory delta live. Intervene from the console at any moment.
400+
Concurrent workers
1200
Log lines buffered
18
Behaviour modules
99.98%
Control plane uptime
Module registry
Composable behaviour.
Every worker is assembled from independent modules. Toggle them per bot, per workspace, or fleet-wide.
In production
Built for operators.
“
We went from three terminal windows and a spreadsheet to one console. The live log stream alone paid for itself in the first week.
Fleet operator
Running 120 workers
“
The proxy pool health checks catch dead endpoints before a single bot notices. That used to be an hour of manual triage every morning.
Infrastructure lead
Managing 40 endpoints
“
Hot-reloading scripts across the whole fleet without a restart is the feature I did not know I needed. Now I cannot work without it.
Automation engineer
Shipping daily
Pricing
Simple, honest tiers.
No seat maths, no surprise overages. Scale the fleet, not the invoice.
Operator
$24/mo
For serious fleets
- Up to 100 bots
- Unlimited proxies
- Script engine + hot reload
- Schedules and jobs
- Multi-user workspace
- Priority support
Fleet
Custom
For teams at scale
- Unlimited workers
- Dedicated shards
- SSO and audit log
- Custom modules
- Onboarding engineer
Questions
Answers,
no fluff.
NativeLaunch is a control plane for headless Minecraft clients. Each bot forks as an isolated Node process with its own credentials, proxy route, module set and log buffer, supervised by a single control service.
You register SOCKS5 endpoints in the network page. NativeLaunch health-checks them on demand or in bulk, then assigns workers automatically with a hard ceiling of three bots per endpoint so no single route gets saturated.
Yes. Users have roles, and every bot, script, alias and schedule is scoped to a workspace. Admins see the users page and can reassign ownership of any worker.
Everything streams over server-sent events. Fleet-level status, per-bot logs, inventory refreshes and job results all push to the browser without polling. The client keeps the last 1,200 log lines per bot.
No. Modules toggle live, aliases sync instantly and behaviour scripts hot-reload across the fleet. Restarts are reserved for credential or target-server changes.