MokSa
MokSa is a video intelligence platform that layers AI over a business's existing surveillance cameras, flagging theft, unsafe or unhygienic staff behaviour and footfall patterns in real time across retail, hospitality, school and fuel-station sites.
What is MokSa?
MokSa is a video intelligence platform that sits on top of the cameras a business already owns. Rather than selling hardware, it reads existing surveillance feeds and turns them into real-time alerts and operational analytics — what the homepage calls AI powered surveillance that thinks ahead. The company presents itself as a video intelligence solutions provider for businesses, and its terms spell out the scope: theft detection, employee tracking, most visited locations in a store and busiest days, across every business location.
The platform is camera-agnostic, and that is the pitch's centre of gravity. Its FAQ states that no camera replacement is required and that the AI layers onto most existing systems, promising capability without a capital expenditure cycle. Detection is said to rest on a model trained on millions of hours of real-world surveillance footage, tuned to detect what matters and ignore what doesn't. Unusual or suspicious behaviour is flagged automatically in real time, and people counting is claimed at over 95% accuracy with shadows and duplicate counts filtered out. Alerts reach a security team by email, SMS and mobile notification.
Five verticals are addressed: retail spaces (convenience stores, general stores, supermarkets), hospitality and lodging (hotels, guest houses, resorts), educational institutions (schools and universities), fuel and service stations, and food safety monitoring for any premises with a kitchen or food-handling area. In that last case the platform watches staff hygiene and sends instant notifications when standards slip. A published case study for the retailer Lion Stop reports a 38% cut in shrinkage that had been running at 4 to 5.7% of store revenue, alongside footfall analytics used to rework layouts, store-specific dashboards and privacy-first facial blurring.
Scale runs from a single-location small business to enterprise multi-site rollouts. Deployment is quoted at 24 to 48 hours, and at 30 minutes per store in the case study, with no extra bandwidth or staff. Compliance is signposted through third-party validated SOC 2 Type 2 and GDPR badges. What the site never publishes is a price: the only route forward is booking a demo.
What it does
- Detect theft as it happens and alert staff instantly
- Flag unusual or suspicious behaviour automatically
- Count people and measure footfall, at a claimed accuracy above 95%
- Monitor staff tasks and hygiene compliance in food-handling areas
- Push alerts to a security team by email, SMS or mobile notification
- Surface busiest days and the most visited areas of a store
- Blur faces in footage for privacy compliance
When to use MokSa / When not to
A quick filter to help you decide if MokSa is the right fit.
When to use MokSa
- Multi-site retailers — convenience stores, general stores and supermarkets — losing revenue to shrinkage
- Hotel, guest house and resort operators wanting oversight of guest-facing areas without buying new hardware
- Food businesses that must evidence kitchen hygiene and staff compliance across several locations
- Schools and universities adding automated threat detection to an existing campus camera network
- Security and loss-prevention managers who need instant alerts rather than footage to review after the fact
When not to use MokSa
- Buyers who need published pricing or a self-serve signup: every path on the site ends at a sales demo
- Developer teams expecting an API — no documentation, endpoint or integration guide is published
- Procurement and data protection officers requiring a DPA, a subprocessor list or a stated hosting region before signing
- Households and individuals after consumer-grade camera monitoring; the product is sold to businesses only
- Online-only businesses with no physical premises or cameras for the platform to read
How to use MokSa
A typical end-to-end flow, from setup to results.
- Check that your sites already run camera systems — MokSa adds AI to them rather than replacing them
- Book a demo from any page of the site; the button opens a scheduling slot with the team
- Or use the contact form, write to info@moksa.ai, or call +1 313-887-8586, with a reply promised within 24 hours
- Discuss scope with the vendor: which locations, which detections, which vertical applies
- Agree commercial terms directly, since no price, plan or self-serve signup is published
- Let the team connect the platform to your existing feeds — most deployments are quoted at 24 to 48 hours
- Decide who receives alerts and through which channel: email, SMS or mobile notification
- Review incidents, footfall and busiest periods in the store-level dashboards
- Feed footfall analytics into layout decisions and hygiene alerts into staff compliance routines
- Turn on facial blurring wherever local privacy rules require it
Pros & Cons
Pros
- Works with cameras already installed — no hardware replacement required
- Fast to stand up: 24 to 48 hours quoted, and 30 minutes per store in the published case study
- Third-party validated SOC 2 Type 2 and GDPR badges, both linked to an external validator
- A concrete, quantified customer result: 38% less shrinkage at Lion Stop
- Facial blurring built in as a compliance feature rather than sold as an add-on
- One platform covers retail, hospitality, education, fuel stations and food safety
- Scales from a single shop to multi-site enterprise deployments
Cons
- No published pricing at all: the pricing path returns a 404 and every route ends at a sales call
- No free plan and no documented trial; the 'Try for free' button on the case studies page leads nowhere
- No API, no technical documentation and no app store listing, despite advertised mobile notifications
- A thin website: the features page renders only a loading state and the FAQ answers are absent from the served HTML
- A single published case study, covering one retailer
- No DPA, no subprocessor list, no stated hosting country or region, and no named EU Article 27 representative
- Terms last updated in March 2024 declare Indian governing law against exclusively US addresses, and still carry template text describing the site as offering recruitment services
Pricing & Plans
No pricing is published. MokSa operates no pricing page — the pricing path returns a 404 — and no plan, rate, currency or billing unit appears anywhere on the site. There is no permanent free plan and no documented free trial; the only free elements stated in the terms are access to the website itself and the newsletter subscription. Commercial terms are obtained by booking a demo, and the terms reserve the right to change or discontinue the sale of any service, or its price, at any time, with changes posted on the website.
Data, GDPR & hosting
A consolidated view of how MokSa handles your data.
GDPR overview
GDPR is addressed concretely. The homepage carries a GDPR badge next to a SOC 2 Type 2 badge, each linking to a third-party validator, under the claim of being independently audited and certified; the site's FAQ states compliance with GDPR, CCPA and other relevant regulations. The Privacy Statement, effective October 2025, lists EU data subject rights — access, rectification, objection, erasure, restriction, portability and protection against solely automated decisions — and places international transfers under EU Commission approved standard contractual clauses. Moksa.ai, Inc. is named as controller and a Data Protection Officer is reachable at info@moksa.ai. Two gaps remain: the Article 27 EU representative is said to be appointed but is never named, and no DPA or subprocessor list is published.
Who owns the data?
The terms name Moksa.ai, Inc. as the controller of personal information for EU data subjects, and reserve site content and trademarks to MokSa.ai, its affiliates and third-party licensors. Anything a user posts in a public area of the site or emails to the company carries a non-exclusive, royalty-free, worldwide, perpetual licence, with a right to sub-license, covering reproduction, distribution, derivative works and public display, plus the right to use the contributor's name in related advertising. Customer video footage is never addressed: the terms note only that data sits on an external server run by an unnamed technical partner, for which MokSa disclaims any liability in the event of loss.
Reuse rights
The rights granted run in one direction. A user may print and download portions of the site for personal, non-commercial use provided copyright notices are left intact; modifying, copying, reproducing, republishing, transmitting, redistributing or caching any part of the site is expressly prohibited without separate written permission. Nothing in the documents allows an end user to reuse MokSa's material or content commercially without asking first. In the other direction, material submitted to public areas of the site or sent by email may be reproduced, distributed, sub-licensed and turned into derivative works by MokSa without further consent, and the contributor's name may be used in the advertising and promotional material attached to it.
Data retention & training
Hosting summary
MokSa publishes no hosting location. Neither a country nor a region is named for customer data, and no subprocessor list exists. The terms state only that data is stored on an external server maintained by a technical partner who is never identified, and disclaim responsibility for any resulting data loss. The privacy statement covers transfers rather than hosting: personal information may move outside the user's home country or region, including outside the European Economic Area, to the United States and other countries where MokSa, its affiliates or its business partners maintain facilities, with EU Commission approved standard contractual clauses cited as the safeguard. For reference, the public website itself resolves to 76.76.21.21, an anycast address geolocated in the United States, but that describes the marketing site's infrastructure and says nothing about where video or analytics data is processed. Buyers with a data residency requirement will need to obtain that commitment in writing.
Things to keep in mind
Risks and trade-offs to weigh before adopting MokSa.
- Filming staff for task and hygiene monitoring carries employment-law and staff-consultation obligations that the site never addresses; the burden falls entirely on the buyer
- Automated behaviour flagging invites over-trust: a suspicious-activity alert is a statistical signal about a person, and treating it as proof is how such systems produce unfair outcomes
- The terms declare the laws of India as governing law while every address and legal reference in the document is American, which muddies where a dispute would actually be heard
- A single generic mailbox, info@moksa.ai, serves support, legal, the Data Protection Officer and the EU representative, so a rights request has no dedicated channel
- The privacy statement permits broad profiling: data combined across sources and devices, enriched from third parties and business partners, and used for targeted advertising, with opt-out only by emailing the company
- Retention is a floor and not a ceiling — at least six months of backups, with no published maximum and no deletion schedule
- Certification badges resolve to a third-party validator, with no scope, date or certificate detail shown on the site itself
Setup & Integrations
Technical difficulty
Low, as presented. No camera replacement is needed, since MokSa states that it integrates with most existing systems. Most deployments are quoted at 24 to 48 hours with minimal disruption, and the published case study reports being fully operational within 30 minutes per store, with no additional bandwidth or staff. The real constraint is commercial rather than technical: there is no self-serve signup, so setup happens through the vendor after a demo. No public documentation describes network or camera prerequisites, so the real-world effort cannot be verified independently.
Deployment
Behind MokSa
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Frequently asked questions
How is MokSa different from a traditional CCTV system?
Do I have to replace my cameras?
How accurate is the people counting?
Can it detect suspicious behaviour on its own?
Is it only worth it for large deployments?
How long does deployment take?
How are alerts delivered?
What does MokSa cost?
How long is data kept?
Is MokSa GDPR compliant?
Should you pick MokSa?
MokSa makes a narrow and sensible promise: keep the cameras you have, and add a layer of AI that watches them for you. That framing removes the usual barrier to intelligent surveillance, the capital cost of new hardware, and it is backed by the strongest evidence on the site — a customer case reporting a 38% reduction in shrinkage that had been running at 4 to 5.7% of store revenue, plus SOC 2 Type 2 and GDPR badges verified through an external validator.
Against that sits an unusual amount of commercial opacity. There is no price, no plan, no trial and no self-serve signup; the only route is a demo booking, and even the Try for free button on the case studies page leads nowhere. Buyers needing a data processing agreement, a subprocessor list or a stated hosting region will not find them, and the EU representative required under Article 27 is declared but never named.
The legal documents are the weakest link. The terms were last updated in March 2024 while the privacy statement dates from October 2025; they declare Indian governing law against exclusively American addresses, and their definitions still carry template text describing the site as offering recruitment services. None of that is disqualifying, but it signals a young company whose paperwork has not kept pace with its product: the domain's first web archive capture dates from September 2023, and trade press reports a USD 1.5 million pre-seed in March 2024.
MokSa is worth a conversation for multi-site retail, hospitality, education, fuel and food-service operators facing a real shrinkage, hygiene or footfall problem with cameras already in place. Treat the accuracy claims as vendor claims, ask for the certification scope and a processing agreement in writing, and settle the employment-law implications of filming staff before signing.
- Choosing a selection results in a full page refresh.
- Opens in a new window.