Mudhaven hosting
Choose the hearth
your realm needs.
Plans set the safe resource envelope for hosted BYOND and MUD games. They are reviewed by staff before provisioning, so the right fit matters more than rushing the gate open.
Plan tiers
Limits without mystery.
These are technical hosting limits, not automated billing yet. Staff may approve a different tier or set a temporary override if your codebase needs it.
Starter
0.5 GB
Best for small worlds, pilots, and early testing.
- Storage
- 512 MB
- Upload max
- 50 MB
- Backups
- 3 snapshots
- Backup storage
- 1.0 GB
- Memory
- 512M
- CPU
- 50%
- Tasks
- 96
Standard
2.0 GB
Best for active worlds with room for releases and snapshots.
- Storage
- 2,048 MB
- Upload max
- 100 MB
- Backups
- 10 snapshots
- Backup storage
- 4.0 GB
- Memory
- 1G
- CPU
- 100%
- Tasks
- 192
Large
8.0 GB
Best for larger worlds, heavier MUD codebases, and busier communities.
- Storage
- 8,192 MB
- Upload max
- 250 MB
- Backups
- 20 snapshots
- Backup storage
- 12.0 GB
- Memory
- 2G
- CPU
- 200%
- Tasks
- 384
BYOND
DreamDaemon hosting
BYOND slots focus on versioned `.dmb` deployments, staged uploads, backups, log tails, and controlled Start/Stop/Restart actions after staff installs the systemd unit.
MUD
Codebase-aware hosting
MUD slots account for codebase family, build command, runtime language, start command, log path, manual build review, and runtime approval before the process controls unlock.
Review
What staff checks
- 01Account trust
Email verified, account approved, and no active bans.
- 02Runtime fit
Plan, port, filesystem path, codebase family, and resource limits make sense.
- 03Safe launch
Filesystem prepared, release reviewed, runtime unit previewed, then installed.
Questions before applying?
Send the right raven.
Hosting applications are for games you want Mudhaven to run. Atlas listing requests are for games that should appear in the public directory, even if hosted elsewhere.