Security is the cornerstone of each information system; in case such system should be taken seriously. Moreover, governmental systems became targets of hybrid wars.

ROBON is secure by design. All parts of the application were designed and built from a scratch to meet all reasonably required security standards. Security of user identity and authenticity is similar to internetbanking systems. Data transfers are encrypted by customer’s choice of encryption. Vulnerabilities of traditional email systems is eliminated by different architecture.

ROBON is compliant with eIDAS security recommendation.

Similarly designed application runs for more than 10 years without any security breach despite of being under attacks on daily basis.

Document management systems (DMS) are implemented in most of countries. Why then ROBON?

DMS implementation is mostly done in central agencies, where the number of documents is large and DMS is the only way how to handle the number of documents. DMS systems, (although there might be implemented centrally and regulated by law) for a good reason might be governmental agency specific. DMS systems are not implemented in small governmental agencies, typically in small municipalities.

ROBON interconnects ALL governmental agencies while protecting particular agency specifics and investments.

ROBON as an eGovernment asynchronous Enterprise Service Bus (ESB) interconnects governmental administration in one communication structure with trusted documents and data messaging.

It is advised to build as soon as possible testing environment including DMS API, make API available to DMS developers, discuss with them how to connect DMS to ROBON. It is necessary to allow enough time to test DMS connections to ROBON before launching production environment of ROBON.

Remember: User experience of DMS users must remain unchanged after connection of DMS to ROBON.

We are quite flexible in terms of financing.


To share some experience, it makes a good sense to implement ROBON in indicated phases, e.g., to implement first ROBON Core Services, then ROBON Advanced Services. It is important to know, that G2G communication as well as the communication G2B and G2C should be paid by the government. B2B and B2C communication should be paid by the sending or receiving party. (E. g., bank may want to pay the incoming messages for its clients.


Thus, we would recommend to finance ROBON I. using CAPEX/OPEX model, ROBON II. on performance and/or revenue sharing basis.

We expect to cooperate with local partners.

We would expect local IT partners to provide communication and hardware infrastructure, L1 support staff. We expect local law firm to support local legislation compliance.

Cooperation with local electronic means of identification is definite prerequisite.

It is the customer who has to own the solution completely. In ubiquitous hybrid war, national digital sovereignty becomes the cornerstone of country’s defense. ROBON is secured by design, which means among others that ROBON architecture expects it is the customer who seeds own cryptographic mechanism into ROBON framework. Not only us as ROBON authors can tamper with transferred data content, much less someone else. Registered and authorized users are usually the biggest and difficult to control thread, ROBON’s audit mechanism can handle also this danger.
Get ROBON – get safe.