Lumic Control Center
v2 pre-alpha

Lumic Control Center documentation

Install Lumic Control Center, connect MCP, open the UI, then let Lumic manage the server.

Lumic Control Center (Lumic) is a host-native Linux server operating layer available at lumic.cc. Its core workflow has three steps.

1. Install Lumic

ssh root@server 'curl -fsSL https://lumic.cc/install.sh | sh'

A fresh VPS becomes an autonomous Lumic node with the daemon, CLI, management surface and structured host model. The installer is published directly at https://lumic.cc/install.sh from the repository’s canonical root install.sh.

2. Connect MCP

lumic mcp setup

Lumic exposes that individual node to Codex, Claude and other MCP clients through structured operations rather than making unrestricted SSH the normal agent interface. Multiple VPS nodes remain independent; no Lumic relay or central cloud account is required.

Pre-alpha: the MCP setup command and remote transport are part of the v2 public contract and are being implemented during the initial roadmap.

3. Open the UI

lumic ui

Use the clean Rust management UI when you want visibility or direct control. CLI, UI and MCP must operate over the same capability model.

Pre-alpha: the management UI follows the core/MCP foundation and is not yet complete.

Those three actions define Lumic. The growing collection of server capabilities is deliberately secondary: packages, runtimes, PHP extensions, Git hosting, databases, Redis, TLS, deployments, workers, events, diagnostics, notifications, webhooks and multi-node infrastructure should increasingly feel like things Lumic simply already knows how to do.

Describe the application once

Application repositories can include an optional lumic.yaml file. It records the useful production intent that otherwise has to be explained repeatedly to coding agents: runtime, services, build commands, web process, workers, scheduled jobs, domains, secrets, health checks and deployment hooks.

The file is intentionally not a strict infrastructure language. Lumic and the coding agent should combine it with repository evidence and target-node state, fill in safe obvious details, then show a plan before material changes.

A typical request can therefore be short:

Read lumic.yaml, inspect this repository and prepare this Lumic node for production. Fill in safe obvious details from the repository, show the infrastructure plan before material changes, deploy the application and verify its health.

Give Codex a complete VPS task

After MCP is connected, the ideal Lumic workflow looks like this:

Inspect this Lumic node and the current repository. Prepare the VPS as a production environment for this application. Detect the required runtime, system packages, extensions and backing services. Install only what is needed, configure the web server, database, cache, TLS, firewall, workers and scheduled jobs where applicable, and create a zero-downtime Git deployment from the repository. Use Lumic plans before material changes, keep the host secure, verify the deployment with health checks, and report exactly what was configured. Do not use unrestricted shell access when a Lumic capability exists.

The coding agent performs the reasoning. Lumic provides trustworthy host status, safe operations, plans, policy and auditability.

Common outcomes without infrastructure frameworks

A Laravel project should be able to resolve into PHP, the required extensions, Composer, Nginx, PostgreSQL or MariaDB, Redis when needed, TLS, environment configuration, workers/Horizon, the scheduler, Git deployment and zero-downtime releases.

A React or Node project should be able to resolve into its actual Node/build requirements, environment variables, static or server-rendered deployment mode, Nginx routing, TLS, Git deployment, health checks and zero-downtime activation where applicable — giving a VPS a Render/Vercel-like application workflow without handing control of the infrastructure to a hosted platform.

The same model will cover Python applications, static sites, APIs, workers and custom services as their integrations become available.

Documentation status: Lumic v2 is pre-alpha. These pages describe both the implemented foundation and the intended public contract. Each capability page must be updated in the same change that makes the capability real. Documentation must never silently present planned behavior as already shipped.

Lumic manages Linux directly. Docker is supported as a workload feature, not used as the product’s core abstraction.

STARTIntroductionWhat Lumic Control Center is, what it replaces, and the rules that keep it simple.STARTInstallationFrom a fresh VPS to a Lumic Control Center node.SERVERServer managementThe host is Lumic's primary abstraction: OS, packages, services, users, network, storage and diagnostics.APPLICATIONSApplicationsApplications own runtime, Git, environment, web routing, workers, jobs, TLS and deployments.APPLICATIONSlumic.yamlDescribe an application's runtime, services and deployment needs once so Lumic and coding agents can prepare the server without rediscovering the stack every time.SERVICESManaged servicesInstall and operate server-side infrastructure without turning every package into a bespoke subsystem.APPLICATIONSDeploymentsGit-backed releases, health checks, activation and rollback with zero downtime where the runtime allows it.AGENTSMCPStructured infrastructure capabilities for Codex, Claude and other agent clients.AUTOMATIONEvents & automationLumic actively observes server state, records events and can notify or run constrained remediation.SECURITYSecurity modelRoot-level infrastructure management requires explicit policy, safe native execution and auditable mutations.REFERENCECLI referenceThe human console over the same typed capabilities used by UI and MCP.REFERENCEConfigurationMachine, application and infrastructure intent should be exportable and reproducible.RELEASESNightly channelEarly Lumic development ships continuous gated improvements while stable stays conservative.DEVELOPMENTDevelopment & documentationHow contributors and coding agents keep Lumic extensible and the docs permanently trustworthy.