SoMo Technologies Tests OpenFrame in Beta

Anthony Gormley, who goes by Tony, is a self-taught engineer at SoMo Technologies in Missouri. He has been in business for 10 years. He looks after 15 commercial locations with about 150 computers, plus about 100 residential machines on break-fix. His clients include two nursing homes, municipalities, police departments, a food distributor and payment processing, so HIPAA and PCI come with the job.

He keeps costs low and watches his locations from his own open-source server. Part of the draw to Flamingo was AI: "You guys are bringing AI into the board." At the interview in December 2025 he was testing OpenFrame in beta, alongside his existing tools. His verdict so far: "So far so good. Everything seems to be working." His healthcare sites were on hold until two HIPAA needs were met.

Tony isn't fighting fires. On his commercial sites, he says, "it's pretty peaceful." At one location he's had three tickets in seven years. His view of service is simple: "I say that the best customer service is when they don't have to reach the help desk."

The strain sits behind the scenes. He watches all his locations from an open-source server he runs at home, and over the years that has meant storage issues and hardware dying.

He also wants software to take the small, dull jobs off his plate. In his words: "I'm just needing a piece of software that just does all the stupid stuff that I don't want to do. Like password resets, and just keep people at bay." He doesn't have many repeat processes to hand over. Password lockouts are the main one.

He uses AI himself, but the tools he ran for clients had none built in. That is part of what caught his eye about OpenFrame.

Tony joined the OpenFrame beta and put the agent on his own servers first. "I have a domain controller that works fine. I have a SQL server that works fine." One terminal server wouldn't take the chat agent, and he wasn't sure yet which side the issue was on.

He worked through the remote shell, PowerShell and the security posture view, and kept a running list of what he wanted changed. His read on the platform: "I'm not wanting this stuff to snap a finger, it'd be all magic. But functionality seems to be fine."

Fae, the AI agent that sits on client machines, got his attention too. He tested her himself with a slow computer: "She does do a pretty good job of finding exactly what is causing the slowdown." His clients spotted her on their screens and asked who she was. None of them had chatted with her yet. "All the chats have been me," he said.

Healthcare is where he takes it slow. Before OpenFrame goes on his nursing home sites, he needs an on-screen notice when a tech connects, and a Business Associate Agreement. His terms for the beta are clear: "I don't mind helping out the project, as long as security stays a must and logs are clean and nothing's crazy."

At the interview in December 2025, Tony's results were early beta results, not hours saved. He was running OpenFrame alongside his existing tools, not in place of them.

The core worked where he tried it. The agent ran on his domain controller and SQL server, and in his words, "functionality seems to be fine." His overall verdict: "So far so good. Everything seems to be working." He was clear it was still a beta: "It's work in progress, that's for sure."

Fae made a first impression on both sides. In his own tests she pinned down what was slowing a computer. His clients noticed her too: "Some of my clients have noticed her and they said, hey, who's that lady?" When he told them, their reaction was "oh, AI cool."

What he still wants, framed as polish: BitLocker keys in the security posture view, full admin rights in the remote shell and PowerShell, the chat agent installing on his terminal server, a way to move devices between organizations, a way to pause Fae and take over a client chat, a mobile app, and Mac device management. For his HIPAA sites, he needs an on-screen notice when a tech connects, and a Business Associate Agreement.