OpenFrame

OpenFrame is Flamingo’s unified MSP/MSSP operating platform. The current Gen1 commercial surface bundles remote monitoring and management, remote access, patch management, professional services automation, SIEM/security monitoring, mobile-device management and documentation/password management behind one platform. Fae handles end-user support intake and resolution, while Mingo is positioned as the technician-side agent for executing operational work. ¹²

The technical surface is unusually inspectable for a commercial MSP platform. Flamingo publishes the OpenFrame tenant code and CLI, with a cross-platform Rust endpoint agent, multi-tenant services, OAuth/OIDC, event streaming, API services and integrations with components such as Fleet MDM, MeshCentral and osquery. The self-hosted CLI can bootstrap an OpenFrame environment on Kubernetes/K3D with ArgoCD. That gives technically capable MSPs a real self-hosting route rather than only a marketing promise. ³⁴

This breadth is also a source of execution risk. OpenFrame is trying to replace multiple mature point products at once, and its own roadmap shows additional endpoint security, backup, IAM, network and XDR/MDR categories arriving in later generations. Gen1 should therefore be assessed on what is live now rather than on the eventual 19-category vision. ¹²⁵

Managed Gen1 pricing is simple: $1 per device per month with 10 million AI tokens included, or an advertised $0.80 per device per month equivalent on annual billing with 25 million tokens and a 20% discount. Flamingo offers a 14-day free trial without a card or long-term contract. There are no per-technician fees on the current public pricing surface. ²

For MSP economics this is highly aggressive. The same public roadmap lists Gen2 at $3/device/month and Gen3 at $5/device/month when the additional security/backup categories arrive, so buyers should not assume today’s Gen1 price buys the eventual full roadmap indefinitely. Self-hosting is separately permitted under Flamingo’s license and public codebase, but customers bear their own infrastructure and operational costs. ²⁴

OpenFrame’s evidence profile is mixed in a useful way. The source code, CLI, release notes, privacy policy and license are public enough to inspect architecture and legal terms directly. Flamingo’s privacy policy says self-hosted OpenFrame customer data remains under customer control and is not collected by Flamingo; the managed-cloud FAQ separately says hosted data is on US infrastructure. Buyers should therefore distinguish self-hosted and Flamingo-managed data paths rather than treating them as one privacy model. ⁶

The licensing deserves precise wording. Flamingo calls OpenFrame open source and permits use, copying, modification, distribution and self-hosting. But the Flamingo AI Unified License v1.0 also prohibits offering Flamingo Software as a competing commercial managed service without a separate license and prohibits relicensing. Upstream components such as Fleet, osquery and MeshCentral retain their own permissive/open-source licenses. AiToolMap therefore classifies the Flamingo-authored layer as partially open/source-available with commercial restrictions, not as unrestricted OSI-style open source. ⁴

Maturity is the main unresolved trust factor. Flamingo published OpenFrame v1.0.4 as its first GA release on July 16, 2026. Independent Channel Dive and CRN reporting in early September nevertheless describe the company as converting roughly 400 beta MSPs into paying customers and scaling commercial operations with new funding. That is credible market validation, but it is not the same as years of production history. G2 currently has an exact OpenFrame product profile with zero reviews, and the broader fixed 50-source panel produced no independent user-rating corpus. ⁵⁷⁸⁹

OpenFrame is most attractive to small and midsize MSPs/MSSPs that feel trapped by per-module and per-technician pricing and want one operational surface instead of a patchwork of RMM, PSA, MDM, security and documentation tools. The combination of managed cloud and self-hosted code gives technically mature providers more deployment choice than many closed competitors. ¹²³

It is a less obvious fit for organizations that require a long independent production track record, a large integration marketplace or conventional enterprise certifications before consolidating critical client operations. Self-hosting also transfers substantial responsibility to the MSP: infrastructure, upgrades, security and availability become operational work rather than a free benefit of “open” software. ³⁶⁴