AverDesk
AverDesk — Your IT.
On one map.
Your IT equipment, the links between systems and requests for help, kept together in one app.
Visual concept · not a product screenshot
Know what a restart
will affect
Link each server and service to the person in charge of it. Before you restart something, you see which services it will affect.
What a change will affect
Requests with reply deadlines
Data import and sync
How it works
A map of your IT that people actually use
AverDesk keeps a CMDB, a register of your IT equipment and how it is connected, right next to everyday support. Equipment, links between systems and failure reports sit side by side. So an engineer can understand a problem before touching anything.
One linked register
Servers, laptops, services, licenses, IP addresses, locations and the people in charge are stored as linked records. Engineers use these records every day, so there is no separate spreadsheet to keep up to date. Every field remembers who changed it and when.
See the chain before a change
For each system, note the servers, ports, outside services and backup sites it needs to run. These links form one map, from a single machine up to the product people use. When something fails or needs a restart, follow the chain to see which business services are at risk.
Requests tied to equipment
Each help request or failure report is linked to the equipment it is about. The conversation, the affected systems and two SLA timers (deadlines for the first reply and for the fix) stay in one ticket. Planned maintenance shows up next to unexpected outages.
Bring in the data you have
Upload CSV or JSON files, or connect your scripts through the API, the documented way for programs to talk to AverDesk (OpenAPI 3.1). It works with n8n, Python, PowerShell or bash. A small agent program for Windows or Linux only makes outgoing connections. It reads people and groups from your staff directory (AD or LDAP) without changing anything there and finds your infrastructure on its own.
Separate organizations and access
Each organization has its own database, and the AverDesk team has no access to it. Teams set which equipment a person sees, and roles set what they can do. One subscription can hold several organizations, so service companies keep each client’s data apart.
Employee portal
Employees ask for help through a list of services written in plain words. They see what stage their request is at and who is working on it, and questions are answered right inside the request. The portal works on a phone, in English, Ukrainian or Russian.
Planned work and service status
Record the announced maintenance window, the time set aside for planned work, next to when the work really happened. The dependency map shows what it touched. Alerts arrive in the app, by email or in Telegram. The status page shows the last 90 days from recorded checks, and days without checks stay grey instead of turning green.
Where it helps
Before a server restart
See which services rely on the server and who is in charge of them, then decide how risky the work is.
During an outage
Follow the map from the broken part to the affected systems and keep the whole incident in one place.
For several clients
Keep each client’s data separate while your team supports all of them from one workspace.
Plans and access
One IT person can use AverDesk for free, with no time limit and no card. There is also a one-time trial of the Standard plan. Paid plans count only operators, the people who handle requests. Employees who just use the portal are never billed. To install AverDesk on your own servers, there is the OnPrem plan with individual terms and yearly payment.
Key capabilities
- Automatic discovery
An agent finds servers, programs and the links between them, so you don’t have to type the register in by hand.
- Cloud connections
Resources you rent from cloud providers appear in the same register as your own servers.
- AI that spots repeat problems
AI reads through past failures and points out the problems that keep coming back.
- AI in the employee portal
An employee describes a problem in their own words and gets an answer or a correctly filled-in request.
- Virtual assistant
An assistant answers common employee requests by itself and passes the rest to the IT team.
- Mobile app
Handle requests and check how your systems are doing from your phone.
Who it’s for
For the people who keep IT running, from a single administrator to a company serving many clients. Pick the situation closest to yours.
Teams and service work
Company IT teamsStop juggling spreadsheets and email
Keep equipment records, owners, requests and the employee service list in one workspace. Engineers handle daily support from the same records.
Full scenarioMSPs and IT service companiesSupport many clients without mixing data
If you run IT for other businesses (an MSP), give each client a separate organization with its own access rules. Your team works across all of them and keeps the history of failures and planned work.
Full scenarioNOC and night-shift engineersUnderstand an outage and brief the next shift
NOC engineers watch systems around the clock. Follow the links from a broken part to the services people use. Compare the outage with planned work and leave notes for the next shift.
Full scenarioSupport leads and employeesGive people a clear way to ask for help
With the employee portal and service list, every request shows its stage and the person handling it. Employees can ask for help in English, Ukrainian or Russian.
Full scenarioEquipment and who owns it
Teams with equipment in many placesConnect offices, server racks and the cloud
Link each location to the systems it runs. Together, the map, the register and the links show which equipment serves which service.
Full scenarioIT leads and equipment ownersPrepare a review of equipment and renewals
Find items that aren’t linked to anything, and keep license dates and owners in a shared register. Your records stay useful all year, not just during the yearly check.
Full scenarioStaff directory and integration adminsKeep people, groups and locations up to date
Connect AD or LDAP, the directory of staff accounts, through the agent that only connects outward. Send other company data, such as offices and cost centers, with API scripts.
Full scenarioSolo administratorsDon’t keep everything in one person’s head
Build a register of equipment and a map of links for a small organization. If the admin is on leave or hands the job over, everything written down stays at hand.
Full scenarioQuestions about AverDesk
Which languages does AverDesk support?
The interface is in English, Ukrainian and Russian. The employee portal uses the same three languages, has light and dark themes and works on a phone.
Can we run AverDesk on our own servers?
Yes. Besides the cloud version, there is the OnPrem plan: AverDesk is installed on your own servers, with your own branding if you want it. Terms are agreed individually and paid yearly. AverDesk runs in containers, a standard way to package and run server software.
How do we get data in and out?
Upload CSV or JSON files, sync people and groups from AD or LDAP through the agent, or send records through the API. Your scripts can read everything back the same way, one organization at a time. If you need a full export in a specific format, AverDesk support can prepare it.
Who is AverDesk for?
For company IT teams, firms that run IT for several clients, night-duty engineers and admins who work alone. A single admin can start on the free plan and move to a paid one when the team grows.
