Deployment

AURA supports flexible deployment options to match your infrastructure needs and compliance requirements.

Deployment Options #

Cloud SaaS #

Cloud SaaS is the recommended deployment for most customers. IBG Technology manages the entire infrastructure, so your team can focus on property operations instead of server maintenance.

Key Features

• Multi-region availability — deploy closest to your tenants for lowest latency
• Global CDN — static assets and dashboards served from edge nodes worldwide
• Managed database — PostgreSQL and TimescaleDB provisioned and maintained automatically
• Automatic scaling — capacity adjusts dynamically based on load

Available Regions

Quick Setup

Getting started with Cloud SaaS takes minutes: sign up at aura-pm.io, create your organization, and configure your property portfolio. No servers, no Docker, no DevOps required.

On-Premise #

For organizations requiring full data control, AURA can be deployed entirely on your own infrastructure. On-premise deployments are containerized and ship as Docker images.

System Requirements

Docker Compose Setup

Use the following Docker Compose file to spin up the core AURA stack:

version: "3.9"
services:
  aura-api:
    image: ibgt/aura-api:latest
    ports: ["8080:8080"]
    environment:
      DB_HOST: postgres
      TIMESCALE_HOST: timescaledb
  postgres:
    image: postgres:16
    volumes: ["pgdata:/var/lib/postgresql/data"]
  timescaledb:
    image: timescale/timescaledb:latest-pg16
    volumes: ["tsdata:/var/lib/postgresql/data"]
volumes:
  pgdata:
  tsdata:

Hybrid #

The hybrid deployment model runs the core AURA platform in the IBG cloud while keeping IoT data and sensitive records on your local infrastructure.

Use Case

Hybrid is ideal for compliance-sensitive environments such as healthcare facilities, government-owned properties, and organizations with strict data residency requirements.

Architecture

The hybrid model uses an edge gateway that connects local sensors to a local TimescaleDB instance. Aggregated metadata is synced to the cloud for dashboards, analytics, and AI predictions, while raw sensor data never leaves your premises.

1. Local IoT sensors send data to the on-site AURA edge gateway
2. Edge gateway writes raw telemetry to the local TimescaleDB
3. Aggregated metrics and metadata sync to the IBG cloud on a configurable schedule
4. Cloud dashboards and AI models operate on aggregated data only
5. Full raw data remains under your physical and legal control

Scaling #

AURA uses Kubernetes-based horizontal scaling to handle growing portfolios. The platform auto-scales API pods based on CPU utilization using a Horizontal Pod Autoscaler (HPA).

HPA Configuration

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: aura-api-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: aura-api
  minReplicas: 3
  maxReplicas: 20
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 70

Performance Benchmarks

Monitoring #

AURA exposes built-in observability endpoints for health checks, metrics collection, and dashboard integration.

Health Endpoint

Check the platform status with a simple HTTP call:

GET /v1/health

{
  "status": "healthy",
  "version": "2.14.0",
  "uptime": "45d 12h 33m",
  "services": {
    "api": "ok",
    "postgres": "ok",
    "timescaledb": "ok",
    "redis": "ok",
    "mqtt": "ok"
  }
}

Prometheus Metrics

Metrics are exported on the /metrics endpoint in Prometheus format. Scrape this endpoint with your existing Prometheus instance to collect API latency, request rates, database connection pool stats, and IoT message throughput.

# Example Prometheus scrape config
scrape_configs:
  - job_name: "aura-api"
    metrics_path: "/metrics"
    static_configs:
      - targets: ["aura-api:8080"]
    scrape_interval: 15s

Grafana Dashboards

AURA ships with pre-built Grafana dashboard templates covering API performance, database health, IoT device connectivity, and tenant activity metrics. Import the JSON templates from the /monitoring/grafana/ directory in your deployment package.