Security monitoring that investigates, not just alerts.
Prahari watches your servers, cloud accounts and internet exposure around the clock. When something looks wrong, it gathers the evidence and tells your team what happened, how serious it is and what to do.
प्रहरीprahari, Sanskrit: the sentinel who keeps the night watch.
auth.log · 4 servers● watching
Nov 02 02:09:41 app-07 sshd[2211]: Accepted publickey for deploy from 10.0.4.12
Nov 02 02:10:03 db-2 CRON[8812]: (root) CMD (/usr/local/bin/backup.sh)
Nov 02 02:10:22 lb-1 haproxy[901]: 198.51.100.7 GET /api/health 200
Nov 02 02:11:17 app-12 sshd[3390]: Accepted publickey for root from 203.0.113.45
Nov 02 02:12:00 app-03 systemd[1]: Started Daily apt upgrade and clean
Nov 02 02:12:48 db-2 postgres[611]: checkpoint complete: wrote 412 buffers
Nov 02 02:14:06 app-12 audit: write /root/.ssh/authorized_keys
Nov 02 02:15:31 lb-1 haproxy[901]: 198.51.100.22 GET /login 200
Nov 02 02:19:52 app-07 audit: write /root/.ssh/authorized_keys
Nov 02 02:20:10 app-15 kernel: nf_conntrack: table full, dropping packet
Nov 02 02:21:44 db-2 sshd[1209]: Accepted publickey for deploy from 10.0.4.12
Critical · confidence high
Unknown key added for root on app-12, now on 2 more servers
Why
Login from a hosting network never seen before, outside any deploy window.
Fix
Block the IP, remove the key from 3 servers. Commands included.
Illustrative example. Names and addresses are made up.
How it works
Rules filter the noise. AI does the first investigation.
2.4MCollect
Server events, cloud-account changes and daily scans of everything the internet can reach.
41Detect
Security rules and each server's normal pattern pick out what deserves a look.
3Investigate
The AI pulls related evidence across servers and time, then rates severity and confidence.
1Tell you
One page per finding: what happened, the evidence, why it matters and the exact fix.
Counts shown are an example day
Coverage
Watches the places other tools don't look.
Endpoint tools see inside a server. Prahari also watches the cloud account around it, the traffic leaving it and what the internet can see.
Cloud accounts
Servers created or rebuilt, account-level SSH keys, firewall rules added or detached, snapshot coverage, and outbound traffic per server.
Servers
Who logged in, from where, with which key. New keys, users, services and listening ports. Logs copied off the server straight away.
Internet exposure
Daily port scans of every public IP, exposed databases and admin panels, certificates and DNS changes.
Weaknesses
Software you run matched to new vulnerabilities, ranked by real exposure.
Drift
Root login, password SSH, open firewalls and missing updates, checked against an agreed baseline.
How Prahari behaves
A security tool has to be safe itself.
Never touches your systems
Read-only cloud tokens and an agent that only observes. Prahari never changes your systems.
Runs in your account, not ours
Prahari and its AI run in your own cloud account or on your premises. Your logs and evidence never leave infrastructure you control.
Every alert shows its evidence
Every finding links back to the raw events it came from. Nothing is a black box.
Sees only what it needs
Secrets, passwords, card numbers, emails and phone numbers are removed before the AI reads anything.
Never takes orders from logs
Attackers can write into logs. The AI treats everything it reads there as text and never runs it.
Tells you if it goes quiet
Prahari checks its own health, so silence is never mistaken for safety.
Plainly
Prahari detects, investigates and explains. It does not block attacks on its own, so we recommend running endpoint protection alongside it. No monitoring can promise an attack never happens. Prahari shortens the time between something going wrong and someone who can fix it knowing.
Now onboarding founding customers
Go live in a few days.
Built for teams that run their own cloud servers with little or no security staff. Tell us about your setup and we'll scope it with you.