Engine Deployment Architecture
The Niksphere Engine is designed as a portable, high-performance runtime component that can be hosted across diverse operational environments. To meet varying enterprise security, compliance, and infrastructure requirements, Niksphere offers two primary deployment models:
- Self-Hosted (Customer-managed on private infrastructure, available as a Docker Container or Standalone Executable)
- Niksphere Cloud (Fully Managed) (SaaS / Managed platform operated directly by Niksphere)
1. Self-Hosted Deployment
In the Self-Hosted deployment model, the customer operates and manages the Niksphere Engine on their own infrastructure—whether in local on-premise data centers, edge environments, or private cloud VPCs. Self-hosted deployments provide maximum control over network perimeters, data residency, and system administration.
Niksphere provides two distribution options for self-hosted environments:
1.1 Docker Container
The Docker Container packaging delivers the Niksphere Engine as an immutable, multi-architecture container image hosted on the official GitHub Container Registry (ghcr.io).
Key Characteristics
- Multi-Architecture Support: Published as a unified OCI Multi-Arch image index supporting both
linux/amd64(x86_64) andlinux/arm64(Apple Silicon, AWS Graviton, ARM64 servers) natively without emulation overhead. - Minimal Attack Surface: Built on top of a lightweight Alpine Linux base with minimal runtime footprint.
- Immutable & Reproducible: Guarantees strict environment parity between local development, staging, and production environments.
- Orchestration Friendly: Native compatibility with Docker Compose, Kubernetes, HashiCorp Nomad, or cloud container services (AWS ECS, Azure Container Apps).
- Flexible Infrastructure: Host Self-Hosted in local data centers or within private cloud VPCs.
Image Specifications
- Supported Platforms:
linux/amd64,linux/arm64 - Base Image:
alpine:latest - Default Exposed Port:
8080/tcp(HTTP & WebSocket API) - Default Command:
./niksphere-engine run
Best Suited For
- DevOps-driven organizations utilizing modern container orchestration (Kubernetes / Docker Compose).
- Enterprise environments requiring isolated network perimeters and custom CI/CD pipelines.
NOTE
Official Docker images are available via release channel tags:
- Stable Channel:
ghcr.io/niksphere/niksphere-engine:latest - Insider Channel:
ghcr.io/niksphere/niksphere-engine:insider
1.2 Standalone Executable
The Standalone Executable packaging delivers the Niksphere Engine as a single, native binary file (.exe on Windows, ELF on Linux, Mach-O on macOS).
Key Characteristics
- Zero External Runtime Dependencies: Static binary compiled with no requirement for Java, Node.js, or external interpreters.
- Native OS Service Integration: Can run directly via command line or register as a native system service (Windows Service / systemd).
- Air-Gapped & Legacy Environment Support: Operates seamlessly in isolated, air-gapped corporate networks without internet access or container runtimes.
Best Suited For
- Self-Hosted enterprise servers where containerization (Docker) is unavailable or restricted.
- Edge deployments, local development workstations, and classic Windows/Linux server administration.
TIP
Download platform packages directly from the official portal:
👉 Niksphere Downloads & Installation
2. Niksphere Cloud (Fully Managed)
In the Niksphere Cloud (Fully Managed) deployment model, the Niksphere Engine is hosted and operated directly by Niksphere within a fully managed multi-tenant or dedicated cloud infrastructure.
Key Characteristics
- Zero Infrastructure Management: Automated provisioning, patching, OS updates, and database maintenance.
- High Availability & Auto-Scaling: Built-in multi-region redundancy and automatic scale-out capabilities.
- Integrated Identity & Storage: Pre-configured identity management (IDP Broker) and managed PostgreSQL storage.
Best Suited For
- Organizations seeking minimum operational overhead and fast time-to-market.
- Applications with standard enterprise compliance requirements.
TIP
To provision and manage Cloud Niksphere Engine instances, log in to the central portal:
👉 Niksphere Cloud Portal
Deployment Models Comparison Matrix
| Feature / Criteria | Niksphere Cloud (Fully Managed) | Self-Hosted (Docker Container) | Self-Hosted (Standalone Executable) |
|---|---|---|---|
| Primary Deployment Model | Cloud (Fully Managed) | Self-Hosted | Self-Hosted |
| Distribution Format | Managed SaaS Instance | OCI Container Image (ghcr.io) | Native Binary (.exe, ELF, Mach-O) |
| Supported Architectures | Managed (Cloud) | Multi-Arch (linux/amd64, linux/arm64) | Cross-Platform (Windows, Linux, macOS) |
| Hosting Environment | Niksphere Cloud (Fully Managed) | Self-Hosted (Docker / Private Cloud) | Self-Hosted (Native Binary / Local Server) |
| Maintenance & Patching | Automatic (Niksphere) | Customer / DevOps | Customer / System Admin |
| Container Engine Required | No | Yes (Docker / K8s) | No |
| Air-Gapped Operation | No | Yes | Yes |
| Native OS Service (systemd/SCM) | N/A | Container Daemon | Native |
| Database Options | Managed PostgreSQL | PostgreSQL / SQLite | PostgreSQL / Embedded SQLite |
Related Documentation
- Engine Installation & Setup Guide — Step-by-step guide to installing and running the Engine locally.
- Engine Configuration Reference — Complete list of
NIKSPHERE_ENGINE_*environment variables.