Everything SCRHUB builds, hosts and runs
The SCRHUB ecosystem
A connected family of services SCRHUB builds, hosts and runs itself. A Discord bot with a real dashboard, a storefront and a licence platform behind it, and the everyday tools around them.
Self-hosted on SCRHUB infrastructure. No third-party analytics on this page.
Flagship
SCRHUB Guard
A Discord bot you configure from a browser, not a config file. Twenty-three modules, each one a toggle: turn on what your server needs and leave the rest off.
Twenty-three modules, one dashboard
Every module below ships in the running bot. Nothing here is planned or coming soon.
- Moderation
- Raid protection
- Leveling
- Economy
- Tickets
- Role panels
- Welcome
- Giveaways
- Custom commands
- AI assistant
- Notifications
- Announcements
- Reminders
- Birthdays
- Boosts
- Counters
- Crypto
- Embed builder
- Fun
- Games
- Server templates
- Temporary voice
- Utility
Five languages
English, Hungarian, German, Spanish and French, in the bot and in the dashboard.
Self-hosted
Guard runs on SCRHUB's own infrastructure. There is no subscription and no per-server limit.
Bring your own AI key
The assistant stays inactive until you add a Groq, OpenAI, Gemini or Claude key. No AI usage is bundled and none is billed.
Commerce and licensing
Sell it, licence it, prove the two agree
The storefront and the licence platform are two services, not one, and a scheduled reconciliation checks hourly that they still tell the same story.
Reconciled every hour
A revocation in the Shop must never leave an entitlement active in Licenses. A scheduled job compares the two and reports any disagreement, so drift is found by a machine rather than by a customer.
Everyday tools
Small services, built the same way
Three utilities SCRHUB runs for itself and opens to everyone. All of them are deliberately quiet about their visitors.
Your SCRHUB
One place for your account, and one for the truth about ours
How SCRHUB is run
Checked, not assumed
Every claim on this page is something a scheduled job re-checks against the running estate. When one of them stops being true, the estate says so before a customer has to.
- Availability, every ten minutes
- Each public service is asked whether it is up and whether it is ready. A service answering "degraded" fails the check; answering at all is not enough.
- The code that runs is the code on record
- Files inside each running container are hashed against the recorded source. A stale build context or an out-of-date deployment pin is a failure, not a surprise.
- Backups that are restored, not just taken
- Backups are restored into a throwaway database and read back. A backup nobody has restored is a hope, not a recovery plan.
- One design system, measured in a browser
- A real browser renders every surface and compares what it paints: the ground, the accent, the contrast and whether the typeface actually loaded.
