Our Technology

"Every once in a while, a new technology, an old problem, and a big idea turn into an innovation."

ENTITY FABRIC The Universal SoftwareSolutions Entity Fabricis used to describe the Domain Model for the associated application. TheFabric allows for granular, tightlycoupled definition of all elementsincluding structure, relationships,permissions and logic. APPLICATION FRAMEWORK The Application framework exposes a dynamic and responsive, web-based interface to the Entity Fabric. The integrated Application Programming Interface is a first-class citizen of the framework ensuring full support for the Fabric via a common authentication provider for both user and machine interactions. uHUB uHUB The Hub enables dynamic, data-drivenprocess modelling and execution of actionsIt allows for true task segregation, separation of concern and out-of-bandprocessing - making it ideally suited for server-less cloud based environments.


We pride ourselves on our technology and believe in making the latest innovations available through our framework to all our partners. What was previously only available to Enterprise sized organisations is made accessible to small to medium sized businesses. Our dynamic and adaptable architecture and an underlying Microsoft Azure Cloud basis allows us to access an amazingly powerful suite of features on a pay-per-use basis, meaning we can make this available at a next to no cost. Our architecture is based on three primary components. The Entity Fabric component describes the Domain model for the Application. This allows for granular, tightly coupled element definition including Structure, Relationships, Permissions and Logic. The Application Framework provides interaction with the Entity Fabric via a dynamic and responsive web-based application along with an integral API. Our u-Hub is the engine behind the scenes, providing immense capability for dynamic, data-driven process modelling and execution of actions.

Application Framework

The Framework allows User interaction with the underlying Entity Fabric through a dynamic and responsive web-based application. A heavily reliance is placed on re-usable, self generating, convention based components. API endpoints are available for any defined entity with a common authentication provider for both user and machine interactions ensuring that all permissions and business logic are applied at any level throughout the eco-system.
  • Application

    The Application layer allows user interaction with the underlying Entity Fabric. Through the use of re-usable, self generating, convention based components, dynamic and responsive desktop, mobile or web-based application are easily achieved with a shared authentication provider for both user and machine interactions.

  • API

    The API provides full controlled interaction with all elements of the Application layer. Full technical details of the API are available in our documentation portal.

Entity Fabric

Our Entity Fabric provides the Domain Model for the eco-system. The Fabric allows for granular, tightly coupled definition of all elements including Structure and Relationships, Permissions and Logic.
  • Structure and Relationships

    The structure is descibed as a strongly typed first-class citizen of the Entity Fabric. Relationships between entities are fully defined within the structural layer allowing for multi-level entity traversal from any related entity.

    The strongly typed nature of this component allows external systems to query the entity metadata including navigation paths for relationships and entities and associated properties.

  • Logic

    The logic layer is an integral component within the Entity Fabric. It provides capability for custom entity validation (with transaction continuation or rejection), manilpulation of related entities and iterative execution of logic for those entities. The logic layer will automatically log all transactions.

    Logic may be injected into the execution pipeline at all stages allowing for pre-transaction and post-transaction components. Logic may also be extended to communicate with external services via Webhooks.

  • Permissions

    Permissions are defined on an action type basis as retrictive expressions. These are applied at the lowest level ensuring security compliance regardless of the request instigator, source, filter and selection criterea.

    With permissions being data driven, any alteration results in full transaction logging via the standard Logic layer process.


uHub provides dynamic, data-driven process modelling and action execution capability. Through separation of concern and out-of-band processing - true task segregation is achieved making this ideal for server-less cloud based environment. With this underlying environment, Microsoft Azure provides the perfect home for the platform allowing for utilisation of other Azure features such as Machine Learning, Big Data Analytics, PowerBI etc.
  • Sources define information origins for Actions.
  • Triggers are used to initiate Actions.
  • Destinations define information targets for Actions.
  • Outputs are artefacts generated for specific Transformations.
  • Transformations allow information manipulation during the Action.