AppBus’ Application eXtension Platform (AXP) is a platform for creating APIs on top of legacy applications.
How Does AXP differ from RPA?
AXP tooling shares a lot in common with RPA. The “hooks” into your legacy applications will be the same between AXP and RPA solutions.
However, traditional RPA is not built for creating APIs. It doesn’t cost effectively scale and it has issues with reliability. The API design process is front and center in AppBus. The deployment model addresses many of the common scalability concerns with traditional RPA. Finally, making APIs created with AXP as reliable as possible is at the core of the solution.
Is AXP a SaaS product?
The main control plane for AXP runs in the cloud. However, all APIs are backed by workers (sometimes referred to as bots in traditional RPA). These AXP workers can be deployed in AppBus Cloud or on-prem depending on the requirements of your organization.
Can AppBus work with my API management solution?
Absolutely! Every API created in AXP is OpenAPI compliant. This makes it extremely straightforward to integrate with tools like MuleSoft, Apigee, Dell Boomi, and others.
What kind of use cases is AXP best suited for?
AppBus AXP is most relevant when a function is able to be performed in an application’s GUI, but not through an API. This is what we refer to as the “API gap”. Many legacy applications lack API’s or have APIs which are either incomplete or impossible to decipher.
With AppBus you can remove blockers from your digital transformation initiatives, and worry about replacing legacy systems only after the project’s value is clearly demonstrated.