Flamingo

OpenFrame v0.3.4 - Enhanced Stability & Cross-Platform Support

Version: 0.3.4

BACKUPBEST PRACTICESINTEGRATIONOPENFRAMEPERFORMANCEPLATFORM UPDATESSECURITYTOOLSUSER EXPERIENCE

MINOR

Release Type

BETA

Release Status

December 13, 2025

Release Date

Michael Assraf

Michael Assraf

Founder and CEO

This beta release focuses on improving system stability and ensuring feature parity across Windows and Mac platforms. Key improvements include reverting to a stable Apache Pinot version, adding S3 backup capabilities, and fixing critical Windows CLI compatibility issues. Enhanced file search and SSO integration round out this release with better user productivity features.

Features Added
4

  • File Search Capability for File Manager

    New file search feature that indexes and searches files by name, type, and metadata for fast retrieval, improving productivity by eliminating manual folder navigation

  • S3 Backup Integration for Pinot

    Automatic backup functionality to Amazon S3 storage for data redundancy and disaster recovery capabilities

  • SSO Support for Invitations

    Users can now register and accept invitations via Google/Microsoft SSO for seamless authentication

  • Remote Sessions in New Windows

    Remote access control sessions now open in separate browser windows, allowing better multi-session management

Bugs Fixed
4

  • Apache Pinot Stability Issues

    Reverted to proven stable version 1.4 to resolve reliability issues with newer versions, restoring consistent uptime for log aggregation and real-time querying

  • Windows CLI Compatibility

    Fixed path handling, command execution, and environment variable management issues specific to Windows, ensuring feature parity with Unix-based systems

  • Tools Registration Endpoint Error

    Resolved 400 Bad Request error occurring in the Tools Registration integration endpoint during registration requests

  • Fae Initial Load Issue

    Fixed issue preventing Fae from loading correctly on initial startup

Improvements
1

  • Mac Self-Update for Integrated Tools

    Aligned Mac client capabilities with Windows to ensure feature parity across platforms

Related Links

Github Release0.3.4
Michael Assraf

Michael Assraf

Founder and CEO

Hey everyone, I'm Michael - founder and CEO of Flamingo. Before this, I built Vicarius, a cybersecurity company focused on vulnerability remediation, where I raised over $60M in funding. Working closely with service providers through that journey, I saw firsthand how MSPs were losing money to vendor payouts and inefficient systems - and that's when the idea for Flamingo clicked. I set out to build an open-source platform that dramatically increases MSP margins while helping them deliver better service to their clients.

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Onboarding Guides

Frequently Asked Questions

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.
Both. It's built for MSPs and MSSPs alike.
In the cloud, on US soil. Your data stays stateside.

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.

AI MSP

Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

AI Safety

It can be, with governance. Keep a human in the loop on high-risk actions, log every automated step for audit, and choose platforms that keep your data yours with no vendor lock-in. Pilot on internal data first so you catch issues before client systems are involved.

AI for MSPs

Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.