What does the Synatic platform interface look like and does it adapt to the users requirements?

There is a singular interface to Synatic that adapts in accordance with the users’ requirements and how they are administratively set up. This compromises of 5 major areas:

  1. Administration – administrative users can log in to this interface and allow specific users access to specific portions of the solution. They can set up new users, deactivate users, link organisations, check on current billing and manage the system’s API key. Further administrative users can check and assess both the event log and the change log from a single point, allowing them to assess all activities in the system.

  2. Flow design – the manner in which a user does this is to drag on a source on the left of the canvas, then to take the data that is sourced through transformation, augmentation (called a lookup in system to fetch additional data), splitting of data into sub flows in parallel or on condition. The data that is transformed is then sent to a destination, be that a file, database, API or SDK. This is a process that a power user / technical consultant should be able to handle

  3. On prem relay – this allows Synatic to connect up to an on prem solution from the cloud without calling in via the firewall. The on prem relay calls out to push data to Synatic, and calls out to pull data down from Synatic, thereby circumventing the need for inward bound connections.

  4. API set up – ability for users to configure API calls that expose flows and / or buffers externally to other systems. This includes complex API creation, or simple incoming webhooks.

  5. Ops Portal – this is a powerful part of Synatic that allows a user to see very cut down portions of the application that allows them to focus on the tasks that they need to handle. Whether this is error management, inputting of mapping values or approving a workflow of data between two solutions; Synatic can handle this interaction without requiring an additional interface.