Register the resource
Store a customer-safe server reference, purpose, ownership, and project relationship in the public application.
In development
Infrastructure
Understand customer-owned infrastructure without turning the browser into a control plane.
DenOps is building a project-centered operating view where server references, Link Kits, health evidence, tasks, approvals, and outcomes stay connected without exposing private credentials or unrestricted access.
Projects own the operating context
Keep infrastructure attached to the work it supports.
The intended workflow treats a server as a customer-owned project resource, not an invitation for an agent or browser session to gain broad authority.
Bound the connection
Use Link Kit as a narrowly controlled per-server component with explicit capabilities and no reusable credential in browser code.
Review safe evidence
Present useful health, task, and change evidence without leaking private addresses, credentials, internal paths, or unrestricted traces.
Decide exact actions
Require explicit Approve or Reject controls for sensitive work and preserve the decision with the project record.
Link Kit is a bounded connection
Connection does not mean control.
A Link Kit is intended to connect one customer-owned server through a reviewed, narrowly scoped path. It is not browser shell access, a shared administrator credential, or a route around project permissions.
Projects remain primary: server references, requested work, approvals, deployments, activity, and customer-safe outcomes belong with the project that owns the objective.
See the controlled release path →Bounded by design
Useful visibility with narrow authority.
These principles describe the infrastructure experience being built; they do not claim connected monitoring or execution is available today.
No direct browser-to-server access
The browser never receives private service credentials, shell access, or a direct route to Link Kits, servers, or private Core.
Least capability
Every request stays limited to the exact project resource and customer-granted capability needed for the task.
Safe evidence
Customer views show bounded status and outcomes while private topology, secrets, hidden reasoning, and internal traces stay private.
Durable authority
A chat reply is never permission. Sensitive actions require separate, explicit Approve or Reject controls tied to the exact request.
In development
Connected infrastructure actions are not yet available.
The public application does not currently monitor or operate customer servers through private DenOps Core or Link Kits. Those capabilities remain disabled until the customer-safe gateway contract, scoped authorization, enrollment, approval validation, and response protections are accepted and tested.
Planning an infrastructure workflow?
Contact DenOps →Tell us where your team loses operating context.
We can discuss the workflow while staying direct about what DenOps supports today and what is still being built.