Built for a community that actually runs

Why it exists

Running a roleplay community means keeping track of who is in which department, who is on duty, who applied, who is on leave, who is suspended, and who is allowed onto the server tonight. Those are all the same few facts about the same few people.

FiveHQ keeps them as one record. That is why a suspension can reach the whitelist, and why a promotion can change an in-game job grade — not because those features were bolted together, but because they were never apart.

What happens if you stop?

A fair question to ask anything you are about to run your community on. The answer is not a promise about the future, it is a set of properties that hold today.

• Your community owns its dataNot whoever created the account. A community can have several owners, and ownership can pass to somebody else without anything being rebuilt.
• There is an API on every planScoped keys, published rate limits, and signed event webhooks — including on the free plan. Whatever we do, your data is reachable by something you control.
• Incidents are publishedA status page and a changelog, so you can see what broke and what changed rather than taking our word for it.

Every community can export everything it holds, on every plan including the free one. One archive: JSON for the complete record, plus CSV for the tables you would actually open in a spreadsheet — members, characters, factions, ranks, appointments, applications, discipline, bans, duty and tickets. No plan gate, no support request, and no charge to leave.

Can I run it myself?

Not yet. FiveHQ runs in containers and self-hosting is technically possible, but it is not something we support today.

Getting hold of us

Support is by Discord and email. We are not going to promise you a response time we cannot keep — what we do promise is a public changelog and a status page that says when something is broken.