For your organisation
Priced per seat, documented for review
Endpoint protection for a fleet, monitoring for the machines that stay online, and an architecture description precise enough to argue with.
Endpoint protection
Built · not releasedPer-seat licensing for Windows desktops — known-malware detection, USB scanning and device posture checks across a fleet.
From ₹99 per month, incl. GST
Where it standsWeb & server monitoring
Designed · not builtUptime, TLS, intrusion attempts and file integrity, watched continuously, with alerts to the people who run the machine.
From ₹99 per month, incl. GST
Where it standsManaged mobile
In developmentPer-seat mobile safety for staff devices, on the same billing as the desktop fleet.
From ₹99 per month, incl. GST
Where it standsWhat a fleet actually costs
Business licensing is ₹69 per device per month with a minimum of 20 devices — so the smallest Business invoice is ₹1,380 a month, not ₹69. Annually it is ₹690 per device.
The minimum exists because the per-seat rate is below the single-device price; without a floor, one person would buy one Business seat instead of Personal. Below 20 devices, the household tiers are cheaper and we would rather say so.
What we do not have
- No certifications. We hold no ISO 27001, no SOC 2, and we will not describe ourselves as “DPDP compliant” — self-declared compliance is worth nothing to a reviewer, and a certificate we do not hold is worth less.
- No central management console yet. Fleet reporting and a management console are named in the Business tier and are not built. They are labelled as planned on the pricing page rather than listed as features.
- No network-layer protection. Nothing of ours sits in the path of traffic. The desktop product detects known files and hardens a device; it is not a gateway, a proxy or a firewall.
- No remediation on servers. The web and server line alerts your team; it does not log in or change anything. Handing a monitoring vendor write access to production is a larger risk than most of what it watches for.
What a review can actually check
Consent enforced as a precondition in code rather than a recorded preference; evidence records that refuse their own updates and refuse deletion; server-side SHA-256 fingerprinting from the bytes received rather than a client-supplied hash; and per-file encryption whose authentication was exercised against the production key — a flipped byte, a truncated file and another file’s key are each refused.
Our signature feed publishes its own composition, its licence basis and the timestamp of its last successful update, so its freshness is visible rather than asserted.
Architecture and its limitsThe signature feedVulnerability disclosure
Talk to a person
If you are evaluating this for an organisation, write to us and you will reach somebody who can answer specifics rather than a sales sequence. We would rather tell you we are not ready than take a purchase order against a roadmap.
None of this is on sale yet
The Windows build runs but is not code-signed, so it is not published. Mobile is unreleased. The web and server line is scoped and priced with no code written — that is stated on its own page with the evidence, rather than described as “in development”.
If a procurement timeline depends on a date, ask us for one directly and we will give you an honest answer, including “we do not know”.
Every product page says exactly where it stands and how we know — the prices are published in advance so the catalogue is honest about what the company intends to sell, not because anything can be bought.