Deploy ManicTime Server with the tools you already use
Install the server on Windows, Linux, Docker or Azure, push the client as an MSI, and users can sign in with their Windows accounts. Most deployments are straightforward, and our support team helps if you get stuck.
Runs on the platform you already use
Install ManicTime Server on Windows or Linux, run it in Docker, or deploy it from Azure Marketplace. Start with SQLite, or use PostgreSQL or Microsoft SQL Server alongside the databases your team already runs.
The installation guide includes sizing for 100, 200 and 1,000 users. Activity volume, screenshots, retention and reporting all affect the resources you need, so use the pilot to confirm your production size.
Sign in with existing Windows accounts
When ManicTime Server runs on Windows, users sign in with Windows authentication. Accounts are created automatically on first connection, and teams can follow your Active Directory groups. Native ManicTime accounts are also available.
Need Entra ID, SAML, SCIM or another identity workflow? Tell us your requirements and we will confirm what the current release supports.
Roll out with the tools you already use
- Set up the server. Add HTTPS, your licence, teams and the central client settings you want every computer to use.
- Package the Windows client. The client installs from an MSI, so you can distribute it with Group Policy, Intune, Configuration Manager or a similar tool. The documented rollout pairs the MSI with a server-generated settings file, so users sign in with Windows authentication and have nothing to configure.
- Add macOS and Linux. Windows, macOS and Linux clients all connect to the same ManicTime Server.
- Check the result. Connected devices shows every reporting device, its version and when it last updated, so you can compare it with your device inventory.
- Expand in groups. Start with a pilot group, then roll out team by team with a short introduction for employees.
Read the Windows deployment guide and central settings guide.
Back up with the tools you already have
Only the Core database holds source data; the Reports database rebuilds from it. Back up Core with your usual SQL Server or PostgreSQL tools, or copy the SQLite files with the server stopped, together with the server configuration and any screenshot storage. Test a restore once before going to production.
Upgrade on your schedule
You decide when to upgrade. Read the release notes, back up the server and try the new version before rolling it out widely. After upgrading, check that sign-in, synchronization and your key reports work.
To roll back, restore the pre-upgrade backup: installing the previous version alone does not undo database changes.
Try it in your own environment
The 30-day trial starts automatically after installation, with no licence key or sales call needed. Prefer a walkthrough first? Book a demo.