Why Secure Tokens Plans to Move Its Endpoints to OpenFrame

Stephen Garriques runs Secure Tokens, a small MSP that looks after a few hundred endpoints for small and medium businesses across several industries. He's the main technician and brings in about three other people when a project needs them. His stack is security-heavy and built from single-purpose tools, and he builds his own open-source tooling in house.

He heard about OpenFrame from Michael Assraf at Flamingo, whom he knows personally. What caught his eye was the open-source angle: mature open-source tools, made easy to use from one platform. Getting it running on real endpoints took "next to no time," with no deployment blockers.

At the interview in February 2026, OpenFrame was running next to his current RMM, which is branded as a digital experience platform. His plan: that would probably be his last year on it, and he'd "move strictly over to OpenFrame after that." His reason is consolidation and cost, not a grudge against his vendors.

Stephen moved away from all-in-one RMMs years ago. On those platforms, script and app deployment was hit or miss, and he got tired of it. So he built his stack from tools that each do one thing well. He finds that more reliable.

The tools work. The contracts are the issue. Each tool is its own product and its own bill, and the price tends to go one way over the years. He's fair about his current RMM: "I don't think it's a bad product, but you get locked into these contracts of pricing and stuff like that."

He also knew the open-source alternatives had grown up. Many are mature and work well on their own. But someone has to learn them, wire them together and roll them out. In his words, not a lot of companies were "really willing to kind of put the time in." He was putting that time in himself, stitching open-source tools into an in-house SOC and an asset management platform.

OpenFrame takes mature open-source tools and runs them from one platform. That's the part Stephen cares about. "OpenFrame really gives those types of companies a real alternative where they're not tied down to one single vendor or locked into a contract that gets more expensive over the years."

Setup was quick. He sent out the agents, installed them, and the endpoints showed up in OpenFrame. "Next to no time," he said. Asked about blockers: "No deployment blockers. They're very easy to install."

He also likes how it's put together. It's "built from the ground up," with open-source tools that are each good at one job, managed in one place. That's how he already runs his own stack, without the work of stitching it together himself.

At the interview he hadn't spent much time with Mingo and Fae, OpenFrame's AI agents. What he expects from them is at the end of the results.

At the interview in February 2026, there were no measured results yet: no endpoint count on OpenFrame and no time or cost figures. What he had was a fast setup, no blockers and a plan.

The plan, in his words: "I think this will probably be the last year that I use [my current platform], and I'll move strictly over to OpenFrame after that." The plan is about his RMM, which is branded as a digital experience platform. It doesn't cover his security tools, from endpoint protection and anti-ransomware to email security and DNS filtering. His goal: "lower my costs, consolidate products."

His view on OpenFrame for other MSPs: "It's already a no-brainer in my opinion." And for shops that don't have the time to learn and roll out open source themselves: "OpenFrame has already done all that for you."

What he still wants: reliable backup and disaster recovery, and endpoint protection with an API, so an existing SOC can support it. Those are two of his biggest costs. On the rest: "I think y'all are nailing everything else, though."

What he expects next: AI agents that take on general endpoint maintenance and clear low-level alerts, so technicians can focus on the mid, high and critical issues.