Self-Hosted Plexicus
Plexicus can be deployed on any Kubernetes cluster using the official Helm chart (current release: 1.2.36), published as an OCI artifact to Google Artifact Registry. This section covers everything you need to install Plexicus on your own infrastructure — no support ticket required.
A self-hosted Plexicus deployment does not send telemetry, analytics, or feedback data outside your cluster. Features that depend on Plexicus' own commercial services (billing, marketplace listings, product analytics) are disabled in this mode. Only the integrations you configure (your GitHub, your AI provider, your SMTP server) talk to external systems — and only to the endpoints you specify.
Choose Your Path
Pick the guide that matches what you are trying to do:
🧪 I want to evaluate Plexicus locally
You want to spin up Plexicus on a small Ubuntu 24.04 server (cloud VM or on-premise), click around, and see if it solves your problem. No GitHub, GitLab, or Bitbucket app is needed to install: your first scan runs through the built-in Sandbox connector, and SCM connectors can be added at any time afterwards from the UI (Settings → Integrations / Settings → Source Control). One command installs everything — Kubernetes (k3s), TLS, secrets, the platform with bundled infrastructure, and an admin account. The guide shows the exact invocation (it points the installer at the three files from your delivery package). This is the path we validate end-to-end.
→ Local Evaluation (Self-Signed)
🏭 I'm deploying to a production Kubernetes cluster
You have a real cluster (GKE, EKS, AKS, on-premises, etc.), a domain you own, and you want a TLS-enabled installation that your team will use day-to-day. The guide installs MongoDB, Redis, MinIO, PostgreSQL, and Temporal as separate Helm releases for maximum control over versions, lifecycle, and tuning. Bundled subcharts are also available as an alternative — see the guide for details.
→ Self-Hosted Installation (Helm)
🔒 I'm deploying to an air-gapped or restricted environment
Your cluster has no public internet access, or you need to mirror images to an internal registry, or you have strict egress controls.
After Installation
Once the platform is running and reachable, you'll want to configure provider integrations: SCM (GitHub, GitLab, Bitbucket, Gitea), AI (OpenAI or Azure OpenAI), email (SMTP), and OAuth login providers.
Per-provider configuration guides are published incrementally as the chart stabilizes. The configuration index lists which guides are available today and what is coming next.
Getting Help
- Documentation gaps or issues: open an issue at github.com/plexicus/docs
- Chart bugs, feature requests, registry access, license keys, or anything that requires a real human: engineering@plexicus.ai