Licensing policy

Companies’ need for flexibility in the way they adopt products and services is constantly increasing, especially when a long-term contract is required. This need is driving change in software contract practice, away from the adoption/maintenance model and towards the new model called SaaS, or Software-as-a-Service. With SaaS, software is treated as a service and paid for according to the customer’s usage.

The growth of this model is strengthened by the tendency to offer solutions in the cloud, where SaaS is part of the same type of solution.

For companies, this new model presents various advantages:

  • The number and type of software licenses can be better adjusted to the company’s needs.
  • The SaaS model allows easy adaptation as a business fluctuates and evolves.
  • Purchased licenses that are no longer used become a problem of the past.
  • Software runs on an operating expenses (OPEX) model rather than a capital expenditure (CAPEX) model, so it’s easier to schedule around budgetary periods.

Many companies find that their ERP presents sky-high costs year after year. Instead of an instrument to increase the company’s productivity and efficiency, ERP becomes a passive product, limited to reporting events and hindered by its complexity and the amount of resources it consumes.

In many companies, the most frequent scenario is that:

  • The high cost of software maintenance takes resources from other company projects.
  • The integration of innovative new applications requires specialized consulting companies to be hired.
  • Often, only part of the installed software is used.
  • The company avoids software updates out of fear of disrupting the system. On the other hand, the migration to a new product would be quite costly and would require a large dedication of resources.

The reality is that, in spite of the elevated price, most ERP implementations tend to be homogeneous and aren’t able to provide differential value to make each company more competitive. As a result, organizations face the quandary of how to lower costs and find new ways of doing business. In other words, how can we make sure ERP investment creates added value for a company?

At Deister we believe every company is unique in all aspects, and that’s why we conceived our ERP software as a platform that can adjust to the needs of our clients.

This platform is built on modern web-based architecture and a Software-as-a-Service (SaaS) licensing system where the client doesn’t need to worry about infrastructure, maintenance or improvements, and in exchange, they have a greater degree of control over their investment.

In this way, we’ve turned software investment into a scalable system that allows you to adjust costs according to your actual needs and increase profitability.


1. On Demand

This model offers licensing of Deister applications which can be accessed via the Internet. License cost includes application usage, infrastructure and additional software.

2. On Premises

This model allows the licensee to install the products on their own servers. In this case, usage rights are applicable to users as well as systems.

  • The SaaS model allows companies to customize their number of licenses based on the demands of their business. Each year a revision of the licenses used by the company is performed and adjustments are made according to level of demand.
  • The flexibility and ease of configuration means that users learn much more quickly and the client can adapt our ERP solution themselves.
  • Only one version of the software stays up-to-date. Development and innovation are focused on maintaining that version. In the licensing sale model, the costs of development are split between all versions supported on each platform.

From January 2014 onwards, all new versions of the products offered by  are licensed according to a new alternative subscription-based model.

The service includes the use of the software, essential maintenance and the downloading of updates during the subscription period.

If the subscription is not renewed, usage rights will terminate at the end of the corresponding period, and the license and usage rights of the licensed products will expire.


    The onpremises model enables the owner of the license to install the products on their own servers. In this case usage rights shall apply to both users (who use the products) and systems (where programs are installed). The license does not include the costs of infrastructure, the database backend or additional software.


    The ondemand model provides licensing of applications which  provides access to via the Internet. The license costs include use of the applications, infrastructure and additional software. In this case, the licenses are applied per user, as licenses per system are included as part of the OnDemand model.


The licensing of these applications consists of a Licensing by a Sole Legal Entity plus the licensing modalities that are described below that are applicable according to the operation of the Legal Entity.


The license to use the software for these applications is always granted individually to a single legal entity. The licensing does not allow the transfer of the right of use. Therefore, the affiliated companies or entities must acquire their own licenses independently. For the purposes of this definition, “affiliated” shall mean the union of the main legal entity that holds the license and all other entities that control, are controlled by, or are under common control with that entity.


Users of applications are defined as those that use any end applications of the “BUSINESS SOLUTIONS” product family, such as Axional ERP or Axional WMS, as well as products belonging to the “MOBILE SOLUTIONS“ family.

The licensing model for these applications is by “nominal” user. Depending on their usage, it’s possible to distinguish three different types of users:


An authorized user user is a physical person who is granted access to the program. The program can be installed on any number of computers or servers, and each authorized user may have simultaneous access to many instances of the program. The license holder must grant individual rights to each user with access to the program directly or indirectly (e.g. via a multiplex program, device, or application server). The usage rights of each authorized user are personal and non-transferable. They can only be transferred to another person, and the transfer must be permanent.

