What is AXSOR?

AXSOR is the platform where everything about your key management is managed and monitored. It is the solution of the future that will make you have peace of mind. You can setup rules for almost everything about your key management. Instead of checking all things manually it is possible to setup messages. This means that you will get promted when actions are needed and you do not need to check the system status manually. You get all answers in the system. You get key management on a completely new level. Everything is managed directly from your web browser. 

Play Video

Do you want to see more?

In AXSOR there are endless possibilities

Quick overview

Get a quick overview of the status of the system. See how many withdrawn Objects you have per day, week, or year. How often is the system used? It’s just a click away.

In AXSOR there are many things to check, see and do. It’s all up to you how much information you need or want to have.  Choose just to use the basic traceability of who holds an object at a certain time or use AXSOR to find addresses in maps, send messages for activities that have not been performed or make reservations of objects. The possibilities are almost endless.

If it turns out that you are in need of more functionality, it is possible to integrate AXSOR with other systems or we might develop new functionality to solve your requierments.

See withdrawals

All withdrawn objects are shown in a list view under Check Up, but you can also have a look directly into an EAGLE-Assembly. In this way it is possible, not only to see withdrawn objects, but also which objects that are reserved or not administrated yet. 

Reset Alarms

Different limitations and settings can be set to give you warnings and alarms that you want to pay attention to. When they appear, check what has happened and when action is taken, you can easily reset the alarm. All information remains in the system, but now you can focus on new events.

Handle Reciepts

Add a new receipt by choosing the receipient and then add the objects to the receipt. Simple. And of course, it is possible to have different return times for different objects in the same receipt.

Ease up the receipt handling

Instead of printing receipts, it’s possible to sign them directly in AXSOR on a signing pad. This saves time and the environment. It is also possible to identify the receipient by scanning a drivers licens or other types of ID by using a scanner

AXSOR Installation

AXSOR is installed on a server, usually operated by your IT department. If, by any circumstance, you don’t have the possibility to install AXSOR on your own server, PAAM can offer to host your installation. The servers we use are placed within EU.


Which web browsers are possible to use?

The two latest versions of the most common web browsers are possible to use for AXSOR:

  • Chrome
  • Firefox
  • Edge
  • Opera

What is installed on the server?

The following web services and databases are installed on the server or servers that are used:

Web services

AXSOR_GLOBAL for database control
AXSOR_DB with actual data for administration
AXSOR_LOG with administrative history data
AXSOR_Archives with history events from EAGLE


What specification is needed for AXSOR?

Data below is specified for a dedicated server. However, it is possible to split the application and database servers on different servers. It is also possible to use virtual servers. 

Processor2.3 Ghz2.3 Ghz
Internal memory4.0 GB4 GB
Operative systemMS Windows 2012-newUbuntu 18.04 or later
Web serverIIS 8.5-newNGINX 1.14-new
Database serverMS SQL 2014-newMySQL 8.0.27

.NET core hosting bundle 6.0.x

Storage applicationmin 10 GBmin 10 GB
Storage databasemin 1.0 GBmin 1.0 GB
Port openings80/443 (in), 22 (out to EAGLE), 1339 (out to proxy)80/443 (in), 22 (out to EAGLE), 1339 (out to proxy)

Back-up plan has to be set in MS SQL Server. The AXSOR databases are approx. 250 MB at start, but it grows continuously as the system is used. As a guideline, AXSOR makes the database grow approx. 100 MB per assembly per year.

Does AXSOR require any client installations for PC?

There is no need to install anything else besides a web browser.

Everything is managed in the web browser. This means that there is no need for updates on a single PC to manage the system.

If a signing pad should be used there is a need to install drivers for that specific device. However, all other readers that are possible to use with AXSOR do not need any drivers to be installed.

What happens if there is a power failure?

It is of course a need of UPS for the AXSOR server as it is on every server.

In old EAGLE there is a built-in battery back-up. New EAGLE is powered via an UPS with battery back-up.  The power failure is of course indicated with an alarm so it is possible to discover as soon as it happens.

What happens if the network is down?

Communication between AXSOR and EAGLE is no longer possible. AXSOR will indicate that the network is down.

Registrations and changes that are made in AXSOR are stored and will be sent out when the network is working again. All things that happens in EAGLE are stored locally until the network is up and running and the data is sent to AXSOR.

What is AXSOR developed in?

The Back-End is developed in:

  • .NET Core 3.1
  • C#

The Front-End is developed in:

  • Javascript (ES5)
  • Typescript
  • Angular

The development of AXSOR can be summarized by the following:

  • Responsive design developed in Angular supported by HTML5/CSS3/Sass and with framework Bootstrap 4.
  • The Browser client communicates Asynchronously via HTTP or HTTPS with a JSON REST-Api.
  • Events and HTTP Traffic is turned into observable streams using RxJS 6.4.1
  • Code written in TypeScript, which is then transpiled back to JavaScript (ES5) in waiting for web browsers to read ES6.

What is EAGLE developed in?

EAGLE is developed in the following languages:

  • C, C++, C#, Assembler, Lua and SQL
  • Operative system is Linux 2.6-4.19 using X-Windows with LXDE.

Guiding examples

Below are some guiding examples for the database server specifications recommended for AXSOR. These numbers are guidelines. To properly balance what specifications will best suit your system it is recommended to inspect the workload on the server over time and decide from there. The system will start to drop in performance if the specifications are substandard compared to the load put on the system – this can affect the speed of the system. 

Customers with 1-5 EAGLE assemblies or up to 3000 objects in AXSOR.

Processor2.3 Ghz (2 cores)2.3 Ghz (2 cores)
Internal memory4 GB4 GB
Database serverMS SQL 2014-newMySQL 8.0.27-new
Storage databasemin 25 GBmin 25 GB

Customers with 40 to 100 EAGLE assemblies or up to 40 000 objects in AXSOR

Processor2.3 Ghz (6 cores)2.3 Ghz (6 cores)
Internal memory16 GB16 GB
Database serverMS SQL 2014-newMySQL 8.0.27-new
Storage databasemin 270 GBmin 270 GB

Customers with over 150 EAGLE assemblies or  more than 100 000 objects in AXSOR.

Processor2.3 Ghz (8 cores)2.3 Ghz (8 cores)
Internal memory32 GB32 GB
Database serverMS SQL 2014-newMySQL 8.0.27-new
Storage databasemin 1012 GBmin 1012 GB