Bring one device-operations question.
Share the smallest useful context. ZENQIX will review fit, authorization and pilot scope before access.
Start small. Learn from the real constraint.
- 01Share the device and platform shape
Scope and authorization stay visible at this step.
- 02Review a bounded pilot question
Scope and authorization stay visible at this step.
- 03Run a human-led preview
Scope and authorization stay visible at this step.
- 04Receive evidence and next decisions
The outcome is a reviewable record, not an unsupported promise.
Bring enough context to learn something real.
Use the smallest safe sample. Public forms do not ask for credentials, secrets or production records.
- A named operator and an authorization owner
- A small Windows, Linux or macOS device sample
- The pilot question and desired evidence outcome
- A review window for agent installation and removal
- No passwords, secrets or customer records in the public request form
Answers without the larger claim.
What platforms are supported now?
The accepted pilot baseline covers Windows amd64, Linux amd64/arm64 and macOS amd64/arm64. The exact pilot matrix is confirmed before access.
Is Endpoint an MDM?
No. Endpoint is presented as a focused device-operations preview. Broader MDM, mobile management and EDR claims are not made.
Can it patch devices or deploy software?
Some guarded control-plane foundations exist, but patch deployment and broader execution remain agent- and physical-QA-dependent. They are not represented as general availability.
What data does the agent collect?
The baseline covers device identity, reported inventory, availability and operational evidence. It should not routinely collect passwords, tokens, keystrokes, clipboard history or document contents.
How is access controlled?
Authenticated control-plane sessions, server-side role permissions, device bearer credentials and audit records form the access boundary.