Flamingo Raises $4.5M Seed Round

Back to Life at Flamingo

Interactive Notifications. Identity-First SSO. Incidents

AI INTEGRATIONINCIDENT MANAGEMENTMINGOPLATFORM UPDATES

September 2026

Month

September 28, 2026

Published

Oleksandr Koltunov

Oleksandr Koltunov

Full-Stack Engineer

In September the team shipped a reworked identity-first OAuth/SSO flow, a new Incidents management tab, conversation compaction for Mingo dialogues, read-only billing info in the desktop app, and native background token/notification handling for mobile, together improving authentication consistency, incident response, chat performance, and mobile interactivity.

  • Shipped: Reworked OAuth flow with identity-first SSO so 'Continue with Google/SSO' behaves consistently across sign-in and sign-up tabs, auto-detecting existing tenants or guiding new organization creation.
  • Shipped: New Incidents tab in the sidebar listing incidents on managed devices, with search/filtering by organization, severity, and status.
  • Why: These changes solve inconsistent login experiences across tabs and give teams a centralized way to triage, investigate, and act on device incidents.
  • How: Incidents integrate directly with Mingo (pre-filled prompts from incident context), ticket creation (auto-filled from incident data), and assignment workflows; SSO discovery checks tenant/domain config to route to custom providers or default flow.
  • Shipped: Added conversation compaction for Mingo dialogues (on-demand or from the dialogue list) using background watchers/subscriptions to track completion.
  • Shipped: Desktop app now shows read-only billing information, redirecting to browser for plan upgrades/management; mobile app gained native token lifecycle management enabling interactive push notifications even when the app is closed.
  • Result: Demoed working end-to-end: incident-to-ticket creation, Mingo session linking, and mobile notification approval flow (e.g. approving a knowledge base article request) all functioned correctly during the walkthrough.

What I Shipped
6

  • Identity-first SSO

    sign-in routes by email, and signup happens in the same screen

  • Native session handling

    the iOS and Android apps own token refresh, so sessions don't drop

  • Actionable push

    approve, reject or reply from the notification

  • Incidents

    detected issues become a ticket or a Mingo chat in one click

  • Compact Chat Memory

    long Mingo chats keep context without the full history

  • Pinned release builds

    every frontend release is tagged, and desktop and mobile build from that tag

Why It Mattered
4

  • Mobile released

    login-only screens and stable sessions match what App Review expects

  • Fewer steps from detection to fix

    incident → ticket → Mingo without retyping context

  • Reproducible builds

    desktop and mobile always ship a known frontend version

  • Know who's calling

    every request reports whether it came from web, desktop or mobile, and which build

What I Learned
3

  • The app must own its tokens

    web-view tokens alone don't survive a mobile app's lifecycle

  • A locked Keychain isn't an empty one

    treat a read failure as "wait", not "sign out"

  • Pin every build to a release tag

    floating dependencies make builds impossible to reproduce

What's Next
3

  • Incidents to prod

    turn on the insights flag beyond dev and QA

  • Use the client-version data

    track which app versions are in use and set a minimum supported version

  • Mobile version control

    check the installed app version against a minimum and prompt users to update in the App Store or Google Play

Oleksandr Koltunov

Oleksandr Koltunov

Full-Stack Engineer

Hi! I’m Oleksandr, and I am currently working as a full-stack engineer. In my role, I design, develop, and maintain different applications, handling both frontend and backend.

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.
In the cloud, on US soil. Your data stays stateside.
Both. It's built for MSPs and MSSPs alike.

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.