Project Overview and Ingress
Project Overview and Ingress
Section titled “Project Overview and Ingress”The Project Overview tab (◉) is the whole project at a glance, separate from any single service’s logs. Open it from the sidebar’s overview entry. It has four sub-tabs.
Runtime Status
Section titled “Runtime Status”A matrix of every service in the project: running state, resource usage, and a detail pane for the selected service (its deployments, nodes, and health). This is the fastest answer to “what is up right now.”
Pipelines
Section titled “Pipelines”The deployment pipelines for the project, with run history. From here you can run a pipeline and open its Run Console — the run logs, filterable by step and host, with failed steps called out (step · host · exit code) and a jump to the logs.
Config
Section titled “Config”The project and service configuration: AI guidance, debug credentials, and the per-service settings. Editing a service opens the service config editor — language runtime, entrypoint, startup / readiness, debug launch, and log source.
Config writes go through preview → apply, and real writes wait for approval when policy requires it. See Approval model.
Ingress
Section titled “Ingress”The ingress tab models how public traffic reaches your services. It is a three-stage flow:
- Public entry — DNS points at the reverse-proxy nodes.
- Reverse proxy — nginx (or another provider) on the selected proxy nodes.
- Upstreams — the backend services, chosen from hosts or imported from a pipeline environment.
DNS record values are generated from the public IPs of the selected proxy nodes. You can enable HTTPS and attach a certificate. Existing ingress entries are listed and editable.
Humans still own ingress, SSL, and DNS — the agent prepares config and evidence, you confirm the network boundary. This matches Configure tier 3: team deployment.
- Node Center and remote hosts — the hosts your upstreams run on.
- Runtime and debug workbench — start and debug services.