RFF Reviews and Details

Questions & Answers

1. What makes RFF unique?

   RFF is Windows-only on purpose, and it goes deep on the surfaces other RMMs skip. Group Policy is captured as a readable, versioned baseline you can diff for drift, down to which GPO set each value. It pushes software to machines that have no agent installed at all, over SMB and WMI. It installs apps that refuse SYSTEM context into the signed-in user's real session, the classic SCCM blind spot. It takes a wiped machine to named, enrolled and domain-joined off one USB stick, pulling Windows straight from Microsoft so there is no golden image to maintain. And every operational feature is on every plan, including the free one: you pay for the number of machines, not for capabilities.

2. Why should a person choose RFF over its competitors?

   Three concrete reasons. Pricing is published and self-serve: free for 100 endpoints forever, then $149/mo including 100 and $2.00/endpoint above that with no cap, no per-technician seats and no sales call. Gating is by scale, not capability, so a 40-machine shop gets vulnerability scanning, conformance baselines, BitLocker recovery-key escrow and remote desktop on the same terms a 2,000-machine one does. And support is the founder's inbox, usually answered in hours, by someone who ran Windows endpoint management for a hospital fleet of tens of thousands of devices on SCCM, Tanium, Intune and PDQ. RFF is also honest about the trade: Windows only, no PSA or ticketing, no network monitoring. If those are must-haves, something else fits better, and our comparison pages say so.

3. How would you describe the primary audience of RFF?

   Windows-first internal IT teams running roughly 100 to 2,000 endpoints, plus small and mid-size MSPs managing several client fleets. Usually a one-to-five person team that has outgrown scripts and ad-hoc tools, finds SCCM too heavy to keep alive, and has hit the gaps in Intune for anything that is not a modern-managed laptop. Regulated shops in healthcare, finance and legal come for the compliance export, BitLocker escrow and audit trail. Not a fit for macOS, Linux or mobile fleets.

4. What's the story behind RFF?

   RFF is built by Brian Vitko, who spent years running Windows endpoint management for a hospital: tens of thousands of devices across SCCM, Tanium, Intune and PDQ. The pattern never changed. The expensive tools could not do the ordinary thing, like install an app into a user's session, tell you which GPO actually set a value, or patch the laptop that was asleep at deploy time. The affordable tools stopped wherever the vendor decided "small business" ended. RFF is the tool that would have saved that team its worst weeks: every feature on every plan, priced by machine count, and honest about what it does not do. It is built and supported by one person, which is why the founder's inbox is the support channel.

5. Which are the primary technologies used for building RFF?

   .NET 8 and ASP.NET Core (C#) for the API, PostgreSQL with EF Core for storage, with tenant isolation enforced at the database layer via row-level security. SignalR over WebSockets carries live job events and remote desktop. Redis handles rate limiting. The console is React 18 with TypeScript, Vite, Tailwind CSS, TanStack Query and Zustand. The Windows agent is C#, runs as a service, and talks outbound HTTPS on 443 only. Hosted on Render, with Cloudflare for DNS and R2 for package artifacts, Stripe for billing and Sentry for error tracking.