Best in class pricing for light workloads. Superior performance for heavy workloads.
180 Days of Logs
All Product Connectors
All Technology Connectors
30 Hours Support Included
Choice of Region
To learn more (e.g., what are Workflows and Sites, why hand-coding integrations can be a problem), see our FAQs.
Need private cloud for the enterprise?
Not sure what you need yet?
Sign up for a 14 day trial including all features and we’ll help you get your first proof-of-concept Workflow up and running.
Add 50 Users
50 additional Users per Site
Add 50 Workflows
50 additional Workflows across all Sites
Bind Workflows to REST Endpoints to create API’s
View the full design history of each Workflow with rollback and fork
Publish Workflow Revisions to separate Environments using a formal promotion process
Get insight into how Workflows, Connections and DropPoints are related to each other
Flowgear operates a Professional Services team to help organizations that don’t have the time or skills to create or manage integrations. Services include project definition, creating and implementing integration workflows, and support on an existing integrations
25 hours of Professional Services per year
50 hours of Professional Services per year
100 hours of Professional Services per year
What is a Workflow?
A workflow in Flowgear is the sequence of steps to perform an integration – typically it involves pulling data from a source, then some data transformation or validation, and finishing by pushing the data into a target system. Flowgear workflows are created in the Flowgear Console which includes a visual designer for building and maintaining integrations.
For example, an integration that takes customer and order data from Salesforce, and loads that data as accounts and orders into Sage One, would comprise two workflows – one for customers/accounts, the other for orders.
Once design of a Workflow is complete, it can be activated in one of three ways:
What is a Site?
A Site provides isolation between our clients. Assets such as endpoint connections and Workflows are associated with a specific Site. User roles are also managed per Site.
Most organisations use only a single Site regardless of geographic locations of services and apps. However, some choose to split integration workfloads into separate Sites in order to isolate them from each other, typically according to Workflow function.
Can I purchase additional support?
Yes – Please get in touch with us to discuss an appropriately sized support plan.
Also, if your organisation doesn’t have developers available to create the solutions you need, you can engage the Flowgear Professional Services team to have the integrations built for you.
I can't find the Connector I need
If you don’t see the Connector for the app or service you need, please get in touch with us.
In most instances, it’s also not necessary to have a Product Connector in order to integrate. For example, Connectors such as Web Request can be used to integrate via a RESTful API or the SQL Database Connectors can be used to query information directly.
If you’re a developer, we’ve also made it very easy to build your own Connectors.
Can I purchase multiple subscriptions of a plan?
Yes – if you’ve exceeded the number of Workflows permitted on a plan but aren’t ready to jump to the next plan up, you can purchase additional subscriptions of the existing plan.
How does Revision Management work?
Every time a Workflow is saved, the Workflow revision number is incremented and the old version is retained. Developers are able to view either the current (head) revision or browse back to prior versions. Read more about Revision Management.
How does Release Management work?
Release Management allows developers to control when Workflows are promoted to a different Flowgear Environment. This capability allows enhancements to be made to existing Workflows within a Test Environment so as not to disrupt Production use. Combined with Revision Management, it is also possible to roll back to earlier versions of a Workflow when needed. Read more about Release Management.
Are other log retention policies available?
Yes – clients may customize the log retention period on the Standard and Premium plans to between 1 and 90 days for Standard or between 1 and 180 days for Premium.
As a developer, why should I use Flowgear rather than hand-coding integrations?
As a developer, your most precious resource is time. With Flowgear, you will drastically reduce the time to develop, deploy and maintain integrations, freeing you to focus your time and effort on the apps you’re building rather than the integrations it needs to support.
To find out more, read Should you Build or Buy a software integration solution.