Keycloak Hosting

Open your pod and allow about a minute for initial startup, as noted in the PikaPods instructions. Open the Administration Console and sign in with the administrator account provisioned for your pod.

The PikaPods note does not publish a universal default username or password, so do not assume admin/admin. Keycloak's Docker getting-started guide shows how bootstrap credentials are supplied in a self-managed installation; keep your pod's administrator credentials unique and store them securely.

No. PikaPods sets up and runs Keycloak for you, including OS and app updates and HTTPS. You won't touch Docker or a server. Your files and database stay accessible if you ever want to move them elsewhere.

1. Create a separate realm for your users and applications rather than using the master realm for everyday integration.
2. Create a client, select its authentication flow and set its exact redirect URIs and web origins.
3. Create or federate users and assign only the roles and groups your application needs.

Use the securing-applications documentation for the client protocol and adapter appropriate to your application. Client credentials and signing keys are secrets and should not be embedded in public code.

The pod supplies Keycloak's server-side persistence. Email verification, password-reset messages and other mail flows require SMTP settings and may need a paid mail provider. SMS authentication or third-party social login likewise depends on an external provider and its own account, credentials and charges.

Set up incremental backups to S3 in your pod settings for automatic nightly snapshots, or download your files and database yourself. We keep whole-server backups for server failures, but they aren't a per-pod restore service, so your own backup is what protects your data.

You can use Keycloak instead of Auth0 and Okta. PikaPods runs it for you, and you can move your files and database elsewhere.

Both provide login, single sign-on and user management for your applications. Auth0 is a hosted service with quickstarts and pricing tied to usage. Keycloak runs on your pod, supports user federation and standard protocols, and leaves configuration in your hands. Expect a steeper learning curve, and plan for keeping it available, since your apps rely on it for logins.

No. You add prepaid credit and your pods are billed by the hour from that balance, rounded up to full hours. There are no contracts or minimum terms: delete a pod anytime and billing stops. Optional automatic top-ups keep your pods running without manual payments.

You do. And you're in full control. If you ever want to download, migrate, edit or delete your data, just enable file and database access for your pod and it will be right there.