Built by BIDUA Industries. Measured, not promised.
Safeavio Sentinel started as Safeavio ServerGuard, a server monitoring and protection platform, and is growing into protection for people, families and organisations — with every page saying plainly what works today.
One family, two halves that never share authority
Consumer editions protect your own device and can only take reversible actions. Business editions administer servers and fleets. They share threat intelligence and one event format; they never share credentials or remote-control authority.
- Sentinel PersonalNot released
- Safeavio Sentinel MobileAvailable
- Sentinel FamilyLimited
- Sentinel PremiumComing
- Sentinel for Small BusinessLimited
- Sentinel Enterprise XDRLimited
- Safeavio ServerGuardAvailable
From a server dashboard to a security family
- Safeavio ServerGuard begins
The first commit of a server monitoring and protection platform, deployed at safeavio.com the next day with a backend, web dashboard and agents for Linux, macOS and Windows.
- Scanning across three operating systems
Security scans with matching depth on Linux, macOS and Windows, a command queue for machines behind NAT, and a first set of protection features.
- The architecture is written down
Fifteen architecture specifications, a live detection pipeline mapped to MITRE ATT&CK, Android device protection brought into one timeline, and every piece of seeded demo data removed.
- Isolation, verified against a real database
PostgreSQL row-level security tested against a real server, an isolated staging environment, and a single status file made the authority on what is live.
- Five production deploys in one day
Tenant isolation on every write and ingest path, Ed25519-signed agent updates, an audited server-command lifecycle, daily backups with a weekly restore drill, and an incident recovered without losing an event.
- Safeavio Sentinel
Role-based access with named permissions, the new web console for personal, business and security-operations users, and this public site — which states what works today and what does not.
- Production moves to PostgreSQL
At 21:06 UTC the live hub switched from SQLite to PostgreSQL with row-level security enforced; the event store and command tables followed on 3 October.
- Protecting servers and families
Endpoint isolation, token actions with a two-person rule, scheduled reports, device groups and update rings, family sharing, UPI checks and reversible quarantine on servers.
- The Android app meets real phones
Every catalog screen built and tested on a physical phone, DNS protection, phone takeover signals, per-device licences, vulnerability management, SOAR playbooks and white-label branding for service providers.
- Scans, a virus list and honest pricing
Quick and full phone scans with a signed virus list that updates itself, automatic protection, family safety on the phone, one secrets file, encrypted off-site backups and prices in rupees with coupons.
Numbers we can show you the source for
- Attack families tracked
- 127
- coverage register
- Detected end to end
- 1
- rule, sensor and test
- Editions
- 7
- product boundary spec
- Architecture specs
- 15
- written before the code they govern
- Trust boundaries
- 9
- each one written down and tested
- Row-security policies
- 300
- enforced on PostgreSQL in production
- Access roles
- 6
- fixed permission bundles
- Certifications held
- 0
- and we say so
Six rules we hold ourselves to
Every capability is marked available, limited, not released or coming. A status only moves up with a rule, a real input and a test.
We will never claim 100% protection, zero battery use or an unhackable product. We publish measurements instead, when we have them.
Files, browsing, keystrokes and screen never leave it. Reporting is opt-in on consumer devices, and revoking it stops events already queued.
Consumer protection can only take reversible actions. Only the server product may take privileged actions, and only at an administrator's instruction.
When a security boundary is crossed by a bug rather than by design, the system refuses the request and writes it down. It does not half-succeed.
We verify the running system, not the HTTP status. Our status file records what was checked, what was not, and why a change was rolled back.
Things we do not publish, on purpose
We do not show customer names, logos, testimonials, team photos, award badges or uptime percentages. None of them would be backed by something we could show you, so none of them appear. When there is a named partner, an audit report or a measured figure, it will be here with its source.
- Developed and operated by
- BIDUA Industries Pvt Ltd
- Marketing partner
- Ramaera Industries Ltd
- Payments and billing
- BIDUA Industries Pvt Ltd
- Registered office
- Suite 209, C-104, Sector 65, Noida, Uttar Pradesh 201301, India
- CIN
- U72100UP2024PTC213229
- GSTIN
- 09AANCB0882D1ZM
- Service
- safeavio.com
- Contact
- [email protected]