Who to talk to
If you are considering deploying Tines in a self-hosted environment, please first contact your Account Executive or Customer Success Manager to explore your options.
Following that conversation you’ll be put in touch with the right technical resources in Tines to help you access the Tines Docker images, guide you through the installation, and provide ongoing support.
We highly recommend sharing the relevant pages in this section — particularly Reference Architecture, Connectivity Requirements, and Sizing & Scaling — with your internal IT/infrastructure/network admin/security teams early (as appropriate) to provision the infrastructure, services, and network connectivity required.
Compatible environments
Tines self-hosted artifacts are delivered as a set of Docker images, which means it runs in any containerized environment where Docker images are supported. Tines has been deployed successfully by our customers in the following environments:
AWS Elastic Container Service (Fargate and EC2)
AWS Elastic Kubernetes Service
Azure Container Service
Azure Kubernetes Service
Google Kubernetes Engine
Red Hat OpenShift
VMware Virtual Machine
Docker Compose on:
AWS EC2 instances
Azure Virtual Machine Instances
Google Virtual Machine Instances
Tines will support our application running on any container orchestration system and infrastructure once the requirements laid out below are satisfied (though correct operation of that container orchestration system and infrastructure remains the responsibility of the customer).