Loading...
solo devs & small studios
Ship your game without running the infrastructure
Link the repo you already have, cut a build, and put servers in front of players — all from the same panel, at a size that makes sense for one person.
- 80+
- Game titles
- 390+
- Templates
- 24/7
- Support
Toolkit
What you get
The pieces a small team needs to get a game out, without standing up any of it yourself.
Build Pipeline
Link your project source once, then let the build runner fetch and build it.
- GitHub
- GitLab
- Bitbucket
- Gitea
- Git URL
- Zip upload
Game Servers
Run servers for playtests or for players, sized to the session and resized on demand.
- Fleets
- Auto-resize
- Backups
- World maps
Storefront
List what you have made and watch how it sells, without wiring up a shop.
- Listings
- Sales
- Analytics
Backend & Bots
Deploy the services around the game — APIs, matchmaking, Discord bots.
- Node.js
- Python
- Go
- Bots
Databases
Managed engines for saves, accounts and telemetry.
AI Assistant
Page-aware help that can read a crashing server log and tell you why.
- Log analysis
- Guided setup
- Deploy
How it works
How shipping works
Source to players, in three moves.
Step 1
Link your source
Point the project at wherever the code already lives. You wire it up once, in the project overview, and every build after that reuses the same linkage.
- GitHub, GitLab, Bitbucket or Gitea
- A raw Git URL, if you self-host
- Or upload a zip and skip Git entirely
Step 2
Cut a build
The build runner fetches your source and produces an artifact. Unity projects are first-class — this is the studio side of the product, not the hosting side.
- Unity build pipelines
- Build config stored with the project
- Releases promoted from a build
Step 3
Put it in front of players
Spin up servers from the same panel, hand out a share link for a playtest, and let players sign in from inside the game.
- Server fleets that resize on demand
- Scheduled backups and save management
- In-game sign-in via the server browser
Game Development
Built for shipping games
The studio side of OTHCloud — the parts that exist because running a game is not the same as running a server.
Blueprint wizard
Package your own game into a deployable blueprint. A built-in expert answers the fields a form can only hint at — what belongs in the startup command, why a server sits there doing nothing.
AI log reading
A game server's logs are mostly chunk saves and join spam, with the stack trace that matters buried thousands of lines up. Ask what went wrong and get the part that answers it.
Public game page
A share page for your server that hands players the modpack — zipped live from the mods folder, a file you uploaded, or a link somewhere else.
In-game sign-in
Players sign into OTHCloud from the modpack's server browser using a device code, so they never leave the game to get on your server.
Scheduled backups
Auto-backup on an interval and, if you want, at a set time of day — with the countdown to the next one shown on the server.
World maps
Rendered maps of Minecraft worlds via BlueMap, for any world on 1.13 or later.
Fleets & auto-resize
Run a group of servers together and let them resize to the load instead of paying for a peak that rarely arrives.
State notifications
The agents report what each server is doing, and a change of state becomes a push notification rather than something you find out about later.
When you grow
Outgrowing solo
Start on your own, and switch the organisation over when there are more of you.
Indie
On your own
- Servers, deploys and databases
- Marketplace listings
- Sized and priced for one person
Games company
As a studio
- Everything above, plus
- Unity build pipelines
- The full org suite — members, email, tasks
Game Development is the studio side of the product, so it comes with a games-company organisation rather than a personal one.
Games companies