Product Features Solutions Pricing Learn Resources
Pricing

One facility. Unlimited operators.
One price.

No per-seat fees. A single site licence covers every operator, every screen, and every area in your facility.

Starter
$299/month
1 facility · up to 25 employees · 1 admin account · billed monthly
1 facility, 1 admin account
Up to 25 employees
Live takt timer per operator
Operations Table + KPI dashboard
Floor Map view
Weekly Schedule view
Manual / Excel standard hours
Power BI CSV export
Auto-update via Updater.exe
Email support
Pilot deployments · single-line shops
Buy Starter →
Enterprise
Custom
Unlimited facilities & employees
Unlimited facilities & admins
Everything in Professional
All ERPs + custom adapters
Custom onboarding & floor mapping
Dedicated success manager
SLA & enterprise support
Source code escrow available
Multi-site manufacturers · group rollouts

Payments & licence key delivery by Whop. Keys delivered instantly. Cancel anytime.

Frequently Asked Questions

No. Standard hours can be entered manually in the Data Entry tab or imported from a spreadsheet on any plan. ERP integrations (M3, SAP, Oracle, Epicor, Dynamics 365) are available on Professional and Enterprise plans but are entirely optional.
One always-on Windows 10/11 PC to run TaktClock_Server.exe, with TCP port 5000 open in the Windows Firewall. Client PCs just need to be on the same local network. No cloud services, no VPN, no new hardware.
Your key is entered once on TaktClock_Server.exe → Settings → Licence. The server validates against api.taktclock.io and caches the result locally. All client apps receive their licence from the server — no per-seat fees. The 24-hour cache allows offline operation if the internet is temporarily unavailable.
Most sites go live in under one business day. Install the server, enter your licence key, configure areas and employees, deploy TaktClock.exe to operator PCs. Many teams finish initial setup in 2–4 hours.
TaktClock is self-hosted on your premises and transmits no production data externally. It does not introduce new CUI transmission risks when properly deployed. Internet is used only for licence validation and update checks — not for production data.