OpenFrame

OpenFrame v0.3.7 - Enhanced Developer Experience

Version: 0.3.7

AIAI INTEGRATIONAUTOMATIONDEVELOPER EXPERIENCEDOCUMENTATIONINTEGRATIONOPENFRAMEPERFORMANCEPLATFORM UPDATESSECURITYUSER EXPERIENCE

MINOR

Release Type

BETA

Release Status

December 23, 2025

Release Date

Michael Assraf

Michael Assraf

Founder and CEO

This release transforms the OpenFrame developer experience with comprehensive documentation, Windows CLI compatibility, and streamlined cloud deployments. We've optimized build times, enhanced authentication flows, and introduced AI agent integrations to make development faster and more intuitive.

Features Added
4

  • AI Agents Integration (Fae and Mingo)

    Integrated Fae and Mingo AI agents with real-time NATS messaging for instant updates and enhanced user interactions

  • Social SSO Auto-Login

    Seamless authentication with automatic login after Google or Microsoft SSO authentication - no additional verification required

  • Enhanced Cloud Environment Launch

    Track real-time progress during cloud deployments, parallelize operations for faster launches, and execute custom pre-launch scripts

  • Billing and Subscription Management

    Complete billing system with subscription management, payment processing, invoicing, and usage tracking

Bugs Fixed
2

  • Windows CLI Compatibility Fixed

    Resolved Windows-specific issues including path handling, command execution, and environment variable management for full cross-platform support

  • Frontend Build Time Optimization

    Fixed slow compilation times with incremental builds, improved caching strategies, and optimized build tools

Improvements
5

  • Comprehensive Documentation Overhaul

    Complete rewrite of CLI and platform documentation with step-by-step guides, API references, troubleshooting sections, and real-world examples

  • Container Registry Migration to GHCR

    Migrated all Docker images to GitHub Container Registry for improved reliability and faster deployments

  • Unified Frontend Library Architecture

    Consolidated frontend common components into openframe-frontend-core with automated npm publishing

  • macOS Code Signing Implementation

    Automated code signing for macOS builds to prevent antivirus false positives and improve security

  • Simplified Logging Architecture

    Removed Loki dependencies across all microservices for a cleaner, more maintainable logging solution

Related Links

Github Release0.3.7
Github Release0.3.7
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

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.
An AI agent for an MSP is software that reads a ticket, decides the action, performs it across your tools, and records the result without a technician driving each step. It differs from a chatbot or copilot by taking action, not just suggesting one.

AI MSP

MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Most MSPs start with AI features inside their existing PSA, RMM, and ticketing systems rather than standalone products. Common categories include AI ticket triage, alert correlation, scripting assistants, and AI-native all-in-one platforms like OpenFrame that run intelligence across the whole stack.
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%.

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.