One Platform to
Manage Your Entire
IT Business

• Escalation that climbs by itself

  A ticket past its resolution time moves up your escalation levels the longer it waits. Each level is told once — the assignee, their manager, the dispatchers and the administrators you choose.

  You set the levels; it runs once you switch it on.

  Included in every plan · How it works

• Tickets raised from where people already are

  Email, WhatsApp and the ticket API create tickets with the same SLA clock, contract link and ticket number as the console, and can assign them automatically.

  Automatic assignment is a switch per company.

  Included in every plan

• Renewals that nudge before cover lapses

  AMC contracts raise a reminder ahead of their end date and once after it, each at most once per term. Warranty and licence dates raise alerts as they approach.

  Reminders reach the in-app inbox and the channels you connect.

  Included in every plan · How it works

• Preventive maintenance that schedules itself

  Define maintenance schedules against equipment, and preventive-maintenance tickets are raised automatically when they fall due, so routine servicing is not forgotten.

  You define the schedule once.

  Included in every plan · How it works

• Safe fixes that run on their own

  When an alert fires, a rule you wrote can run a pre-approved, safe fix on that PC — inside your maintenance window, with a rate limit and a cooldown — or only log what it would have done. A follow-up ticket is one switch away.

  Off until you turn it on, with a dry-run mode first.

  Included in Free, Enterprise

• Reports that arrive on schedule

  Pick a report, the recipients and the cadence. Every run re-checks what its creator may see, so nobody receives more than they are allowed to.

  Needs mail connected and export rights.

  Included in Growth, Enterprise · How it works

• Joiners and leavers in one step

  Offboarding deactivates the person, signs them out everywhere and recovers their devices in one action. A new joiner gets an onboarding checklist. Whatever could not complete is reported, never hidden.

  A deliberate click by an administrator.

• A second pair of eyes on risky changes

  A change that grants high-risk access can wait for another administrator’s approval, then replay exactly as requested. You choose which changes count as sensitive.

  A four-eyes gate you switch on.

  How it works

• Your other systems hear about it

  Signed webhooks tell other systems when anything in your company changes, and failed deliveries are retried. Alerts can also go to Microsoft Teams, Slack and Telegram.

  You choose the events and where they go.

See solutions by industry

All systems operationalChecked 06:06 UTC · live status and 30-day record

• Consent before captureAn agent’s content is not accepted until the employee has acknowledged the current notice. Screenshots, live screen and recordings ship switched off.
• One company, one isolated tenantEvery company has its own users, devices and settings; access across companies is refused at the query layer.
• Least privilege, enforced where the data isRole-based access with data scopes down to team and self; sensitive changes can need a second administrator’s approval.
• Two-step sign-in and session policyAuthenticator-app (TOTP) sign-in with recovery codes, lockout after repeated failures, idle sign-out and a sign-in audit.
• Everything administrative is auditedSign-ins, permission changes, exports, payments and support access are written to a log the company can read and export.
• Egress you controlExports are off until switched on, encrypted and watermarked; capture retention is a window the company sets.
• Secrets and paymentsOperator credentials are stored encrypted (AES-256-GCM). A payment counts only once the gateway or the bank confirms it.
• Your data stays yoursSelf-hostable on your own infrastructure. If you stop paying, the console stays readable and your data stays available to you.

Book a security review Read the security page Data security policy · Privacy policy