RBAC-native
Resource visibility and available actions depend on the Kubernetes credentials and permissions you use. Review the access of each connected context.
Security and control
Platform tooling should respect the controls you already trust.
Lumen is designed around local Kubernetes credentials, existing RBAC, and a no-required-agent model for core IDE workflows. Future operator capabilities should be optional, explicit, and transparent.
Security principles
No required agent for Lumen
The desktop IDE can operate through local kubeconfig and Kubernetes APIs for core workflows.
BYOK AI
Configure a supported provider and review the context it receives. Provider credentials, resource content and logs require deliberate handling.
Transparent operator roadmap
Future in-cluster operator capabilities must document permissions, data flow, install behaviour, and uninstall behaviour.
Current and future modes
Separate Lumen’s local model from future fleet automation.
The desktop IDE connects through your existing Kubernetes access. Planned operator-backed capabilities would introduce a separate installation and permission model, to be reviewed when available.
- Today: local desktop IDE, kubeconfig, Kubernetes APIs, no required in-cluster agent.
- Future: optional operator for deeper fleet telemetry and automation.
- Enterprise: support for review, rollout planning, and compliance questions.
mode=lumen_desktop access=kubeconfig rbac=native
mode=future_operator install=optional permissions=documented
Evaluation checklist
Make the security review concrete.
What credentials will the workstation use?
Review kubeconfig, authentication plugins and role boundaries. Use least privilege and confirm permitted actions in a non-production context.
What data can an AI provider receive?
Inspect the selected provider, context collection and model configuration. Resource content and logs can be sensitive; your provider settings and policies define the boundary.
Does the site claim compliance certification?
No certification is asserted here. Contact us for product-specific information and the evidence your organisation needs for its review.
A clearer next step
Try Lumen in your own environment.
Choose a release, connect an existing Kubernetes context and work through an investigation your team knows well. Talk to us when you need help with rollout or enterprise adoption.