App hosting
Host your app, deployed straight from GitHub
Node.js, Python, Bun, Deno, Go, Java, PHP, Ruby, Rust, C# (.NET) and static sites. Point us at a repository and we install it, run it and keep it running. Every push ships the new version, any push can be rolled back, and the app can answer at https://name.fadehost.app. Your first app is free.
- First app free, no card
- Always on, no sleep timer
- Nine runtimes, detected for you
- Four regions, Singapore included
- Push receivedmain · 4f2a9c1 · “show sleeping servers too”
- BuildNode.js 22 detected · npm ci · 38 s
- Startnode index.js · listening on PORT
- Livehttps://status-page.fadehost.app
What you can host
Anything that is a repository and a process. It runs day and night on the same account as your game servers, bots and databases.
Dashboards
A control panel for your bot, your community or your staff, on its own address with HTTPS.
APIs and webhooks
A small API for your plugin or site, or an endpoint that catches webhooks from somewhere else.
Bots and workers
A Discord, Telegram or WhatsApp bot, a queue worker, a scraper, a job on a loop. No address needed.
Status pages
A page your players check to see whether the server is up, who is on and what changed.
Live in three steps
- 1
Point us at a repository
Public or private. The FadeHost GitHub App connects it in one click, or paste the URL and a token. No repository? Pick a ready-made app and fill in a field.
- 2
We build and run it
We read the repository, pick the runtime, install the dependencies, run your build if there is one and start the app. Paid apps can build a Dockerfile instead.
- 3
Push to ship
Every push redeploys. Watch it in the live console, see the commit that is live, and roll back to any earlier one in one click.
The one thing your app has to do
Listen on the port we hand it. Everything else, the address, the certificate and the routing, is ours.
import express from "express"
const app = express()
app.get("/", (req, res) => res.send("online"))
app.listen(process.env.PORT ?? 3000)Python, Go, Java and the rest read the same PORT variable. Files you want to keep go under /data.
Command line
From your terminal
The fadehost command does what the app page does: create an app from a repository, deploy, restart, tail the console, read and write environment variables. You sign in once with a code you approve in the panel, and you can revoke it there whenever you like. Node 20 or newer, and nothing to install if you run it with npx.
Read the CLI docsnpx fadehost login
npx fadehost apps create --repo <url>Then deploy, logs, restart and env on the same app, and mcp install to hand it to an AI assistant.
What we run
We read the repository and pick the runtime from what is in it. You can set it yourself, and set your own build and start commands, at any time.
Node.js
package.json, the lockfile picks npm, pnpm, yarn or bunExpress, Fastify, discord.js, Next.js. TypeScript builds before it starts.
Python
requirements.txt, pyproject.toml or PipfileFlask, FastAPI, discord.py and anything else, installed then started with your command.
Bun
bun.lock or a packageManager pinInstalled with bun, started with your start script.
Deno
deno.jsonYour start task, or the entry file with the permissions it needs. Modules cached between deploys.
Go
go.modThe main package built into a binary, modules and builds cached between deploys.
Java
pom.xml, build.gradle or a jar at the rootMaven or Gradle with the wrapper if you ship one; a committed jar runs as it is. Java 21.
PHP
composer.jsonComposer installs, the app serves from public/ or the root. Small sites, APIs, webhooks.
Ruby
Gemfilebundle install, then your start command or rackup. Ruby 3.4.
Rust
Cargo.tomlA release build of the crate, with the crates and the build cached between deploys. Rust 1.99.
C# (.NET)
a .csproj, .fsproj or .slndotnet restore, then a Release publish the dotnet host runs. .NET 10, C# or F#.
Static sites
index.html or a build outputAstro, Vite, Eleventy or a Next.js export, served with the right headers and a single-page fallback.
What every app gets
The panel around the app, not a bare container. Everything below is on the app's page.
Push to deploy
Connect the GitHub App once and every push to your branch ships the new version. No SSH, no restart button.
Deploy history and rollback
Every deploy is listed with its commit. Roll back pins the app to an older one and redeploys it; unpin when the fix is in.
Live console
Everything your app prints lands in the panel as it happens, on the app's page, with the build output above it.
Crash doctor
If the app dies in a loop we read the logs and tell you the cause and the fix in plain words, usually within a minute.
Environment variables
Keys and tokens live in a table in the panel, values masked. Add a few, save once, the app restarts with them.
Dockerfile and Railpack builds
Paid apps can build into an image on our build box: your Dockerfile, or Railpack when there is none, pushed to a private registry and started in seconds.
One-click database
Paid apps get a MySQL database at no extra cost; PostgreSQL, MongoDB and Redis sit on the same private network. Connection details land in the environment.
Scheduled commands
Run a command inside the app on a cron schedule: a nightly cleanup, a report, a cache warm-up. Ten per app, output kept.
Backups
A daily backup of everything under /data for $1 a month, kept seven days, restored in one click. Take one by hand before a risky change.
Usage chart
CPU and memory over the last 24 hours on the app's page, so an app at its memory limit is obvious before it crashes.
Four regions
Europe West (France), Canada East (Montreal), USA West (Oregon) or Asia Pacific (Singapore). Pick the one your players and your data are closest to.
Always on, locked down
Non-root, read-only filesystem, hard memory and CPU limits, and an automatic restart if the app falls over. No sleep timers.
Web address
A public address for your app
Pick a name, switch it on, and your app answers at https://name.fadehost.app with HTTPS within seconds. No port to open, no tunnel to run, the certificate handled for you. It comes with every app. A free app gets an address that sleeps when nobody is using it and wakes on the next request; a paid app keeps its address awake, at no extra cost.
- Dashboards, control panels and status pages
- OAuth redirect URLs and incoming webhooks
- Rename it or switch it off whenever you like
- If the app is not listening, the panel says so instead of a blank error
Web apps and workers only: no proxies, tunnels, phishing pages, bulk media or raw TCP services. The terms have the full list.
- Certificate
- Issued, renews itself
- Live since
- 4 seconds after the switch
- Free tier
- Sleeps when idle, wakes on request
- Paid tiers
- Always on, with the plan
Apps to start from
Open-source apps we build and maintain. Deploy one as it is from the panel, or fork it and make it yours.
For a Minecraft community
They talk to the FadeHost API for you; the panel creates the token when you deploy.
Server status page
Node.jsA public page of your servers: online or sleeping, who is on, the address to join.
View the sourceWhitelist applications
Node.jsA form players fill in, an admin page for staff, the whitelist command run on approval.
View the sourceActivity digest
PythonWho played and for how long, summed up once a day to a Discord webhook.
View the sourceServer guide site
StaticRules, how to join and the mod list on a static site edited in Markdown.
View the sourceBots
Eight Discord bots need no code at all: a token and a field or two.
Discord bots: role, status, ticket, welcome, moderation, giveaway, level, logging
Node.jsPick one in the panel, paste the token, done. Each is a public repository you can fork.
See the botsBot with a dashboard
Node.jsA welcome and log bot whose settings live on a web page behind Discord login.
View the sourceTelegram bot
Node.jsA grammY bot with commands, polling by default or webhooks behind the web address.
View the sourceWhatsApp bot
Node.jsA webhook receiver for the official WhatsApp Cloud API with signature checks and replies.
View the sourceStarters
Bare services wired to the port and the persistent folder, ready to build on.
Ready-made apps, one click
No repository and no build: pick one from the catalog, name it, deploy. Each runs from the project's official image with its data kept safe.
Uptime Kuma
Host Uptime Kuma in one click: the official image, a public https address, daily backups and alerts to Discord, Telegram or email.
How it is hostedn8n
Host n8n from its official image in one click: a public https address for webhooks, persistent data, daily backups and a flat $2 a month.
How it is hostedVaultwarden
Host Vaultwarden, the Bitwarden-compatible password server, from its official image in one click: an https address for the apps and extensions, encrypted data under /data, daily backups.
How it is hostedGitea
Host Gitea from its official image in one click: repositories, pull requests, issues, a package registry and Actions at your own https address, with daily backups, from $2 a month.
How it is hostedLavalink
Host a Lavalink node from the official image in one click, on your private network next to your Discord bot.
How it is hostedBy framework
What the deploy looks like for the framework you use.
Coming from another platform
What changes when an app moves here from a free tier that ended.
By what it does
The same runtime, written up for the job you came to do.
Locations
Close to your players on three continents.
Pick the region when you create a server, or move it later from Settings. Same hardware, same panel, same price everywhere.
- USA WestOregon
- Canada EastMontreal
- Europe WestFrance
- Asia PacificSingapore
Minecraft, other games, bots and apps run in every region.
Pricing
Every plan is a number of apps, and every app gets 1 GB and 1 vCPU. One bill with your game servers. Yearly is ten months for twelve.
Free $0/mo 1 app One per verified account | Starter $2/mo or $20/yr, 2 months free 1 app One app, always on | Standard $3/mo or $30/yr, 2 months free 2 apps Your app and your test app | Pro $6/mo or $60/yr, 2 months free 4 apps A whole shelf of apps | |
|---|---|---|---|---|
| RAM | 256 MB per app | 1 GB per app | 1 GB per app | 1 GB per app |
| CPU | 0.25 vCPU per app | 1 vCPU per app | 1 vCPU per app | 1 vCPU per app |
| Extra memory | not on this tier | +1 GB for $1/mo, up to 3 | +1 GB for $1/mo, up to 3 | +1 GB for $1/mo, up to 3 |
| Disk under /data | 3 GB | 5 GB | 10 GB | 20 GB |
| Web address | Sleeps when idle | Always on, included | Always on, included | Always on, included |
| Database | not on this tier | MySQL included | MySQL included | MySQL included |
| Daily backups, 7 days | +$1/mo | +$1/mo | +$1/mo | +$1/mo |
| Image builds | not on this tier | Dockerfile, Railpack | Dockerfile, Railpack | Dockerfile, Railpack |
| Start free | Add Starter | Add Standard | Add Pro |
- Always on, no sleep timer, no daily renewals
- Need more than 1 GB for one app? Add up to 3 GB for $1 a month each
- GitHub auto-deploy, live console, crash doctor
- Deploy history and rollback, scheduled commands, usage chart
- Environment variables, private network, four regions
What a typical setup costs
A status page for your server
Free tier, sleeping address
$0
Wakes on the first visit in a few seconds; the page itself never sleeps.
A bot with a dashboard
Starter, address included
$2/mo
1 GB, the dashboard answers at once, MySQL included for its settings.
An API and its test copy
Standard + MySQL
$3/mo
Two apps, 1 GB and 1 vCPU each, 10 GB of disk, the database on your private network at no extra cost.
Next to the usual suspects
What an always-on app costs at the hosts people move from, from their pricing pages in September 2026.
| Host | Smallest always-on app | Price | Note |
|---|---|---|---|
| FadeHost | 1 GB, always on | $2/mo | First app free; web address included |
| Render | 0.5 GB, always on | $7/mo | Free tier sleeps after 15 minutes |
| Heroku | 0.5 GB, sleeps after 30 min | $5/mo | Eco dynos share 1,000 hours |
| Railway | Usage billed | $5/mo + usage | About $10 per GB-month and $20 per vCPU-month |
Moving from one of them? Railway, Heroku and Glitch each have a page on what changes.
Already hosting a game server? Add apps to the same subscription in the plan builder. One account, one bill.
Frequently asked questions
- Is the free app hosting actually free?
- Yes. Every verified account gets one app free, forever: 256 MB of RAM, always on. No credit card, no coins to grind, no daily renewal clicks and no sleep timer. Paid tiers start at $2/mo or $20/yr when you need more room or more than one app.
- Which languages can I run?
- Node.js, Python, Bun, Deno, Go, Java, PHP, Ruby, Rust, C# (.NET) and static sites. We detect the runtime from your repository and install with the package manager your lockfile names. If your app has to be compiled first, we run the build before starting it.
- Can I use a Dockerfile?
- Yes, on a paid tier. Set the build mode to Dockerfile and we build the image on our build box, push it to a private registry and run it on the node. Railpack does the same without a Dockerfile. Free apps run from source so the runtime can scan what it starts.
- How does my app get a public address?
- Open the app, pick a name and turn the web address on. It answers at https://name.fadehost.app over HTTPS within seconds. Your app listens on the PORT variable and we route the name to it. A free app gets an address that sleeps when nobody is using it and wakes on the next request; a paid app keeps its address awake. It comes with the plan either way, with nothing to add.
- Can I deploy from a private repository?
- Yes. Install the FadeHost GitHub App and pick the repository, or add an access token when you create the app. We fetch the code on every deploy and never store your credentials.
- What happens when a push breaks the app?
- The crash doctor tells you what broke, and the app's page lists every deploy with its commit. Roll back to the last good one and it redeploys pinned to that commit; unpin when the fix is pushed.
- Do files my app writes survive a deploy?
- The app directory is replaced with your repository on every deploy, so anything written next to your code is gone after a push. Write to the /data folder instead, which is yours and persists, or use a database. Backups of /data are $1 a month.
- Can my app use a database?
- Yes. Paid apps include a MySQL database at no extra cost, created with one click, with the connection string injected into the environment. PostgreSQL, MongoDB and Redis are available as managed databases on the same private network.
- What are the limits?
- Free: 256 MB, a quarter of a CPU, 3 GB of disk, one app. On the paid plans every app gets 1 GB and 1 vCPU, and the plan says how many apps it carries: Starter one, Standard two, Pro four. Disk is 5, 10 and 20 GB. Any app can take up to 3 GB more memory for $1 a month each. Every app has a hard memory and CPU limit; the usage chart shows how close you are.
- What is not allowed?
- Phishing and credential pages, proxies and tunnels, adult or illegal content, and bulk file or media delivery through the address. App hosting runs web apps and workers, not raw TCP or UDP services, outbound mail or privileged workloads. The full rules are in the terms.
- What happens when my app crashes?
- It restarts on its own, and the crash doctor reads the logs and explains what went wrong. The live console keeps the output so you can see what the app said last.
Read on
App hosting documentation
Create an app, the PORT variable, build modes, rollback, schedules, backups and the limits per tier.
Discord bot hosting
The same runtime, set up for a bot: token, intents, eight premade bots.
Managed databases
MySQL, PostgreSQL, MongoDB or Redis on your private network, reachable from your app by name.