Introducing Applications & Languages: Self-Host More Than Games
Table of Contents
Witchly started as a game server host — Minecraft, Hytale, Rust, Palworld — with a free tier backed by a coin economy and Elite plans on dedicated hardware. Today we’re broadening that scope. Starting now, you can host applications and language runtimes on the same platform, with the same tooling, the same coin economy, and the same no-over-allocation hardware guarantees.
What changed
There are two new top-level categories in the deploy flow:
Applications (8 self-hosted services)
| App | What it is |
|---|---|
| Lavalink | Standalone audio node for Discord music bots |
| JMusicBot | Ready-to-run Discord music bot |
| Red | Modular Discord bot framework |
| Uptime Kuma | Self-hosted status page & monitoring |
| Redis-7 | In-memory cache and message broker |
| MariaDB | MySQL-compatible relational database |
| MongoDB 8 | Document-oriented NoSQL database (Elite only) |
| Postgres 17 | Advanced relational database (Elite only) |
Languages (11 runtimes)
Node.js, nodemon, Python, Bun, Deno, Java, Go, Rust, Elixir, Dart, and Luvit. Deploy any of them, point at a Git repo or upload files via SFTP, and run your code with dedicated resources.
Why expand beyond games
Because our users were already doing this unofficially. We’d get support tickets asking “can I host a Discord bot on my free-tier Minecraft server?” (technically yes, but it’s a hack) and “do you have plans to host databases?” (not yet — but the infrastructure is the same). The gap between “game hosting” and “general hosting” was mostly narrative, not technical.
Under the hood, a Minecraft server and a Python script are both Docker containers with dedicated CPU, RAM, disk, and a port allocation. The Pterodactyl panel doesn’t care. What did need building was:
- Category tabs in the deploy wizard (Games / Applications / Languages) so users see what’s available at a glance
- Sensible plan defaults per category — apps and languages need different resource shapes than game servers
- Generic egg configs for each runtime, pulled from parkervcp/eggs and adapted
- Marketing surface — pricing, docs, blog, FAQ — so people understand what’s available
The infrastructure was already there. We just made it visible.
Elite plans, sized for smaller workloads
Language runtimes and applications typically have smaller working sets than game servers, so we introduced two new plan families:
Applications:
- The Helper — $2/mo · 1 GB RAM · 100% CPU · 5 GB disk
- The Daemon — $4/mo · 2 GB RAM · 200% CPU · 15 GB disk (best seller)
- The Orchestrator — $8/mo · 4 GB RAM · 400% CPU · 40 GB disk
Languages:
- The Script — $2/mo · 512 MB RAM · 50% CPU · 2 GB disk
- The Runtime — $4/mo · 1 GB RAM · 100% CPU · 10 GB disk (best seller)
- The Compiler — $6/mo · 2 GB RAM · 200% CPU · 20 GB disk
Plus Free tier for both — earn coins, renew every 7 days, same as game servers.
How it fits the existing platform
Nothing else about how you use Witchly changed. The dashboard, console, file manager, SFTP, backups, scheduled restarts, subusers, notifications, Discord bot, and the coin economy all work identically across games, apps, and languages.
You can run a Minecraft server, a Python Discord bot, and a Postgres database under one account, manage them from the same dashboard, and renew them with the same coin pool. Or host 11 Node.js bots under one Elite plan (well — one per server, but you get the idea).
Try it
- Head to dash.witchly.host and click Deploy.
- Pick the Applications or Languages tab.
- Choose your service, plan, and location.
- Deploy.
If you’re new to running self-hosted services, start with a single-purpose app like Uptime Kuma — it’s a genuinely useful monitoring tool, takes 60 seconds to set up, and fits on the free tier.
If you want to run your own code, the Node.js runtime, Python, and Bun eggs all support Git-based deploys. Push to GitHub, toggle AUTO_UPDATE, and your bot redeploys on every git push.
What’s next
A few things on the roadmap based on what we’re hearing already:
- Custom eggs — bring-your-own-Dockerfile for Elite plans, so you’re not locked into our egg catalog
- Deno on a leaner image — the current Deno egg uses the
debianbase; we’ll ship a proper Deno image - More databases — MySQL 8 (sibling to MariaDB), TimescaleDB, CouchDB
Got a service or runtime you want us to support? Hop in Discord and tell us — we prioritize based on demand.
Happy self-hosting.