There are two variations of a private instance of Ellipsis Drive:
  1. 1.
    An instance deployed on our own cloud infrastructure reserved for your use only.
  2. 2.
    An instance deployed on your own (cloud) infrastructure.
For option 1, deployment and management of the instance is entirely managed by us. For option 2, deployment and management can only be done by us if we are given sufficient access to your infrastructure. Otherwise, we will provide remote guidance on the deployment and management process.

Option 1

Option 1 is the deployment of a private instance of Ellipsis Drive on our own cloud infrastructure, managed by the Ellipsis Drive team and reserved for your use only (single tenant). It is the most simple option to get started with private Ellipsis Drive instance. A default configuration of this option can be made available for you within two weeks.


To make sure only you can access your private instance we will place your instance in it's own network. With cloud interconnect your private instance will be connected to your own internal network. This ensures that only people with access to your own internal network can access your private instance.

Deployment process

After determining the scale, form of access management, and other settings, our team at Ellipsis Drive will get to work to deploy the private instance on our cloud infrastructure. Some commitment from you is required in order to connect your instance to your internal network.

Option 2

Option 2 is the deployment of an Ellipsis Drive instance on your own infrastructure. It allows complete integration of the instance into your network for maximum security. It also allows you to deploy Ellipsis Drive on top of an existing file storage that contains data that you want to immediately activate with Ellipsis Drive.
Deployment and management of the process can be managed by the Ellipsis Drive team. For this we will need full access to the portion of your infrastructure that Ellipsis Drive is planned to be deployed on. For example, you can create a separate project for Ellipsis Drive on your cloud provider and grant us admin access to that single project.
If this is not feasible, we will guide your team through the deployment and management process instead.
Depending on the complexity of the environment in which Ellipsis Drive is deployed, the time required to deploy under Option 2 can be around one month. If you decide to deploy Ellipsis Drive yourself, we advice to prepare at least one full time effort for this duration.

Deployment process

If our team is given full access to the part of your infrastructure that you are planning to deploy Ellipsis Drive, your team does not need to do anything else during the deployment process. We will deliver the API endpoint and access to the machines after the deployment process.
Below is the general process to be followed if you choose to deploy Ellipsis Drive yourself.


Ellipsis Drive consists of different processes working together, where each process must be deployed as a separate docker container. It is highly recommended to run each of these docker containers on a separate (virtual) machine for ease of deployment, management and performance stability.
Each of the containers must be able to reach each other by their (internal) IP address. It is highly recommended to put all the containers inside the same VPC. Subnets are not required as the IP (ranges) of the servers can be set up using the config files.
The containers running the API processes are the only containers that the users of the system need to reach. This container must be reachable from the network of your users. The rest of the containers do not need access to the public internet, but it is recommended to still allow outbound connections for them for system updates.
If you deploy Ellipsis Drive on top of an existing file storage, Ellipsis Drive will need read and write access to this file system. Other processes are not allowed to write to this same file system, otherwise, Ellipsis Drive will not work properly.
Required knowledge
In order to successfully launch Ellipsis Drive on your cloud you need to be at least familiiar with
1 Creating virtual Machines in your cloud
2 Running docker images
3 Managing your virtual machines. Disk size, RAM and number of cpu's
4 Using ssh to enter your virtual machines

Deployment steps

  1. 1.
    Define and set up the infrastructure environment to deploy Ellipsis Drive.
  2. 2.
    Download the latest Ellipsis Drive docker image.
  3. 3.
    Create a docker container out of the image.
  4. 4.
    Edit the configuration file inside the container to suit your needs.
  5. 5.
    Follow the installation guide to create one of the machines needed by Ellipsis Drive out of the docker container, using the setup script inside the container.
  6. 6.
    Repeat steps 3 to 5 for each machine needed and the scale of the deployment.
  7. 7.
    (Optional) If you deployed Ellipsis Drive on top of an existing file storage, you can run a script that comes with the docker image to start the process of importing the existing data to Ellipsis Drive.
  8. 8.
    The private instance of Ellipsis Drive is ready for use.


Upgrading to a newer version of Ellipsis Drive requires you to check out the repository branch of the new version on the main control server. Then, run the upgrade script that automatically updates all the other servers, databases and file systems.