How It Works
CharikaControl keeps day-to-day operations local to the customer environment. The local server hosts the dashboard and data services, the Windows agent reports endpoint activity, and the central authority remains responsible for activation and license trust.
Activation issuance, signing, and validation continue to use the existing CharikaControl activation authority flows.
Deploy the local server
The local server hosts the dashboard, operational APIs, alerting, package workflows, and the local MongoDB-backed data layer used by the product.
Install the Windows agent
The Windows agent runs on the monitored endpoints, sends local activity to the server, and applies practical endpoint-side policies such as USB enforcement where supported.
Activate through the authority
Key validation, issuance, signing, and server linking still come from the central CharikaControl activation authority. The protected activation routes stay unchanged.
Operate locally
Once activated, the customer runs the dashboard locally for device visibility, alert review, analysis, USB policy handling, and backup monitoring.
Architecture in practice
- The local server is the operational center for the customer environment.
- The dashboard is used by local operators for alerts, analysis, events, backups, execution, and configuration.
- The agent collects device activity and reports it back to the local server over the product transport.
- The activation authority remains separate and authoritative for activation artifacts and license state.
- The local-first model reduces dependence on a permanent external SaaS data path for day-to-day operations.
Implementation sequence
Choose the right commercial package
Explain the commercial offer and the activation scope.
This block is admin-managed and can later feed the website landing page or portal guidance without code changes.
Download the required packages
Surface package availability and installation notes.
The download and package layer is configured in the backend and can later be exposed to logged-in users safely.
Activate and operate
Keep the activation authority flow unchanged while improving the commercial layer around it.
Existing activation, signing, replacement, revoke, and validation flows remain authoritative and are not replaced by this extension layer.
Operate locally
Use the dashboard for day-to-day monitoring, alerts, analysis, USB policies, and backup visibility.
Once deployed and activated, the customer works locally through the dashboard instead of relying on a remote SaaS console for normal operations.