Security

From its conception, Primordia has been designed with core objective to strongly secure both the platform and the networked world it will generate. Thus, security is tightly integrated in all layers and components of the platform’s architecture, and it is constantly upgraded and enhanced in every new release, following and adopting the latest standards, techniques and practices in the field of Information Security. As a low code platform, software security features are applied to all deployed apps and to every installation, regardless the type or size of the underlying infrastructure, and they are employed on top of any other security technology (hardware or software) of this infrastructure. As a platform used to generate and interconnect distributed nodes, security has been embedded in all interactions, communications and transactions among nodes, to ensure that each and every node is protected against threats from the outside world, and that all transactions among interfaced nodes are secured, properly authorized and certified.

Encryption is by default applied whenever data are transferred between architecture layers and between interacting services within the same layer. Encryption is also enforced in database level for core Primordia Data (i.e. entities, assets, interactions etc). On the contrary, apps data encryption is configured by Designers or Asset Managers, depending on the type of data (e.g. sensitive or private information), and may be applied in Model level, to specific record sets, to specific fields, based on specific conditions, to data created or accessible by specific users or beneficiaries etc).

The platform incorporates its own identity management module, which covers both local and remote users and organizes them by node and beneficiary, but it can also be integrated with any third party IDM platform available in the market. Access to platform’s services and core data repositories (entities & assets) is controlled by a powerful multi-level permissions management module, based on established relations among nodes, beneficiary origins (local or remote), user types, positons, exercised access profiles, roles, groups and information classification. Registering or updating Primordia entities (e.g. nodes, beneficiaries, users, accessible apps, assigned processes etc) are restricted actions, requiring approval in order to be completed. Actions upon Primordia assets (i.e. specifications) are controlled by Designers or Asset Managers, by organizing assets (of the same specification level) in groups, assigning to groups specific access policies, and managing users and beneficiaries subscriptions. For example, an active subscription of a Beneficiary to an “Asset Sharing” group of Operations, associated with an access policy permitting “Asset Integration” and “Asset Co-Design” actions to its subscribers, allows users of this Beneficiary with an active “Designer” position, to integrate any of the group’s Operations to processes they design, as well as to modify or extend the specifications of those operations, assuming they are in “Under Development” status. Similarly, an active subscription of a Beneficiary to an “Asset Export” group of Services (applicable only to Beneficiaries of interfaced Nodes), associated with an access policy permitting “Unconditional Export”, allows users of this Beneficiary with an active “Exporter” position, to transfer any of the group’s Services to their host Node, assuming they are in “Published” status. Access to apps and processes, as well as actions upon app data, are authorized using a different approach. Apps are organized in groups, and they get directly accessible by Beneficiaries that maintain an active subscription to those groups. Access to an app means that the beneficiary may request to be assigned one or more processes contained to this app (micro-apps or workflows), as well as to request the appointment of one or more roles engaged in those processes (of performer, participant or supervisor type) to one or more of its users with an active “Process Participant” position, Users appointed a performer role will be able to use a micro-app process or initiate a workflow process, users appointed a participant role will be able to undertake and execute tasks associated to this role, while users appointed a supervisor role will be able to monitor process execution, change tasks assignments, pause or resume process, as well as acquire access to operation and service log reports.

All actions upon Primordia entities (i.e. nodes, beneficiaries, users, groups, roles, permissions etc) and upon assets (i.e. specifications), regardless the performer (i.e. system or user), are analytically logged along with data past versions, enabling users to fully monitor system resources utilization, indicate unauthorized access or actions, or restore data from previous versions after a security breach.

Universal keys are utilized to uniquely identify Nodes and their hosted entities (e.g. beneficiaries, users, contracts etc) and assets (i.e. specifications) in Primordia world, as well as to virtually link their reflections or copies, generated in remote nodes as a result of a transfer or exporting process respectively. Global keys are also assigned to data created and manipulated by Primordia apps (record sets following Model specifications), so as all their instances in different nodes (i.e. created after data exchange) can be linked to the original. Each transaction between nodes, including interface generation and heartbeat check, is authorized or not through a standard process performed in both nodes, involving node validation (activity which protects original nodes from imposter software), node verification (using SSL certificates) and node authentication (using public and private keys and universal identifiers). Each node maintains a directory of all Primordia nodes (universal identifiers, locations, public keys, certificates etc), the interfaces among nodes and their transactions, which gets updated every time nodes are interacting with each other. Transactions among nodes require verification by a third Primordia Node (designated specifically for this purpose by the “interacted” node), in order to be considered as completed, else both nodes rollback transactions. Each interaction is logged by both nodes and the certifier.

Performance

Primordia nodes are multi-user & multi organization service provision infrastructures able to cope with huge volumes of data and vast amounts of concurrent node-to-node or node-to-device interactions, with exceptional operational efficiency, guaranteed by the platform’s architecture itself. Prior to any app deployment, all relevant specifications are automatically validated, integrated and optimized, to ensure a great user experience in any operational condition. Volume testing and simulation tools enable designers to detect prospective errors or bottlenecks, assess their impact, identify the cause and evaluate recommendations in every level of the specification stack. App & process monitoring tools powered by advanced data visualization dashboards, offer real-time measurement of process execution, service response times and resources utilization (in combination with the conditions of the execution environment), assisting designers to identify where and what extent of reconfiguration will align app operation to the usage patterns of its target user community.

Self-Deployment

Lorem ipsum

Accessibility

Lorem ipsum

Connectivity

Lorem ipsum

Scalability

Designed to operate as an orchestration of self-reliant modules in every layer of its multi-layer architecture, autonomously or within a network of nodes sharing their resources for a common objective (e.g. app delivery through services operating in multiple nodes, collaborative processes distribution in several nodes, app export and deployment in another node, direct access of apps in remote nodes etc), the platform offers an impressive ability to scale in vertical, horizontal and network level, so as to accommodate with the most efficient way the changing needs and demands of its user community. Likewise, the ability of the platform (node) to initiate, monitor, settle and broadcast its “relocation” from one infrastructure to another, directly from the node’s management console, and without any effect to its global identity, node interfaces and ime-imprint connections, makes much easier the process of maintaining application performance and availability in high levels as the user communities, their service demands or the node’s networking requirements are increasing.

Integration

Lorem ipsum

Intelligence

Lorem ipsum

People Friendly

Lorem ipsum

Unlimited Potential

Lorem ipsum

Data Protection

Lorem ipsum

Localization

Lorem ipsum