New Installation
After reviewing the system prerequisites and preparing your environment, you can proceed with installing Nected. Based on your infrastructure setup and intended use, Nected supports two installation methods:
Docker Compose – For local development and testing
Kubernetes (Helm) – For production and staging environments
Aws Marketplace - For production level deployment
Terraform - For full-scale, infrastructure-as-code deployments on Azure
This section provides links to detailed guides for both methods.
Installation Methods
Docker Compose
Local testing, evaluation, development
Installs Nected on a single machine using Docker Compose. Ideal for quick setup, feature validation, and building rule logic. Not suitable for production.
Kubernetes
Production, staging, distributed workloads
Installs Nected on a Kubernetes cluster using official Helm charts. Supports autoscaling, high availability, and full cloud-native integrations.
Amazon Marketplace
Enterprise production deployments requiring AWS compliance
The Nected AWS Marketplace offering provides a one-click deployment solution that automatically provisions all necessary AWS infrastructure components and installs Nected on Amazon EKS using CloudFormation templates and Helm charts.
Terraform
Enterprise-grade Azure deployments, teams requiring reproducible IaC workflows
Deploys the entire Nected stack on Microsoft Azure using Terraform. This method provisions networking, AKS, managed PostgreSQL, Redis, Elasticsearch, DNS records, SSL, and all runtime services through versioned, declarative infrastructure code.
Each method includes step-by-step instructions, value file configurations, and service validation procedures.
Continue Installation:
Docker Compose
Deploy Nected as a single container using Docker. Ideal for local testing, development, and small-scale use cases.
Kubernetes
Deploy Nected on Kubernetes for a production-grade setup with automatic scaling, load balancing, and high availability.
Last updated