How Hubbl added enterprise SSO without refactoring
Before
- Hubbl used Firebase and did not want to refactor their stack
- Prospects required Microsoft Entra ID SSO integration
- Vendors like Auth0, WorkOS, FusionAuth lacked native Firebase support
After
- Hubbl integrated Entra ID via Scalekit without touching core auth logic
- Customers now configure and manage their SSO setups
- Closed enterprise deals with seamless SSO, not losing track of roadmap
Hubbl is a Denmark-based platform built to spark meaningful connections among colleagues, both during and beyond work hours. Whether it’s walk-and-talks or spontaneous chats, Hubbl fosters real connections at workplace among colleagues.
As momentum grew, so did attention from larger organizations with more sophisticated IT and compliance expectations. To serve these enterprise customers, Hubbl needed secure, scalable identity management. Single Sign-on was non-negotiable and many prospects specifically asked for integrations with identity providers like Microsoft Entra ID.
There was just one catch. Hubbl was using Firebase for auth. Building SSO inhouse would derail months of momentum.
The solution Hubbl was chasing
The team evaluated solutions like Auth0, WorkOS, and FusionAuth but found them too heavy for their lightweight architecture needs, with some lacking Firebase support. Scalekit stood out right away with simplified configuration and clearly documented Firebase integration.
With Scalekit’s OpenID Connect support, the team was able to add enterprise SSO as a provider inside Firebase . No hacks, no hidden complexity. Thanks to crisp developer guides, Hubbl had Entra ID up and running in just a few days, fully tested and ready to roll.
In the live setup, Scalekit acts as an OpenID Connect (OIDC) provider to Firebase. When a user signs in, authentication flows through Scalekit to the customer’s identity provider, and the user is routed back into the app, fully authenticated.
Scalekit also supports IdP-initiated SSO, allowing users to log in directly from their company portals without additional configuration. This makes Hubbl directly discoverable within enterprise identity providers for customers who prefer that flow.
The team also tapped into custom attribute mapping, which let them pull in key fields like department, job title, and office location. This opened the door to personalized user experiences and made sure identity data stayed aligned with enterprise policies.
Another big win was the admin portal, which gave Hubbl’s customers full control to set up and manage their own SSO configurations. It cut out the back-and-forth repetitive configurations and freed up Hubbl’s developers to focus on building product, not handling support tickets.
And while flexibility mattered, so did trust. Scalekit checked the right boxes on compliance too, with full GDPR alignment and a transparent Trust Center that gave customers the confidence they needed to move forward.
Results with Scalekit
With Scalekit, Hubbl was able to:
- Closed enterprise deals that were earlier blocked with SSO
- Integrated SSO without changing their Firebase auth
- Enabled enterprise features like IdP-initiated SSO and custom user attributes
- Empowered customers to self-configure SSO via a self-serve admin portal
Why Scalekit?
1. Developer-first SDKs: Built for modern stacks with tailored Firebase documentation
2. Enterprise-grade compliance: GDPR-ready with transparent security practices
3. Built to scale: One integration supports social login, SSO, and future growth
4. Cost-effective: A high-value alternative to complex, expensive legacy providers
The bottom line
For Hubbl, going upmarket meant meeting enterprise expectations without losing product momentum. Scalekit helped them do just that. In a matter of days, they turned an enterprise SSO requirement into a launch-ready feature—with no rewrites, no delays, and no compromise.
