Feature Specifications

Below is an overview of the components that makeup Gearproxy and the specifications behind each.

Professional Services

One of our key differences is our full service offering. Most iPaaS providers only want to provide the system, while you or your team do all the work including setup, configuration, research, analysis and even programming. Our trained professionals take on all of this so you can continue with your day to day business. The cost and 'know how' are handled by our experienced team and we will even be available after the go live; we are in this together, full service ahead!

Support

Customizations

Upgrades

Implementation

Monitoring

Analysis

Gears

These are small independent apps that send and receive data. They also have intelligent monitoring built in so that the systems can be made aware of any issues in real-time.

Data management

Responsible for managing the consumption and production of data flows. This includes analyzing and transmitting all messages.

Run in the cloud

Gears can run in the cloud if need be for SaaS based systems.

Run on premise

Gears can run on premise (a.k.a behind a firewall) of internal system. This is typically used to support systems that are directly managed by you.

Send & receive

Gears send and receive their data through the Gearproxy hub. This ensures a single, highly available centralized system.

Gear Analytics

Reporting and system health tool set. This component monitors all transactions and system performance over time. By using graphing and data visualization tools, we can quickly understand the current system utilization and performance. This is what we use to monitor your system in real time and to know how all your data is flowing.

Centralized management

This is accessible as an “all platform” view from the system maintainers perspective.

Customized monitoring

All analytics data is partitioned per customer and has separate monitoring criteria.

Trend detection

Aggregates all data into a central location and use it to detect system issues and anomalies.

Alerting

Provides feedback through a user interface and alert messaging so that we are always "on".

Gearproxy Hub

This is the hub that handles all messaging and server side configuration. This includes the queueing cluster along with the supporting node orchestration cluster. This is the “brains” behind the entire system.

Fully encrypted

All communication going in and out from the cluster are fully encrypted. All persisted messages are encrypted at rest.

Multitenant

Supports many customers within this same infrastructure.

Routing

Contains routing and registration logic for each customer. This ensures all messaging is synchronized and monitored.

Message semantics

All messaging logic and flow (for reading and writing purposes) for each message group are stored in this cluster.

Failover

Redundant servers are always running and ready to take over messaging just in case of failures.

App

Customers can login to their account to view their setup and analytics.

Gearproxy Options

Some use cases involve the need to save and report on the data that Gearproxy handles. This can be done by your existing system. If you do not have this setup, don’t worry, we’ve got you covered through our optional components. Pricing for these are outside the standard service.

Data Storage

In scenarios of which you need a single location to store all your data, this optional feature would work well as we support a wide range of storage options such as standard SQL databases, column oriented, graph based and data lakes.

Business Intelligence (BI)

If you use the optional data storage, you will be able to to report on an analyze this data through our BI platform. This UI provides a login so you can view your data at anytime.

Example Use Case

Below is an illustation of an actual real world usage of Gearproxy in a standard supply chain example.

Supply Chain Invoice Flow

Here’s how Gearproxy can work in a transactional environment. The following components are shown with their corresponding data flow and are in the order of the flow itself:

SalesForce – New Order data is pulled from SalesForce into Gearproxy.
SAP – An existing SAP system receives inventory level data changes from Gearproxy based on the order information.
Google Drive – The PDF invoice that was generated by SAP is now placed into GoogleDrive by Gearproxy. A link is created as well.
Email – An email is generated and sent by Gearproxy that contains the link to the newly generated invoice.