From a form factor perspective, CA Live API Creator can be put together as simple policy configurations incorporated into your DevOps processes and deployed to running servers, or packaged up with the API Server itself and deployed as a WAR, or deployed - as a Docker container, onto Cloud Foundry, into AWS Elastic Beanstalk, into Azure, or just about anywhere else you can think of.

You can design the bounds however you’d like, to fit within the context of your application. It can be single endpoint, it can be a resource or set of resources, it can be a project that incorporates multiple endpoints and APIs, it can be an account, to enforce multi-tenancy and role-based access control, or it can be an entire server with multiple accounts with multiple projects.

Services can be developed completely independently, and then composed into orchestrated components. There’s no external dependency whatsoever; if you don’t have an existing database to work with, you can create your own from scratch, including defining the data model in an application-centric UI.

These APIs are also independently deployable. They can be built into existing build and deploy processes, using import/export/modification features available through the UI, through a CLI, through an API, and through an SDK. They can be deployed on any of the platforms supported by the product.

With a single API Server running multiple APIs, each transaction runs in a separate thread and won’t affect the others. If you want host isolation, you can deploy separate API Server instances, or you can spin up multiple Docker instances for container-based isolation.