One sentence, then the detail
AverDesk is a place to write down what your company runs, to see what depends on what, and to handle the problems, requests and planned work that happen to those things. That is the whole product. Everything else on this site explains one of those three parts and how they fit together.
The name is a reminder of what we wanted it to do. “Aver” stands for awareness, view, verify and version. “Desk” is the workspace where the work happens. The principle we keep coming back to is See, then Understand, then Act. Most IT tools are good at one of the three. We wanted all three in the same window.
Part one: a list that knows how things are connected
Start with the inventory. Think of it as the company’s memory of everything IT owns and runs (the traditional name is CMDB, a configuration management database). It holds the things the business uses, such as payroll or email; the services behind them; the servers they run on; the hardware, network addresses, software, licences, rooms and buildings, accounts, monitoring checks and backup rules around them. When the built-in fields do not fit, you add your own.
What makes it more than a list is that every record is linked to others. A server belongs to a service, the service to a product the business recognises. Details flow down that chain, and when two sources disagree, a person decides rather than the system guessing. Every field remembers who changed it and when. Lists with tens of thousands of rows scroll as fast as a list of ten, with filters, saved views and three row heights for people who like their tables tight.
Part two: a map of what depends on what
Connections follow rules. Each organization decides which kinds of links exist and how many an object may have. Loops are refused, and the screen shows exactly which chain would have closed the loop. The dependency view lets you arrange the hierarchy by hand and then follow the impact: this server carries these services, which make up these products. So when the server goes down, you know who to warn before the phone rings.
The estate map draws the same data in 3D. Floors are your locations and the products in them. Towers are people, assets and requirements. Cloud regions resolve to a country and city on a world map. A red ring means an outage, an orange one means planned maintenance. The map also looks for what is missing: things connected to nothing, things that never reach a product, and anything forgotten since yesterday’s check.
Part three: a desk for the daily work
The service desk is where problems and requests land. Each one has a conversation, a status path your team defines (a lifecycle set in a rules table), and two timers: one for the first answer, one for the fix (response and resolution SLA). New items wait in a shared queue with live counters, there is a board for the day, and managers get statistics. For IT people these are the familiar incidents and requests (INC and REQ).
Because the desk and the inventory are one product, a ticket points at a real service. The person handling it sees that service’s servers, its dependencies and last night’s changes without leaving the ticket.
Employees get their own portal with a catalog. A person picks what they need, say a new laptop, and then watches where the request is and who is working on it. All the correspondence stays inside the request. People who only order things and follow their requests are never billed. You pay for the operators who do the work.
Next to that sit maintenance windows, announced and actual, with the affected services listed automatically, and a status view with a 90-day availability bar. A day without checks shows as a gap, not as green. Notifications arrive in the app, by email or in Telegram, and the same alert repeated is muted after the first time.
Who it is for
The administrator who keeps the whole company in his head and would like to take a holiday. The Free plan gives one organization, one operator and a demo organization to experiment in, with no card and a one-time 45-day trial of the Standard plan.
The internal IT team of three to twenty people with a server list and a ticketing tool that do not talk to each other. Standard or Pro gives several operators and, on Pro, several organizations for a holding company or separate business units.
The company that looks after other companies’ IT (an MSP, a managed service provider). Each client is a separate organization with its own database. One subscription holds many of them. An operator who works across all of them is counted once. Teams decide which assets a person can reach, roles decide what they can do, and anything they may not see is simply absent, with a plain reason when something is refused.
The manager who is not in IT and wants to know, in one screen, whether the thing the sales team depends on is up, who owns it and when it was last touched. The estate map and the status view were drawn for that reader as much as for engineers.
How it is built and run
Each organization has its own database. AverDesk staff have no access inside a customer organization. Passwords and keys stay on the server. The system watches sessions for signs of theft. Backups are encrypted and sent to your file storage on a schedule (FTPS), with restore. The whole thing ships as containers, which is also how the OnPrem option runs inside your own infrastructure, under your own brand if you like. More on the security page and the pricing page.
The interface works in English, Ukrainian and Russian, in light and dark themes, on a phone, with Ctrl+K search everywhere, good contrast (WCAG AA) and reduced motion for those who want it. The people building it have spent over twenty-five years in IT, more than ten of them inside companies with over a hundred thousand employees. We built the tool we kept wishing for.
Where to start
Read the use cases if you want to see your own situation described. Or skip that and start with the Free plan: create an organization, record one service, and see whether the model matches the way you already think about your company.
Read next
Start with one service
The fastest way to fail at an inventory is to import everything on day one. Here is how to start with a single service and grow from something that already works.
· 5 min read
Nothing comes in: how AverDesk gets your data
To see your servers, an inventory tool usually asks you to open a door into the network. AverDesk does not. Here is how the data gets out without anything getting in.
· 5 min read