Flamingo Raises $4.5M Seed Round

Try for Free
Back to Life at Flamingo

Shipped Scheduled Scripts Client side and Self Update for Desktop application

ARCHITECTUREIMPLEMENTATIONOPENFRAMEPERFORMANCEPLATFORM UPDATES

August 26, 2026

Published

Denys Slieptsov

Denys Slieptsov

Client Engineer

Shipped client-side support for scheduled scripts and completed self-update for the OpenFrame desktop application. Both features target reliability: scheduled scripts now use a new persistent key-value storage so results reliably reach the backend, and desktop self-update is working smoothly and now in QA testing.

What I Shipped
3

  • Client-side support for scheduled scripts

    Built the client-side piece of scheduled scripts, complementing the front-end/back-end work done by teammates, including persistence for script results.

  • New persistent key-value storage on the client

    Introduced a new key-value storage system, moving toward Jetstream for greater persistence, so script results are reliably sent to the backend.

  • Self-update for the OpenFrame desktop application

    Completed the self-update feature; it now works smoothly and is in QA testing.

Why It Mattered
3

  • Scheduled scripts were dropping results

    Results were sometimes lost before reaching the backend; the new persistence layer ensures they're safely and reliably delivered.

  • Reduces manual maintenance

    Self-update for the desktop app removes the need for manual upgrades, improving reliability for users.

  • Lays groundwork for future storage needs

    The new encrypted key-value storage is designed to eventually also hold credentials and other data currently stored as plain files.

What I Learned
2

  • Persistence fixes root-cause reliability issues

    The dropped-result problems in scheduled scripts were resolved by introducing persistent sending rather than patching symptoms.

  • Verified against real tenant traffic

    Checked results against the Morite OpenFrame AI tenant, which actively runs scheduled scripts, and confirmed almost all recent runs completed successfully.

What's Next
3

  • Expand persistence for script results

    Continue moving more script-result handling onto Jetstream-backed storage for even greater reliability.

  • Migrate credentials to encrypted storage

    Move credentials and other file-based data into the new encrypted key-value storage.

  • Push self-update through QA to release

    Continue QA testing on desktop self-update and move it toward general release.

Denys Slieptsov

Denys Slieptsov

Client Engineer

Hey! I’m Denys, a software engineer here at Flamingo. I focus on system-level development, mostly working with Rust to make our apps fast, reliable, and smooth. Always up for optimizing things and choosing the best solutions, bringing new ideas.

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.