GuidesOnly show guides for your app
GuidesGuidesCreate a server, choose an application, press Start, deploy a ready-made template, and change or delete it later — the whole first-server flow, click by click.
This is the hands-on companion to how app hosting works. We'll go from an empty account to a running server in a few minutes, then point you at the guide for whatever you're actually building.
| At a glance | |
|---|---|
| You need | A Falix account |
| Time | About ten minutes |
| Plan | Any — applications run on free and premium alike |
From your server list, click Create server. You'll see two tabs: Games and Applications. You want Applications.
The Applications tab is split into Languages (Node.js, Python, Java, Go, PHP…), Databases (MongoDB, PostgreSQL, Redis) and Software (ready-made tools). Pick the one that matches what you're building — if you're following a language guide, pick that language. Not sure yet? Node.js is the friendliest place to start.
Your choice decides what happens when you press Start, so it matters; how app hosting works explains why. And because applications run on both free and premium, you don't need to pay to try this.
Give it a name and create it. Falix builds the container and installs your chosen runtime. When it's done you land on the server, with the whole menu — Console, File Manager, Settings and the rest — down the side.
Go to the Console page and press Start. What you're checking is that the console comes alive and shows output. This is the loop you'll use forever: press Start, read the console.
🎯 Good to know: On a brand-new, empty server there's nothing to run yet, so the app will start and then stop again — that's expected, not a failure.
The fastest way to see a real, working app is a one-click template: a small set of known-good starter files. There are two ways to deploy one:
The template writes its files into your server folder (only overwriting files with the same name), and then you press Start again. This time the console shows a real app running. One-click templates explains exactly what happens — including the warning you'll see if a template needs to switch your server to a different application.
A free server runs on a session timer and stops when it runs out. Head to the Timer page to top it up: you'll solve a quick captcha, and each extension adds hours back on. Keeping your app online has the full story.
💡 Tip: It's normal to do this a few times a day — and premium removes the timer entirely.
You've got a working first server if the Console shows output when you press Start, and — after deploying a template — you can see your app's own messages there. If it's a web app, the Network page shows the address to open in a browser.
Your first server won't be your last, so it's worth knowing how to change or get rid of one. Everything below lives on the Settings page.
Now pick your language and build something real: