Skip to content

Overview

Development

Overview

IDEs

API Explorer

Installing TORO Integrate on Your Own Server

A server deployment requires the client or organization to maintain TORO Integrate, its family of required services1, and the hardware it will sit on2. Done right, this type of deployment will prove beneficial to clients who want absolute control of TORO Integrate's configuration and environment.

Flexible deployment models

Aside from deploying TORO Integrate on your own server (be it using on-premise hardware or through a public cloud provider), you can also run TORO Integrate on top of TORO Cloud, or both.

TORO Integrate is compatible with and can operate on top of many platforms. Supported operating systems include macOS, Linux, and Windows. In addition to this, you can also deploy TORO Integrate using Docker, and have it publicly available using a cloud service provider like AWS.

But of course, setting TORO Integrate from the ground up by yourself requires you to ensure its prerequisites are satisfied, and adjust other settings such as firewall configurations.

To help you with these tasks, we've compiled a collection of guides:

  • Prerequisites

    Learn what you need in order to run TORO Integrate.

  • OS Installation

    Planning to install TORO Integrate directly on top of your OS? Check this page to learn how to install it on macOs, Linux, and Windows.

  • Deploying with Docker

    Everything you need to know about deploying TORO Integrate on Docker.

  • Deploying with CloudFormation

    Learn how to quicky deploy TORO Integrate on AWS using TORO's AWS CloudFormation template.

  • Firewall Configuration

    Firewall configuration for instances installed behind a server.

  • Domain Proxying

    Proxy your TORO Integrate instance's domain so your users can easily access the instance via a more memorable address.

  • Startup & Shutdown

    Learn the different ways you can start TORO Integrate.

  • Directory Structure

    How TORO Integrate's files and directories are organized.


  1. Including, but not limited to: databases, Solr servers, brokers. 

  2. Optionally delegating this task to a provider should the organization opt for a cloud service subscription.