TL;DR
ZKBio Time Cloud: best for teams that want zero server upkeep, mobile self-service, and simple payroll-ready exports from anywhere.
ZKBio Time 9.0: a self-hosted, web-based option you run on your own machine/network. Solid for sites that must keep everything on-prem.
You can trial both. For Cloud, start small and scale; for 9.0, install on a dedicated PC/VM and test with one device first.
What each option is
ZKBio Time Cloud — hosted on Amazon Web Services (AWS), browser & mobile logins, built for SMB/SME and multi-site use.
ZKBio Time 9.0 — web-based time & attendance you host yourself; manage timetables, shifts, schedules and reports from your LAN/VPN.
Quick comparison: ZKBio Time Cloud vs ZKBio Time 9.0
| Area | ZKBio Time Cloud | ZKBio Time 9.0 |
|---|---|---|
| Hosting | Vendor-hosted (AWS). Browser/mobile access from anywhere. | Self-hosted on your server/VM. Access via LAN/VPN. |
| Core features | Timetables, shifts, exceptions, reports; remote admin and staff self-service where enabled. | Timetables, shifts, exceptions, reports; administered inside your network. |
| Security posture | TLS in transit; AWS availability; role-based permissions. | Vendor lists ISO/IEC 27001/27701 alignment; server hardening/backups are your responsibility. |
| Mobile options | ZKBio Time app + browser self-service (per policy). | Same app connecting to your on-prem endpoint (VPN/port rules). |
| Integrations | Payroll-ready exports (CSV/XLSX); API availability may vary by plan/region. | Exports plus on-prem ZKBio Time API for ERP/HR sync. |
| Device support | Works with current ZKTeco push devices (e.g., SpeedPalm/SpeedFace families). | Same families; you control the device→server path internally. |
| Best for | Multi-site teams, remote admins, minimal IT overhead. | On-premise environments with strict data policies. |
Who should pick Cloud
Choose Cloud if you want:
No server maintenance and easy scale to more devices/sites.
Anywhere access for managers (browser/mobile), with staff self-service options.
Simple payroll workflow using CSV/XLSX exports you can map once and reuse. (Keeps you in “assist payroll” territory, not deep integration.)
Who should pick 9.0
Pick 9.0 if you need:
On-prem control (keep data inside your network/VPN).
API on your terms for ERP/HR synchronisation without exposing a cloud endpoint.
A stable, web-based UI that runs from a server you manage.
Features you’ll care about
Timetables, shifts, and exceptions
Both platforms handle standard time, flexible shifts, and exception reporting (late/early/missed). Cloud adds remote convenience; 9.0 keeps the same logic on-prem.
Mobile self-service
The ZKBio Time mobile app lets employees clock (where enabled by policy), view balances, and submit requests. In Cloud, this is native; in 9.0, you expose the on-prem server for the app.
Device compatibility
Modern terminals (e.g., SpeedPalm V5L) list ZKBio Time among supported back-ends; placement and lighting still matter, but WDR cameras on current models help with tricky entries.
Security and compliance
Vendor materials cite ISO/IEC 27001 (ISMS) and 27701 (privacy) for ZKBio Time; Cloud adds AWS infrastructure and TLS transport. On-prem buyers must still harden Windows, patch regularly, and back up databases.
Integrations & exports
Both platforms output CSV/XLSX for payroll import. If you need programmatic sync, 9.0’s API gives you low-level control from your environment.
Features you’ll care about
Timetables, shifts, and exceptions
Both platforms handle standard time, flexible shifts, and exception reporting (late/early/missed). Cloud adds remote convenience; 9.0 keeps the same logic on-prem.
Mobile self-service
The ZKBio Time mobile app lets employees clock (where enabled by policy), view balances, and submit requests. In Cloud, this is native; in 9.0, you expose the on-prem server for the app.
Device compatibility
Modern terminals (e.g., SpeedPalm V5L) list ZKBio Time among supported back-ends; placement and lighting still matter, but WDR cameras on current models help with tricky entries.
Security and compliance
Vendor materials cite ISO/IEC 27001 (ISMS) and 27701 (privacy) for ZKBio Time; Cloud adds AWS infrastructure and TLS transport. On-prem buyers must still harden Windows, patch regularly, and back up databases.
Integrations & exports
Both platforms output CSV/XLSX for payroll import. If you need programmatic sync, 9.0’s API gives you low-level control from your environment.
Real-world signals
- ZKTeco’s public Cloud page highlights AWS hosting and multi-device access.
- ZKBio Time materials show the web-based interface and the common T&A toolset (timetables, schedules, reports) plus ISO claims.
- Example case (vendor site): enterprise T&A deployments (earlier versions) underline large-scale shift/schedule use with detailed reporting.
Recommendation
Start with ZKBio Time Cloud unless you have a policy or legal requirement to self-host. You’ll cut server overhead, get faster roll-outs across sites, and keep a clean payroll-export workflow. If compliance or IT policy demands on-prem, ZKBio Time 9.0 remains a strong, web-based option.
Implementation notes
Keep a single IN/OUT flow per doorway to reduce queues and improve exception accuracy.
Map your export template once and save it; this keeps the “assist payroll” hand-off consistent every pay run.
For biometrics, capture face + palm (or other second factor) for frequent users; retain card/PIN as a contingency.
FAQs
Yes—create groups with validity windows and separate reporting. (Cloud or 9.0)
Yes. Cloud scales without extra servers; 9.0 scales with your VM/DB sizing.
For self-hosted 9.0, there’s a published ZKBio Time API for ERP/HR synchronisation.
Learn more
ZKBio Time Cloud product page (NZTeco): https://www.nzteco.co.nz/product/zkbio-time-cloud-attendance-software/
ZKBio Time 9.0 product page (NZTeco): https://www.nzteco.co.nz/product/zkbio-time-9-0-time-attendance-software/
