Keep your existing system.
Add the unseen guard.

No. Niwaban adds a location and policy layer to the customer’s approved device-management service. It uses the controls that the chosen platform and device already support.

We start with enterprise-managed Android phones and Wear OS watches and review the controls available through your existing MDM. Apple integration is scoped separately against supervised-device and device-management support. We confirm each model and enrolment mode before deployment.

Usually not. Suitable company-owned devices can join through the existing enrolment process. We confirm exact models, operating-system versions and supported controls before rollout.

Niwaban never listens to or records conversations. On supported enrolled devices, a configured per-app rule can allow a customer-approved Teams meeting while denying a social or other unapproved app’s background microphone request, even if the app received permission at installation. This applies outside protected zones too. Behaviour analysis of supported app and permission events is being added to flag unusual attempts for review.

While the phone is still powered, a locked or dark screen does not exempt an app from the managed permission rule. A fully powered-down device cannot run software policy. Where the phone or watch supports it, an optional haptic alert can notify the user after a blocked request; the block itself can remain quiet.

Not by itself. Advertising can use browsing, location, account and purchase data. Niwaban addresses the controllable enterprise risk: which managed applications have microphone, camera, location or sharing access, and whether that access matches policy.

The customer chooses the rule. Niwaban can limit unapproved applications, change camera availability, apply supported microphone controls, raise an alert or present a restricted working experience.

That is the signature Android demonstration. Unapproved icons can be hidden or paused when the device enters a selected zone, then restored when policy allows. Production behaviour depends on the selected platform.

No. Niwaban is for authorised, enterprise-managed devices under a documented customer policy. It does not secretly record employees or create an unrestricted personal movement history.

Yes. Protection can remain quiet during ordinary use, but management stays lawful and visible through the organisation’s enrolment process and privacy notices.

Niwaban aims to respond to meaningful management and location events instead of continuous high-power tracking. We measure battery impact on the selected phone and watch models during the engagement.

James Tervit uses this term for a hardware-linked software-loading design. The research approach combines a chip-specific physical fingerprint, called a PUF, with cryptographic checks intended to bind approved software to the right device. Its anti-tamper performance requires implementation review and testing. An ordinary management app cannot add a PUF or change the manufacturer’s boot process; this part depends on suitable hardware and manufacturer support.

Company protection can return during setup when the device remains assigned through the manufacturer’s official enterprise-enrolment service. Correct company ownership and enrolment must exist before loss.

No responsible service can. Niwaban improves the response by combining supported lock and location actions, verified hardware details, proof of ownership and an auditable incident record.

Recovery depends on the selected manufacturer service, device model, network state and last available contact. We state those limits clearly for every supported model.

Yes. Enterprise customers can choose a managed service or customer-controlled private deployment. The Raspberry Pi edition serves home automation and demonstrations, not the main enterprise platform.

We stand up a dashboard, enrolled Android phone and Wear OS watch, selected protection zones and the supported app-policy and recovery actions agreed for the engagement.

We begin with paid technical consultancy to review your devices, management service and policies. We then scope and stand up the phone-and-watch demonstration and deployment around the integrations required. Timing and price are agreed after the compatibility review.

We scope a recurring per-device licence where appropriate. Paid consultancy, integration and support are priced for the customer’s requirements after the compatibility review.

Niwaban is scoped as a bolt-on integration. We review your device-management product, enrolled models, supported APIs and existing policies before promising compatibility. Your current platform remains responsible for its established controls.

Not necessarily. The integration review determines whether existing management connections are sufficient or an approved companion app is needed. Some controls require a particular enrolment mode. We scope any migration before deployment.

The aim is to extend your investment. Niwaban adds location context and coordinates supported actions with existing device management and security systems. We agree ownership of each rule to avoid conflicting controls.

Yes. A paid first deployment can focus on one location and a supported set of devices. Expansion follows agreed checks for policy behaviour, battery use, user experience and security reporting.

We can scope a monthly service proposal and explore hardware leasing through a suitable supplier. Hardware leasing, eligibility, term and availability require a separate written quote; no finance arrangement is currently guaranteed.

Yes, subject to compatibility checks. Separate pricing for software, integration, support and any optional hardware lets you see what your existing investment already covers.

We can quote per-device subscriptions, annual commitments and volume tiers. Device count, rollout dates and minimum commitments are agreed in the quote; a first deployment need not cover the full fleet.

Planning examples are $1 per watch per month at 50,000 watches, or $0.50 per enterprise device per month at 500,000 devices. A planning allowance of 20% of annual licence value covers maintenance. Integration, device-brand work, hardware and taxes are separate unless the quote includes them. These are discussion figures, not a binding price list.

Both can be discussed. A deployment proposal specifies deliverables, acceptance criteria and costs. Annual or multi-year terms, renewal increases, support levels and exit arrangements belong in the contract.

The commercial proposal will define active-device counting, volume adjustments and any committed minimum. We agree that basis before deployment so changes in the estate do not create billing surprises.

We scope managed cloud or customer-controlled hosting, including on premises or private cloud. The deployment review confirms operating requirements, security responsibilities, data location and support access for the selected option.

We scope adapters for supported security event feeds and reporting tools. We agree which events leave each system, their format, access controls and retention. Connectors are scoped and tested individually.

A private deployment can be designed around that requirement. The design review maps all data flows, including updates and any external services, before a claim about residency or isolation is made.

The integration can connect approved device events with gateway or network-adapter observations at the boundary of internal systems. Available visibility depends on your sensors and network design. It does not mean unrestricted access to encrypted traffic or private conversations.

NVIDIA Morpheus is an optional integration path for analysing approved security events on existing GPU infrastructure. Where deployed, BlueField and DOCA telemetry could contribute network observations. Niwaban compatibility, versions and throughput must be validated in the engagement; this is not an NVIDIA certification or partnership claim.

Intensive analysis belongs on the customer’s chosen backend. The watch and phone contribute supported events, aiming to limit their power use. Real measurements on the selected devices determine the battery claim.