Deployment

The default distribution for JumpWire is through Docker containers. There are two containers published by JumpWire, one for the control web application and one for the execution engine. Additional containers may also be necessary to implement functionality depending on the cloud environment JumpWire is installed into. See the Components page for details.

In addition to cloud container runtimes, JumpWire is compatible with self-hosted Kubernetes environments. The deployment team can provide Helm charts to assist with installation.

Terraform code for deploying to GCP Elastic Container Service is available at https://github.com/jumpwire-ai/infrastructure-tools/tree/main/terraform/gcp/gce.

To use JumpWire with Google Kubernetes Engine, follow the instructions for Self-hosting with Helm.

Terraform code for deploying to AWS Elastic Container Service is available at https://github.com/jumpwire-ai/infrastructure-tools/tree/main/terraform/aws/ecs. Instructions for using the web console are also available at Self-hosting with AWS ECS.

To use JumpWire with Amazon Elastic Kubernetes Service, follow the instructions for Self-hosting with Helm.

JumpWire supports any OAuth or OpenID providers for authenticating to the web frontend with client credentials configured during setup.

If your preferred provider is not listed below, let us know and we will add it!

Google’s Single Sign On for OAuth authentication. The OAuth client is tied to an installation’s domain name (for callbacks) and a customer’s email domain (for identity verification).

You can read more about provisioning Google OAuth applications on this support page.

When using Google OAuth, the following Configuration variables must be set:

Details on setting up a new Auth0 application are available in Auth0's documentation. The application should be a "Regular Web Application" with these settings:

When using Auth0, the following Configuration variables must be set: