Skip to content
SuperKloud

Frequently asked

Where is my data stored?

On your server. Period. SuperKloud installs on your infrastructure (VPS, bare metal, Docker-capable NAS). No application data transits through our servers.

Is it GDPR-compliant?

Self-hosting makes you the data controller. SuperKloud is designed to make that easier: access logs, centralized user management, real deletion.

Can I migrate from Google Workspace or Microsoft 365?

Yes. The catalog covers standard use cases: mail, calendar, files, chat, wiki, Git repositories, password manager. Migration happens app by app.

What happens if SuperKloud disappears?

The deployed apps are 100% open-source and run in standard containers. You keep your data and can keep operating without us.

And SuperKloud itself, is it open-source?

The catalog apps are — every one of them. For SuperKloud itself, we don't (yet) commit to releasing the code: in an era where an AI can clone a project overnight, shipping the source is essentially handing out the product. What we do guarantee: your data lives in standard formats you keep, the apps run in containers you keep if you leave, and the architecture is documented for your security audits.

I already have LDAP / Active Directory — can I plug it in?

It's on the roadmap. SuperKloud ships with a built-in LDAP directory by default but can connect to an existing directory — that option lands post-launch.

What do I need to prepare before installing SuperKloud?

Three things, that's all. A server (VPS, bare metal or Docker-capable NAS) sized to your needs. A domain name with a wildcard DNS record `*.yourdomain.tld` pointing to the server — that's what lets every app get its own subdomain without manual work. And, if you want automatic wildcard TLS certificates renewed for you, a DNS API key from your registrar (Cloudflare, OVH, Gandi, Scaleway…). The rest — deployment, hardening, certificates, routes — SuperKloud handles.

Does the installer harden the underlying server?

Yes. The SuperKloud installer hardens the host before deploying the first app: SSH switches to key-only authentication with brute-force protection, the firewall is configured to open only the necessary ports, and behavioural intrusion detection runs continuously. You get a production-ready server, not a stack to assemble yourself.

Is 2FA supported?

Yes. Each user can enable TOTP (Google Authenticator, 1Password, Bitwarden…) or register a WebAuthn security key (YubiKey, passkey). It's strongly recommended for every admin account — a reminder shows up on first login.

Waitlist now open

Be the first to know

Drop your email. We'll reach out the day the product is ready — no newsletter spam.

What's the use case you have in mind?

Which needs do you want covered? (optional, pick any)

Tick what you need — we pick the right app behind the scenes.