OZPMS is the enterprise property-management tier of the Sovereign Edge platform, built for public housing, defence housing, private property management firms and large build-to-rent portfolios — the same sovereignty model as OZLOCK and OZLODGE, scaled to 100,000+ properties.
Unlike Tuya/TTLock, where a third-party vendor controls every lock globally, OZPMS puts control in the hands of the property manager — the party with the legitimate legal relationship to the tenant.
OZPMS is a “mini Tuya” owned by the property management company itself — not a third-party vendor controlling every lock globally.
Tenants hold their own key on their device; the PM cloud never sees plaintext credentials, only sealed envelopes.
Access is issued for the term of the lease and expires on its own — non-renewal, tribunal-ordered revocation and emergency access are all logged with a recorded order reference. There is no self-help lockout capability.
Every door access — who, when, which door — is recorded on infrastructure the PM company owns and controls.
Locks connect Wi-Fi direct to your cloud — no bridge hardware needed at every door, which matters at 10,000+ property scale.
No third-party cloud dependency and no offshore jurisdiction over your data — host on AWS/Azure Australian regions or fully on-premises.
Access that lapses by default is safer than access that persists until someone remembers to remove it. OZPMS has no "lockout" control — every change of access is tied to a lawful trigger, and the audit trail records why.
| Trigger | What Happens |
|---|---|
| Lease end reached | Credential expires on its own — access was granted for the lease term, nothing is seized |
| Lease not renewed | No new credential is issued; nothing is taken away |
| Tribunal order for possession | The order is the authority; OZPMS executes it and logs the order reference |
| Tenant hands back / self-revokes | Tenant's own action |
| Emergency access needed | Fire, police, medical and welfare-check access on statutory and duty-of-care grounds |
| Contractor access | Time-bound credential issued with proper notice for scheduled maintenance |
This section describes a product design position, not legal advice. Tenancy law is state-based in Australia — qualified legal review should be obtained before deployment with any housing authority.
| OZPMS | Tuya / TTLock | |
|---|---|---|
| Cloud owner | Property management company | Tuya (third-party) |
| Credentials stored on cloud | No — sealed envelopes only | Yes — plaintext |
| Revocation | Lock-side, lawfully triggered | Cloud deletion |
| Offline operation | Yes — BLE + PIN | No — cloud required |
| Data sovereignty | PM company owns its data | Third-party owns it |
| Open platform | Open protocol, standard hardware | Proprietary, vendor-locked |
Covers the lock software, credential lifecycle management and support for that door.
Your organisation's OZPMS cloud license, licensed in blocks of 100 doors.
Your organisation hosts its own relay — on-premises or in an Australian AWS/Azure region.
Independently buildable and verifiable — no closed, proprietary black box.
For deployments with a hard non-PRC-silicon requirement, a defence-tier hardware option using non-Chinese silicon is available on request — talk to us about your specific compliance requirements.
From a pilot of a few hundred properties to a state-wide rollout — let's discuss what OZPMS looks like at your scale.