FoxWeave also allows you to run your integration tasks out on your
Platform as a Service (PaaS) i.e. On-PaaS. Again, all the integration task Design and Maintainiance
is done On-FoxWeave (from your browser), but you can select to run the task on your own account on your
PaaS provider's infrastructure.
This provides some of the benefits of both the On-FoxWeave
and On-Premise models (see above). In some ways, On-PaaS can be thought of as a hybrid/compromise between
On-FoxWeave and On-Premise. It provides the cloud based runtime (no infrastructure setup) benefits
of the On-FoxWeave model, while at the same time letting you run your integration tasks on
infrastructure that you might already have a lot of trust in in terms of
reliability, security etc (i.e. your PaaS providers infrastructure).
We currently support the CloudBees and
CloudFoundry PaaS providers.
In the case of CloudFoundry, we have successfully
run integrations on CloudFoundry.com. In theory however, it should be possible to configure your own
private CloudFoundry PaaS on Amazon AWS, or use one of the other CloudFoundry based PaaS
If you’re interested in seeing support for other providers, just let us know
(email@example.com). If the
provider has JEE Web Container support with an open SDK for deploying to their
infrastructure, then we can add support in no time.