The Frontier
Open-source tools cover a lot of what a Linux server needs. Where they fall short, we build our own, test each one, and add it to the suite once it passes. Our sensors keep finding new attacks, so the work never stops.
Three pieces, kept honestly apart
There are three parts to protecting a small Linux server, and we keep them clearly separated so you always know what you are paying for.
- What open source gives you. A lot. We list the open-source tools you could run yourself, honestly, on Do it yourself — no sign-up, and it costs nothing but your time.
- What we wrap for you. We install those jobs, keep them current, run them across your servers and report in plain English, with every fix left for you to approve. That is how the suite works.
- What only we build. The Frontier: the places open source doesn't reach, where we build our own tools in-house and add them to the suite once they pass our tests.
Why the Frontier exists
Open-source security tools are good, and for much of what a server needs they are enough. But not for everything. Some attacks are too new. Some checks don't yet exist in a form a small, low-cost server can run. And some problems simply have no good open tool behind them. Where we hit one of those gaps, we don't pretend a tool covers it. We build the answer ourselves, and we tell you plainly which jobs the suite does.
Catch, build, test, add — and it never stops
The Frontier runs all the time, on the same engine that feeds the rest of the suite.
We catch real attacks
Our honeypot sensors pose as ordinary Linux servers around the world and record what attackers actually do, every day. That is where the work begins.
We find what nothing else covers
When an attack, a weakness or a check has no good tool behind it, that gap is where the Frontier goes to work.
We build it and prove it
We build the tool in-house and test it in our lab. Anything that touches malware is built and tested only on isolated machines with no network, so it can never reach anything real. It ships only when it passes.
We add it to the suite
Once a tool passes, it joins the suite and reaches you as an update — at no extra cost. Then we start on the next gap, and the cycle runs again.
What we will and won't say here
We describe the process, not promises. We name a specific Frontier tool on this site only once it has been built, has passed its tests and is part of the suite — never before. We won't claim a tool exists until it does, and the parts of the suite you can use are listed on how it works.
The map of what we are building, and in what order, stays ours. What you see is the result: tools that passed, added to the one suite you already pay a single price for.