Understanding Platform components

Anne Ramey
Platform Admins, Form Developers, Workflow Developers


The Kinetic Platform consists of 4 primary components: Request, Task, Bridgehub, and Filehub.


Request is the platform component that allows you to build powerful and beautiful front ends for your customers. It contains a drag and drop form editor where you can easily construct the forms you wish to present your users, but also supports the complexities of multi-system integrations, multi-tenancy, and workflow integration on all it's components.

You may also see this referred to as Request CE, Request Core Edition, CE, or Core Edition. The platform is built with a version of Request (CE) that is entirely our own creation, unlike our previous versions (RE or Remedy Edition) that relied on Remedy to be the platform.

Request is the point of connection in the platform where Task, Filehub, Bidgehub, and Request itself all come together to provide the customer with the optimal user experience.


Task is the platform component that allows you to build and execute workflows. It contains a drag and drop workflow editor where you connect code snippets together to build your flexible and powerful workflows. It also contains the engine that runs to execute these workflows and handle errors, providing fast workflow processing and robust error handling for all your workflow needs.

There are hundreds of these code snippets, called handlers, already built and available for use. These can connect you with everything from your local Request system to your AWS provisioning service and everything in between. Also, if you desired integration has an API but no handlers currently available, there are instructions available for you to be able to build your own.

While Task can be used stand alone and is a powerful workflow engine without the rest of the platform, with the platform, it allows you to integrate that powerful workflow into your beautiful front end experience for an optimal user experience.


Bridgehub is the platform component that provides the connectivity between the front-end of the platform and other systems. This is what provides that multi-system integration in Request. There are bridges available today from everything from your local Request system to your racks at RackSpace, and all of the bridges come preinstalled and ready to configure with your account information for each of your integrations.

Bridges provide way for your form builders to interact with a read-only interface to any system with an API in a low-code way. Only platform admins need to understand what connects to what and how to create the queries, and the queries only need to be set up the once to be used any number of times. And if the data source changes, the references in the individual items don't need to be updated, just the once central resource.


Filehub is the platform component that stores and secures the files attached to Request forms. You can choose to store these files in several ways, including local disk and remote amazon drives.