Blaze Hosting logoBlaze Hosting Create account
Templates

Pick a stack.
Deploy a server.

Five first-class templates on Blaze Hosting. Same panel for console, files, variables, backups, and a hostname on *.up.node.blazedactyl.app.

Game

Minecraft (Paper)

Paper on Java. First boot downloads the server jar. You get a vanilla-compatible world with Paper’s performance patches — plugins drop into plugins/.

RuntimeJava 21 · Paper
Port25565 (TCP)
StartJar on first boot
RAMGive games more than bots

What you get

  • Paper Minecraft server, world in the volume root
  • server.properties, ops, whitelist, and logs in Files
  • Console for op, whitelist, live chat
  • Hostname on *.up.node.blazedactyl.app or your domain

After deploy

  • Open allocation 25565, then connect in the Minecraft client
  • Drop Paper plugins into plugins/ and restart
  • Need more RAM? Variables after boot — games starve on bot-sized plans
Deploy a Server
Game

FiveM

FXServer artifacts for GTA V multiplayer. The server will not list or accept players until a valid Cfx.re key is in variables.

RuntimeFXServer artifacts
Port30120 (UDP/TCP)
LicenseFIVEM_LICENSE
Keyportal.cfx.re

What you get

  • FXServer with resources folder ready
  • server.cfg in Files — endpoints, onesync, resources
  • Console for ensure, refresh, live joins

Before players

  • Create a key at portal.cfx.re
  • Paste it into FIVEM_LICENSE on Variables
  • Restart, then connect with connect IP:30120
Deploy a Server
App

Node.js

nvm-managed Node. Drop a package.json, we install on boot and run npm start — same idea as a small PaaS, inside the Blaze panel.

RuntimeNode via nvm
Startnpm start
Installpackage.json
Env.env → Variables

What you get

  • Current Node (switch versions in Variables if the egg exposes it)
  • npm install on boot when package.json exists
  • Live console, recursive file search, Railway-style env tab

How to run

  • Upload the app, keep a start script in package.json
  • Detect .env keys into Variables — don’t commit secrets
  • node_modules is skipped in Drive backup; reinstall on boot
Deploy a Server
App

Python

Isolated uv virtualenv. Put requirements.txt and main.py in the volume — modules install on boot, not from a global site-packages.

RuntimePython · uv venv
Entrymain.py
Depsrequirements.txt
Skip.venv in backups

What you get

  • Fresh venv per server — no fighting other users’ packages
  • Pip packages from requirements.txt on start
  • Console stdout/stderr for bots, FastAPI, scrapers

How to run

  • Upload main.py + requirements.txt
  • If modules don’t load, restart after the file is saved — boot is when install runs
  • Secrets go in Variables, not in the repo
Deploy a Server
App

PHP

Static PHP 8.1–8.4 with Composer on boot. Point the web root at public for Laravel. Built-in server or your start command — files and env live next to each other in the panel.

RuntimePHP 8.1–8.4
ComposerOn boot
LaravelDOCROOT=public
Env.env detect

What you get

  • PHP CLI + Composer, versions selectable on the egg
  • composer install when composer.json is present
  • Same Files / Variables / Backups tabs as every other template

Laravel & apps

  • Set DOCROOT=public so the front controller is served
  • Copy .env.example then load keys into Variables
  • php artisan from the console after deploy
Deploy a Server
Total Views: