Answer to common requirements, questions, doubts

Find out here our security framework.

Find out here how we ensure system scalability.

Find out here how we ensure system availability.

Find out here how we support ISO 27001 compliance.

Find out here how we manage the privacy of our customers and end users in compliance with GDPR.

Find out here how you will ensure the compliance with GDPR of your DPS system.

Find out here how we fulfill the obligations of the NIS 2 directive.

Find out here how we let you fulfill technical obligations and maximize monetization opportunities of the EU Data Act.

If you use Servitly, we want this to be your choice, not something you are forced into by an unbreakable lock-in. Here is how Servitly makes your DPS portable.

Data is yours

All the data stored in your DPS belongs to you. You can export it at any time through the API , and use it however you need.

Full independence from our domain

All the URLs your users, devices, and other applications use to interact with the DPS belong to you, not to servitly.com.

For example:

• Users access the DPS at connect.acme.com

• Devices communicate via MQTT at mqtt.acme.com

• Applications call the available APIs at api.acme.com

If you ever decide to replace our DPS with another solution, you won't need to change your users' bookmarks, update other applications, or touch the firmware of your products.

Exportable, machine-readable configuration

You can export your entire DPS configuration at any time through the Configuration Management features.

The export file is machine-readable. It contains everything you need to move your system elsewhere, and it can also generate documentation automatically.

This includes the parts of the configuration where most of your intellectual property lives: your algorithms and your templates.

Evaluating the long-term continuity of a strategic technology partner is a standard part of enterprise due diligence, particularly for a system as central to operations as a Digital Product-Service System. For this reason, we offer an optional escrow agreement as part of our enterprise offering.

Under this agreement, a neutral third-party escrow agent holds a copy of the Servitly source code on our behalf. In the event Servitly were to cease operations, the agent releases the source code, along with related technical documentation, directly to the subscribing customer, ensuring continued access to the technology underlying your Digital Product-Service System.

What really counts is the intellectual ownership of the part of your application that generates added value, such as data processing rules, algorithms, analytical functions, action recommendations.

This represents only a small part of the source code. Everything else is just a huge burden to maintain.

Servitly leaves you the owner of those parts.

What makes the difference between you and your competitors is not how you write the source code of the application, but the impact it has on its users.

Does it give them useful information?

Does it save them time or resources?

Does it help them in their daily operations?

Does it support them in achieving the desired outcomes?

Servitly helps you focus exactly on those aspects.

In reality, even the source code does not free you from lock-in.

Instead of having a lock-in with the system supplier, you have it with the people who developed it. At the first staff turnover, you will have to manage the same kind of risk.

Servitly supports you in portability and handover.

In reality, a DPS system supporting a winning product-service strategy is much more than ’making dashboards’.

You will have to build an enterprise application, with support for business workflows, multiple interfaces, demanding security, scalability and regulatory requirements, integration with information systems (CRM, ERP, ticketing).

If you think only about 'making dashboards', you are surely underestimating the effort.

This is the most dangerous reason, and a well known cognitive bias: sunk cost fallacy.

Having invested millions in an ineffective solution is not at all a good reason to continue doing so.