Client devices which require the execution of the program, receive the results of executing program commands, processes and applications, or are managed by the program are also considered Program Users. These devices need to be granted usage and licensing rights as a physical user would.

The licensee must have, at minimum, as many licenses for authorized users as the number of client databases. For example, if the licensee can access 25 different databases, they must license at least 25 authorized users.


A flexible user is a natural person granted access to the program for usage during a limited period of his working hours. This is an special type of licensing only available for some modules and processes in Deister’s product portfolio. It is intended for environments in which many users only use the program sporadically, at most forty hours per month.


Runtime users, like authorized users, are natural persons granted access to the developments created with Axional Studio’s tools. All licensed users of applications also possess a runtime license,  which allows them to make use of developments built by the client. Additional runtime user licensing is only required for those natural users who do not have application usage license and who use “in-house” developments of applications or processes made with Axional Studio’s development tools.


In the “OnPremises” licensing model, in which the program is installed on the licensee’s equipment and facilities, the licensee must also register the equipment and servers. Licensing of the servers depends on the number of processing cores  of the equipment on which the program is installed. This type of license is called Licensing by Processor Value Unit PVU.

Licenses for authorized users and flexible users also grant the right to included PVU licenses. The licensee may acquire additional PVU licenses to reinforce the processing capacity of his equipment, with a maximum of either 200 PVUs or 25% more PVUs than would correspond to the number of licensed authorized users. For example, if the licensee licenses 200 authorized users of a product, which would give him server usage rights up to 400 PVUs, then the licensee could acquire up to 200 additional PVUs.

If the processing capacity required for the servers would make the use of additional PVUs over the “25% more” limit necessary, then the licensee will need more authorized user licenses to cover licensed servers’ requirements. Referring back to the previous example, if the licensee needed to license servers for 1000 PVUs, then he would need to license a total of 400 authorized users and 200 additional PVUs, despite the fact that the number of natural users on the system will be fewer than the 400 licensed authorized users.

In view of the n-tier architecture of the program, each one of the servers on which it is installed functions as a redundant copy of the others. Therefore, special cases of unlicensed backup servers are not allowed. The licensee should license a sufficient number of servers for normal operation and to support the burden if one server fails.

PVU, or Processor Value Unit, is a unit of measurement by which each program in the OnPremise model must be licensed. The number of usage rights per PVU required is based on processor technology (defined in the PVU Table) and the number of processors available. For the purposes of PVU-based licensing, ‘processor’ is defined as each processing core within a chip. For example, a dual-core chip has two processors. The licensee must acquire enough PVU usage rights to cover all activated cores within the hardware available to or managed by the program.

The licensing rules associated with product use on virtual servers also use the Processor Value Unit (PVU) method, treating the virtual cores assigned to a virtual server as if they were physical server cores. Therefore, to license virtual servers, each guest server must be licensed according to its number of assigned cores, regardless of the actual number of cores available to the physical host server. The PVU value of each virtual server core is equal to the value of the type of processor installed on the host machine. In exceptional cases when justified,  can explicitly grant a particular client a type of peripheral licensing for exclusive use, in which only the host server cores will be licensed regardless of the number of virtual guest machines.


Axional Suite provides a platform for users who want to develop custom applications. For that purpose, the users must have an Axional runtime license.


Certain products in the portfolio are delivered along with the source code that comprises them. This source code is protected by a reference license and is considered confidential information. It is delivered exclusively to the licensee as a reference for examination and review, but its modification, distribution or disclosure are not permitted by any means.

The ability to review the source code and make changes or adjustments to the programs does not grant the licensee rights to technology developed at the time of licensing, or any rights to possible later developments. Improvements, alterations and developments made using the existing source code do not grant any intellectual property rights to the licensee, nor do they permit the formulation of patents, redistribution or resale, even if rights are restricted to existing developments.




Available    Not Available      Required

AXIONAL ERP Nominal users 200 € 250 €
AXIONAL ERP FLEXIBLE Nominal users 50 € 60 €
AXIONAL ERP LITE Nominal users 60 € 80€
AXIONAL ANALYTICS Nominal users 90 € 150 €
AXIONAL ENTERPRISE REPORTING Nominal users 120 € 150 €
AXIONAL MOBILE SFA,PUD, License by Device 49 € 59 €
AXIONAL MOBILE POS License by Device 49 € 59 €
AXIONAL MOBILE WMS/RF License by Device 49 € 59 €
AXIONAL MIDDLEWARE *Nominal users 250 € 300 €
AXIONAL STUDIO RUNTIME Nominal users 60 € 75 €
AXIONAL STUDIO DEVELOP. Nominal users* 250 € 15 € 300 €
INTEGRATION BUS Remote Connections 350 € 10 € 400 €

