Built on KEZEL. Run inside your boundary.
secQR is a DBTEZ product built on KEZEL®, the in-boundary intelligence platform. That foundation is why validation can run inside your perimeter, and why your product data never has to leave it.
Move the work, not the data.
Most platforms move your data to their intelligence. KEZEL inverts that: the intelligence travels to the data and executes where the data lives. Four beats, always in this order.
- 1
Policies define boundaries
You declare where data may live, who may reach it, and what may run against it. The boundary is a policy, not a diagram.
- 2
Workflows flow to the data
Work arrives as encrypted instructions. The platform moves the workload to where your data already is.
- 3
Intelligence runs inside
Validation, rules and analysis execute within your perimeter, on your infrastructure or tenancy.
- 4
Results remain inside
Outputs stay in the boundary and are released only under the access your policy grants.
Verified, contained, evidenced.
KEZEL’s patent-pending Zero-Trust Orchestration framework governs how work enters and leaves a boundary. Every request is verified. Every execution is contained. Every decision leaves evidence.
Validation inside your boundary
The secQR runtime deploys where you choose: your data centre, your cloud tenancy, or an isolated tenancy we manage. Scans validate there, next to the record.
Instructions in, data never out
Policy and configuration updates flow in as encrypted instructions. Product records, scan logs and analytics stay where you put them.
Evidence by default
Every validation decision lands in a tamper-evident audit trail, ready for enforcement teams, auditors and regulators.
For a product-authentication platform, this is the difference that matters in regulated sectors: pharma batch records, PSU supply data and export documentation carry legal weight, and secQR validates against them without asking any of it to leave your custody.