Domain, email & servers
Run Your Own Login Server with Keycloak Single Sign-On
One login for your apps from software on a server you own, with your domain, SSL, a realm, two apps registered, reset-password email and a backup that has been tested.
Delivered in 2-3 working days
Fixed price · one-time · no hidden charges
or
Ask on WhatsApp before you buyA real person replies — usually within minutes during the day (IST).
How it works
- Pay ₹3,399Secure Razorpay checkout, one time. Then send us the server details, domain, mailbox login and the apps to connect.
- Installed and locked downWe install Keycloak with PostgreSQL, add SSL, set up the realm and register your apps.
- Login and backup provenWe test sign-in and sign-out for each app, send a test reset-password mail, test a backup restore, then send the guide and logins.
The short answer
Keycloak’s official container sizes its Java heap to 70% of the container’s memory, and the Keycloak documentation recommends a 2 GB memory limit for smaller production deployments. ZoopCoder installs the free open-source Keycloak single sign-on server on your own Ubuntu server for a fixed ₹3,399, ready in 2-3 working days. The price covers Keycloak running with a PostgreSQL database in Docker, started in production mode behind a reverse proxy on your domain with SSL, one realm, up to 2 of your apps registered as OpenID Connect clients with working login and logout, up to 5 user accounts, SMTP email so password-reset and verification mails are delivered, and daily database backups with one tested restore. Keycloak’s own documentation says a production install needs a public hostname, HTTPS and a supported database, and that is the part a quick start command leaves out: the start-dev command uses a built-in development database that the docs say must be replaced before production. The server, domain and mailbox are billed separately.
What you get
- Keycloak (current stable release, official container image) installed with PostgreSQL on your Ubuntu VPS using Docker Compose, started in production mode rather than the development mode, with a memory limit set on the container so the Java heap cannot grow without a ceiling
- Your domain or subdomain pointed to it, with free SSL that renews itself, a reverse proxy in front and HTTPS enforced
- The admin console kept off the public login address, firewall on, and root login and password login for SSH switched off
- One realm with your branding name, login settings and password rules, and a separate admin account that is not the bootstrap one
- Up to 2 of your apps registered as OpenID Connect clients, with redirect addresses set and a test login and logout proven for each
- Up to 5 user accounts, and SMTP email connected so password-reset and verification mails are delivered, with a test mail sent
- Daily automatic backups of the PostgreSQL database to a location you choose, and one test restore
- A short written guide to adding users, clients and updating Keycloak, and 14 days of fixes for anything we configured
| Price | ₹3,399 (fixed) |
|---|---|
| Software | Keycloak open-source (free) |
| Database | PostgreSQL in Docker |
| Server | Your Ubuntu VPS with root access; Keycloak’s docs advise a 2 GB container memory limit |
| Realms | 1 realm |
| Apps and users | Up to 2 OIDC apps, 5 users |
| Support | 14 days of fixes after handover |
What we need from you
- An Ubuntu VPS with root access bought in your name — we tell you which size to buy before you pay for one
- A domain or subdomain you can point to the server, for example login.yourbusiness.com
- SMTP login details for a mailbox to send from, for example [email protected]
- The names and addresses of the apps you want to connect, and a developer or person who can set the client ID and secret inside each app
Not included
- The VPS fee, domain fee, mailbox fee and backup storage fee, billed by those providers to you
- Code changes inside your own application to use Keycloak for login — if your app needs custom development, that is quoted separately
- Moving existing users and passwords from another system, LDAP or Active Directory connection, and SAML federation with other identity providers
- Clustering, high availability, Kubernetes, custom login themes and custom extensions
- Social login providers such as Google or Facebook — their app credentials and review are your side, and a provider is quoted separately
- Managing or monitoring the server after handover
About this service
Keycloak is an open-source identity and access management server: instead of every app keeping its own usernames and passwords, your apps send people to one login page and get a signed token back. That gives you single sign-on across apps, one place to disable a user, and standard OpenID Connect that most frameworks already speak. It is free to run on your own server, so there is no per-user monthly fee. The official quick start gets a development instance running in minutes, but Keycloak’s production guide is clear that a real install needs a configured public hostname, HTTPS on all traffic and a supported database, ideally behind a reverse proxy that does not expose the admin console. We do that setup, register your apps, and prove login, logout, password reset and a backup restore before handover. Wiring the client settings into your own application code is a separate piece of work. For login with Google or Facebook inside an app, see Social Login Integration, and for the server itself see VPS Server Setup.
Questions before you buy
Is Keycloak free?
Yes, Keycloak is open source and free to run on your own server. You pay for the VPS, the domain and the mailbox. Red Hat sells a supported product built on it, which is not part of this service.
Will you change my app so it uses Keycloak?
No. We set up Keycloak and register your apps with the correct redirect addresses and a working test login. Adding the OpenID Connect client code inside your application is development work and is quoted separately, unless your framework already has a ready login library you or your developer can switch on.
Do I need my own server?
Yes. The server is bought in your name and we install on it. Keycloak runs on Java and needs more memory than a small website: its documentation recommends a 2 GB container memory limit for smaller production deployments, so we tell you which size to buy before you pay for one.
What happens if Keycloak runs with no memory limit?
Keycloak’s container docs say the maximum heap is 70% of the container’s total memory, and that without a limit memory use rises quickly and is returned to the operating system reluctantly. On a shared VPS that can starve your other apps, which is why we set a limit.
Is the quick-start command safe for a live site?
No. Keycloak’s quick start runs start-dev, which uses a development-only database; the database guide says it is not suitable for production and must be replaced. We install with PostgreSQL in production mode behind HTTPS.
Can you move my existing users?
Not in this service. Moving users depends on how passwords are stored in the old system, so it is quoted separately after we look at it.
Can you set up login with Google?
Not in this service. A Google login needs your own Google app credentials, which are on your side. Ask us and we will scope it separately.
Who owns the server and data?
You do. The server, domain and mailbox are in your name and we only use the access you give us. You can remove our access once the 14 days of fixes are over.
Often ordered with this
© 2026 ZoopCoder