Skip to main content

​
Getting Started

To run Paragon on-premise, you’ll need:
  • A Paragon license
  • A major cloud provider account (e.g. AWS, Azure, or GCP)
  • A domain name
  • An email provider (SendGrid or any SMTP provider)

​
Paragon License

Paragon authenticates its license to our cloud at boot and periodically to ensure the license is valid and the system can run. If you don’t already have a license, please contact sales@useparagon.com, and we’ll get you connected.

​
Major cloud provider account

Paragon comes bundled with a set of docker images, meaning you can run it on AWS, GCP, Azure, or any other server or cloud that supports Docker and has internet connectivity. It’s most resilient when running in Kubernetes. We have first class support for AWS, Azure and GCP. For Managed On-Premise installations, you’ll need to provide credentials to provision your account. Here are links to instructions for the AWS, Azure, and GCP:

Configuring Managed AWS

Configuring Managed Azure

Configuring Managed GCP

​
Terraform Account

The infrastructure state is managed within Terraform, a tool for managing infrastructure as code. For managed on-premise, we’ll use our own Terraform account.

​
Email provider

Paragon sends transactional email from your instance, including:
  • Failed workflow emails
  • Inviting team members
  • Resetting passwords
You can use SendGrid or any SMTP provider. For SendGrid, you’ll need an API key and a sender identity approved in the SendGrid dashboard. For SMTP, you’ll need the host, port, and authentication details for your provider.

​
Domain name

A domain name is used to create a zone and CNAMEs for the microservices. You can purchase a domain name on Namecheap or provide a subdomain for an existing domain and we’ll create CNAMEs under that subdomain.

​
Infrastructure Components

You will need some additional infrastructure components including:
  • Kubernetes cluster
  • Postgres database
  • Redis database
  • S3-compliant object store
You can learn more about these on the Infrastructure Architecture page. To see how to configure these components for AWS, Azure, or GCP using Terraform, reference the on-premise repo here.