*Minimum 5 users
*IVA not included


 includes support for its programs in the various subscription-based licensing models. While subscription-based licensing is in effect for licensed programs:

  • deister will provide and authorize the use of the latest commercially-available version of the licensed Product.
  • deister will provide routine assistance: respond to simple questions about installation or use of the product and code-related issues (“Support”). This support for a specific version of the program will be available only for as long as [Deister] or a third party, if applicable, keeps supporting that version (See the product life cycle policy). When the supported version’s life cycle ends, an upgrade to a new version of the program is required in order to continue receiving support.
  • deister offers telephone assistance as well as, if available, remote connection to the staff or advanced users during the support center’s hours of operation.
  • deister may ask the licensee for access to their computer systems via remote connection in order to isolate the cause of the problem. The licensee remains responsible for adequately protecting their systems and all data contained therein when  accesses remotely with their consent. This clause is not applicable to the onDemand licensing model, as in that case the equipment and infrastructure are supplied by .

The support and maintenance service does NOT not include assistance with:

  • The design and development of applications and new product functionalities.
  • The use of the program outside of the agreed-upon environment.
  • Errors caused by programs for which [Deister] is not directly responsible according to this agreement.

To help clarify the meaning of terms used in this document, please read the “Licensing Glossary

Products reach the end of their life cycle for various reasons, such as:

  • Market demand.
  • Technological innovation.
  • Changes in direction in product development, or simply because products mature with time and are replaced with more high-functioning technology.

This evolution is just one more part of the complete product life cycle, and  understands that when a product’s life cycle comes to an end, companies should analyze and examine the impact that this milestone may have on their organization. With this in mind, we’ve established the  end-of-life (EOL) policy to help clients better manage their transition to new products or versions, as well as understanding the role that  can play to help them migrate to alternative products, versions or technology.

Deister’s support life cycle guidelines provide predictable and consistent instructions about the availability of support during a product’s launch and life cycle. By knowing what types of support are available for the product, clients can take better advantage of their investment in technological innovation and plan their future in the tech environment strategically and successfully.

The end of the life cycle comes when  no longer offers updates to resolve issues, patches, assistance or technical support for discontinued versions of the product.

Release Year Full Support  Transition Maintenance Discontinued Life Span Technological changes
1989 1995 1996 1997 Enero 1998 6+2  C
1996 2004 2005 2006 Enero 2007 8+2 Java 1.0, Servlet 2.2, JSP 1.1, NS3
2005  2014 2015  2016 Enero 2017 9+2 Java 1.5, Servlet 2.4, JSP 2.0, NS8, IE7
2015 2024(i) 2025 2026 Enero 2027 9+2 Java 1.8, NIO, Servlet 3.1, JSP2.3; EL3.0,
WebSocket 1.1, Firefox, IE11, Chrome, Safari

Soporte estimado para la línea de productos 2015.

Support is divided into three consecutive periods which determine the benefits  offers for adopted products.


Our products are fully supported with complete service, including:

  • Complete production support
  • Major and minor updates
  • Service Pack and issue resolution

During this period, previously-offered benefits and features will be maintained and transition planning to a new available version may begin. During this phase, the company does not support the incorporation of new functionality or technological changes such as new browsers, operating systems or infrastructure (databases, Java JDK, Tomcat, etc.).

For reference, Axional 2005 includes support for Java JDK 1.7, Tomcat 5.5.35, Linux RH 6, RH7, CentOS 6 and browser support for CentOs7, and FF 37, Chrome 42, and MS IE 10 and 11.


If a client wishes to maintain an old product version, they will have some limited services available:

  • Complete production support
  • Specific Service Packs

When the product life cycle reaches the discontinuation phase, we recommend clients migrate to the new Axional product line. This migration may entail changes in licensing policy and system architecture.

If migration is not carried out, it may be possible to acquire Special Support Extension (SSE) so clients can maintain complete coverage before end of service and ensure their company is protected.

As such, continuous support will be available so that your company can keep functioning until you are able to migrate to the new Axional product line in such a way that service is not interrupted.

SSE, in these cases, does not involve fixes or updates, nor does it support new features.


