FoxWeave lets you to Design and Run your integration tasks in the cloud "On-FoxWeave". Everything happens on-demand within FoxWeave, driven from inside your browser. You don't need to offload the running of your integration tasks to other environments.

This is the standard option provided across all cloud integration services. In fact, it's the only option provided by most other services. FoxWeave provides more options (see On-Premise and On-PaaS below).

Sometimes you need to run your integrations tasks inside your company firewall i.e. On-Premise. You might need to migrate/sync data to or from an App or Database running on-premise, or maybe the data involved is very sensitive and so you'd prefer not to expose it to your integration provider by running the task On-FoxWeave (see above).

FoxWeave lets you easily run your integrations On-Premise. You still design your integration tasks in your browser On-FoxWeave, but you can select to have those tasks run on one of your machines running inside your company firewall, or on one of your Amazon AWS instances (or some other IaaS).

This is not standard among other integrations services, but is provided by FoxWeave and is very easy to configure and use.  It is an essential feature if you want to solve many common synchronization and migration use cases.

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 providers.

If you’re interested in seeing support for other providers, just let us know (tfennelly@foxweave.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.