Most hosting pages describe an ideal customer who happens to be everyone. This one is narrower on purpose, because the fastest way to be useful is to tell you early if this is not for you.
You built something with AI and it needs to stay running
This is the main one. You described an app to Claude, ChatGPT or Cursor, it wrote the code, and it works on your machine. What you need now is somewhere that keeps it alive, and you would rather not spend an evening learning what a process manager is.
You do not need to know how deployment works. That is the entire premise: you ask, it deploys, and when it breaks the assistant reads the logs and tells you what happened in English.
You run a Discord server and the app is for it
Mod tools, ticket systems, welcome flows, role pickers. These are small, they are important to the people using them, and they are embarrassing when they go down at the weekend.
Moderators can restart an app from the panel without waiting for you, which is usually the actual bottleneck.
You ship a lot of small things
A scraper, a cron job, an alert app, a queue worker. Individually none of them justify a server; together they are annoying to keep on one. Per-app slots means you add one, and when you are bored of it you stop it and the slot frees up.
Where you should use something else
| IF YOU… | USE |
|---|---|
| Built a website or web app | Vercel or Netlify, mostly free |
| Want root, SSH and your own OS | A VPS, similar price |
| Have request-shaped, bursty code | A serverless platform |
| Need a database as the main thing | A managed database provider |
| Run at large scale with a platform team | Your own orchestration |
None of those are grudging admissions. Sending you to the right tool costs us one signup and saves you a bad month.
If you are not sure
Ask whichever assistant built your project: "does this need to run continuously, or only when someone visits it?" It will know from the code, and the answer tells you which half of this page you are in.