Flamingo Raises $4.5M to Get MSPs Out of the Ticket Queue

Skip to content
OpenFrame IAM and SSO logo

OpenFrame IAM and SSO

Identity and Access Management (IAM)

Selected
Open Source
Gen2
Paid Plans
OpenMSP Score
28
19
Reddit Impact Score
Github Score
7M
1KStars
28Forks
3KCommits
OtherLicense
Oct 30, 2026Last commit
OpenFrame IAM and SSO is the planned identity layer of OpenFrame, Flamingo's AI-native platform for MSPs. It is part of OpenFrame Gen2, which OpenFrame lists as coming in Q4 2026, and it is in development on the public roadmap. It is not available yet. As planned on the roadmap, it adds centralized identity for MSP staff and client users across OpenFrame services: single sign-on over SAML, OAuth and OpenID Connect with cloud and on-premises identity providers, role-based access control, multi-factor authentication enforcement, session management, user provisioning and deprovisioning, conditional access rules and audit trails of authentication events. What exists today is sign-in to OpenFrame itself: built-in Google, Microsoft and Apple sign-in plus email and password, custom Google Workspace and Microsoft Entra ID OAuth providers per tenant, a domain allow-list for self-registration, and a per-tenant switch to turn off the built-in sign-in. OpenFrame does not enforce MFA itself today, and full role-based access control is a separate roadmap item. OpenFrame lists Gen2 at $3.00 per managed device per month when it launches. Like the rest of OpenFrame, the code is published on GitHub under the Flamingo AI Unified License.

Key Features

SSO for Staff and Clients (Planned)

Single sign-on across OpenFrame services over SAML, OAuth and OpenID Connect

Role-Based Access (Planned)

Roles and permissions for MSP staff and client users

MFA Enforcement (Planned)

Enforce multi-factor authentication and password policies

Provisioning and Deprovisioning (Planned)

Create and remove user access from one place

Conditional Access and Audit (Planned)

Conditional access rules and audit trails of sign-in events

Sign-In Available Today

Google, Microsoft and Apple sign-in, custom Google Workspace and Entra ID providers per tenant, and a domain allow-list

Pros and Cons

Pros

Identity Inside the Same Platform

Identity is planned inside the platform that already holds devices, tickets and cloud tenants

Works With Existing Microsoft and Google Accounts

Sign-in today already uses clients' Google Workspace and Entra ID accounts

Standard Protocols Planned

SAML, OAuth and OpenID Connect support is on the roadmap

No Separate Identity License Planned

Part of Gen2, which OpenFrame lists at $3.00 per device per month

Public Code

Source on GitHub under the Flamingo AI Unified License

Cons

Not Available Yet

In development for Gen2 (Q4 2026); only OpenFrame's own sign-in ships today

No MFA Enforcement Today

OpenFrame relies on the identity provider's MFA at sign-in and does not enforce MFA itself

No Track Record

Unproven next to established identity products such as Entra ID, Okta or JumpCloud

Feature Comparison

Features
Cost and Licensing
Loading the comparison

Comments

No reviews yet. Be the first to share your experience with OpenFrame IAM and SSO.

Frequently Asked Questions

vendor