For companies, upgrading to the new Axional product line offers several advantages:

  • Exceptional performance.
  • Access to the latest application server technologies.
  • Greater security based on new role-based access control algorithms.
  • Support for latest-generation browsers.
  • New Business Intelligence solutions and OLAP engines.
  • Native support for the use of Informix Warehouse Accelerator (IWA).
  • Integration with the new Axional IB and Axional Studio product line.
  • Ability to obtain geofencing statistical data.
  • New business graphic creation functions.
  • Reliability and effectiveness.
  • Full integration and transparency.
  • The number and type of usage licenses can be better adjusted to the needs of your company.
  • The SaaS model lets you easily adapt to the fluctuations and flow of your business.
  • Purchased licenses that are no longer used become a thing of the past.
  • Software runs on an operating expenses (OPEX) model rather than a capital expenditure (CAPEX) model, so it’s easier to schedule around budgetary periods.

At d we want to provide our clients as much information as possible so they can make the best decisions and plan their evolution towards a new product line that adapts to their company’s needs and makes them more competitive in the current market.

That’s why our products have an approximately 10-year life cycle, to make way for a new line of solutions more in touch with the technologies of the present moment.


Products reach the end of their life cycle for various reasons:

  • Technological innovation.
  • Market demand.
  • Discontinuation

As a result, we’ve established an EOL policy to help clients better manage their transition and so that d can help them migrate to new, updated product lines as part of their renewal path.

General policy guidelines are:

  • As a general rule,  will alert clients to the date of end-of-life (EOL) for a product. This alert will also appear on the d blog.
  • When a product reaches EOL, all support services will become unavailable and the product will be obsolete and no longer catalogued.
  • After the EOL date,  does not commit to developing, fixing or maintaining a product.
  • So long as the client is up-to-date with product maintenance SEE (Soporte Extendido Especial), will be provided and must be adopted immediately after the product EOL. Please contact the administrator of your support account to adopt SSE before the EOL of your product so that we can assist you during the transition period.
  • If a client is not up-to-date with maintenance and wishes to adopt SSE at the end of a product’s EOL, they must pay retroactively for maintenance since the last adoption of service or, alternatively, since the date of product purchase.
  • If a client decides to make a change to new hardware during a product’s EOL Transición period, a new license for the new hardware will be required in accordance with the current licensing policy in effect. In addition,  is not responsible for the functionality of applications until the client migrates to the current.

 reserves the right to modify the present EOL policy for different product lines.
Any modification to product policy will be communicated to all clients and published in the support policy section for EOL products on the website.

When their life cycle ends, Deister’s software products enter a Transition period so that clients may carry out a well-planned migration to the new version.

Those clients who do not wish to migrate products that have reached end-of-life  (EOL) have the option of acquiring Special Support Extension (SSE) so they can maintain complete coverage before end of service and keep protecting their investment.

The features and benefits of this support are adopted individually, prioritizing the concrete needs of each client and the characteristics of the discontinued products.

In this way, continuous support remains available to maintain company operations until migration to the new Axional product line can occur without interrupting service.


Clients should note, however, that SSE carries certain restrictions:

  • The annual cost of this service progressively increases by 10% each year, due to the necessity of keeping up operational equipment and tools for obsolete software.
  • It does not entail fixes, updates, security alerts or new functionalities.
  • It does not entail certification or integration with new d
  •  Support is only authorized for the hardware and software environments (operating systems, web browsers, etc.) that were accepted during the product’s Full Support period.
  • This SSE support must be adopted before the product moves to the Discontinued phase. If adopted afterwards, the price will include annual payments that may have been due from the product end-of-life date up until the date of adoption.

Users of discontinued products who opt to continue using unsupported software should be aware of the risks they incur.

The use of unsupported software means d will not provide support of any kind, including issue resolution procedures or programs.

As such, systems may become vulnerable and put your company and clients in risky situations, seriously limiting your ability to maximize the potential of the rest of your investments in technological innovation.

For more information about the special support extension program for d products that will no longer be catalogued, please contact your d representative, request a visit, or request a business call.

Axional Suite runs on the most recent web browsers available from major browser manufacturers. The Browser Compatibility Table (BCT) aims to keep our users informed which browsers Axional supports.

We strongly recommend using the most recent versions of supported browsers in order to get the most out of Axional software’s available functionality, with better performance and enhanced security features.

If you are using an older browser not listed in this table, please contact your Axional account representative to check the availability of the most appropriate browser for your workstation.

Version IE10 IE11 Edge Chrome Firefox Safari

You can find the launch date of the application on the login screen by clicking the “i” (version) icon.