NL EN

IT management
Microsoft 365
Network & security
Who for
Hosting & cloud
Magento
Websites & online shops
Managed applications

All services at a glance

Keycloak hosting: the heavier login, kept up by us.

For organisations with an existing user directory, and for developers who want sign-in built into their own software.

Get in touch
Drawing of a firewall with a switch in front of it, a fibre line going out and a 4G router as backup.Fibre4G backupFirewallSwitch

Short answer

Keycloak is an open source platform for identity and access. It handles single sign-on, connects to an existing LDAP directory or Active Directory, and has fine-grained roles. Developers use it so they do not have to build sign-in for their own software. We install Keycloak on our own machines in the Netherlands and maintain it. It can replace Okta or Auth0.

Keycloak or authentik

SubjectKeycloakauthentik
SizeLarge, with many settingsMore compact, quicker to set up
Existing user directoryLDAP and Active Directory are a core featurePossible, but less of what it was built for
Your own softwareWidely used by developers for login in their own applicationsPossible too, with fewer tools around it
What it asks of a serverMore memory and more maintenanceLess
SuitsLarger organisations and development teamsSmaller organisations with ordinary applications

We host both. If your situation is small and ordinary, we recommend authentik, because there is less to manage.

When Keycloak is the right choice

You have had a user directory in Active Directory for years and do not want to enter it all again. Keycloak reads that directory and lets applications point to it. The accounts stay where they are.

Or you build software for customers or for yourself, and every project has a login, roles and a password somebody forgets. Then you set up Keycloak properly once and let every project connect to it.

If neither applies, Keycloak is probably more than you need.

Facts about Keycloak

Licence
Apache 2.0. Keycloak is a trademark of its owner. Jevana is not part of the project and has no business tie to it.
Origin
A project of the Cloud Native Computing Foundation
Replaces
Okta and Auth0
Our part
Installing, updating, one backup a day with an external copy, and monitoring
Where
A Keycloak of your own per client, hosted in the Netherlands, reachable on your own domain name

Questions

Who is Keycloak meant for?

Keycloak is meant for organisations with many users, many applications or an existing user directory, and for developers who want sign-in built into their own software. It can do a lot, which also means there is a lot to configure. For a small office with a handful of applications a lighter choice is usually better. We will say so.

Can Keycloak use our Active Directory?

Yes. Keycloak can read users from LDAP or Active Directory, so staff sign in with their existing account and you manage nothing twice. We set up that link and test it with a few accounts before everyone moves over. Changes in the directory then carry through to the applications that use Keycloak.

Can you connect Keycloak to software we build ourselves?

Yes, as long as your software speaks a standard such as OpenID Connect or SAML. We prepare the environment and create a client of its own for each project, with the right roles. Building it into the code is up to your developer or whoever builds the software. We do not build custom applications ourselves, so that part is yours.

What do we get from you managing Keycloak?

Keycloak gets updates regularly, security ones included, and everything depends on it: if it stops, nobody gets in. We install the updates, make a backup every day with a copy at an external location, and watch the server. Your team manages users and roles, or we do that if you agree it with us.

Goes well with

Tell us what you run.

An introduction costs nothing. You talk straight away to one of the two people who will actually do the work.

Get in touch

or email info@jevana.systems