Why we built an agentless monitoring platform
For 20+ years we built software that other people's businesses ran on. Systems for Oracle, for Mobileye, for government agencies, the kind that cannot be quietly wrong on a Sunday night.
That work put us inside a lot of other people's infrastructure, and the trouble we were called in on was never dramatic. A config changed on the way to fixing something else, and broke something unrelated three weeks later. A token expired on a Friday, so the nightly export wrote nothing until Monday. An API failed for days into an error log nobody reads. A backup reported success for six weeks while nothing landed.
No alarms. Just silent changes
In every one of them the servers were up and the dashboards were green. Something had changed without being noticed, or stopped happening without being missed. All of them were cheap to prevent and expensive to fix.
So we built what we kept wishing for. Alertica watches the systems you connect it to and tells you when something changes unexpectedly, or when something that should have happened didn't. It started as a security tool and it still is one, but most of what it catches day to day is a system quietly not doing its job, which is why the alert goes to whoever can act on it: the developer who made the change, or the manager waiting on the report.
What Alertica watches
Alertica is an agentless monitoring platform for files, folders and device configuration. It connects over the protocols your systems already speak, so there is nothing to install and nothing running on the systems you watch.
It reads names, sizes, dates and configuration values, and a fingerprint of each file made on your own server, so it sees when content changes even if the date doesn't. Your file contents never leave your server. An error log that suddenly starts growing tells you an API is failing, without anyone reading a line of it.
It also alerts on absence, which is the half most tools miss. A report that stops being generated, a backup that never lands, a file that should have arrived and didn't.
- FTP
- FTPS
- SFTP
- SSH
- Hikvision ISAPI
More device types are on the way.
Support that starts at the technical detail
-
Seven days a week
Support runs seven days a week, not the working week. Weekend alerts tend to be the ones that matter, so there is someone to take them.
-
Human technical support
The person who answers is an engineer. Nobody reads from a script, and nobody takes a message to pass on. You explain your setup once, in the terms you would use with your own team.
Questions we hear most often
What Alertica watches, and how it differs from the tools you already run.
-
What is Alertica?
Alertica is an agentless monitoring platform that watches your infrastructure for unexpected change, and for the things that should have happened but didn't. It connects over the protocols your systems already speak, so there is nothing to install anywhere.
-
What can Alertica monitor?
Files and folders, reached over FTP, FTPS, SFTP or SSH: files created, modified or deleted, unexpected file types, size and growth thresholds, and files that should have arrived but never did. It also monitors Hikvision camera configuration through the vendor's own ISAPI endpoints. More device types are on the way.
-
What does agentless mean?
Nothing is installed on the systems you monitor. Alertica connects to them the way an administrator would, over the protocols they already expose, and only ever reads. There is no software to deploy, no agent to keep updated, and nothing running on your systems that could slow them down.
-
Does Alertica access our sensitive data?
No. It reads names, sizes, dates and configuration values, and fingerprints of your files made on your own server. Your file contents are never copied, sent to us or stored.
-
How is this different from server or uptime monitoring?
Uptime and performance tools tell you whether a system is healthy. Alertica tells you what changed on it. A server can be online, responsive and perfectly healthy while a file sits in a folder it has no business being in.
-
How is Alertica different from a SIEM?
A SIEM collects and correlates logs from across your estate, and you have to ship those logs to it first. Alertica watches the systems themselves, with no pipeline to build, and answers a narrower question. What changed here, and should it have? Plenty of teams run both.
-
Can Alertica tell us when something doesn't happen?
Yes, and that is often the more useful half. A report that stops being generated, a backup that never lands, an API that has stopped recording the calls it used to record. If something should have happened and didn't, Alertica treats that as an alert in its own right.
-
How do alerts reach us?
By email on every plan, and by SMS from Pro upwards. Routing is set per rule, so the people who need to act on a particular change are the ones who hear about it.
-
What do we need in order to connect a system?
The connection details and a set of read-only credentials for each system you want watched. Most are connected in minutes, and nothing about the system itself has to change.
-
Can we start with just a few systems and add more later?
Absolutely. Most customers start with whatever they would least like to be surprised by, then widen coverage from there. Plans scale with what you monitor, so nothing has to be decided up front.
-
Does Alertica help with audits and compliance?
It gives you evidence. Every change Alertica detects is recorded with what changed, where and when, and scan history is kept for the period your plan covers. So instead of telling an auditor that you monitor your systems, you can show them.
-
Who is behind Alertica?
A team that has built mission-critical software since 2004, for companies like Oracle and Mobileye and for government agencies. When you get in touch, the person who answers has real engineering experience, not a support script.
Stop breaches before they start
Get a personalized tour of Alertica from one of our team members and learn how it can fit your infrastructure.