Platform overview
Zectre orchestrates compiled workloads across nodes — API, scheduler, registry, agents, and a dynamic proxy.
What Zectre is
Zectre is a control plane for running workloads on worker nodes — most commonly native binaries built with the Tish toolchain. When container support is enabled on an agent, the same platform can also run Docker-based process_type deployments (deploy.image in zectre.yaml).
You ship artifacts, the scheduler places tasks on nodes, and end-user traffic reaches workloads through zectre-proxy using routing data in the database.
Typical clients:
zectreCLI — authenticate, link projects, deploy, tail logs, manage env.- Web dashboard — visibility into clusters, nodes, deployments, applications, and tasks.
Core components
| Piece | Role |
|---|---|
| API | REST (HTTP/JSON) for projects, deployments, tasks, env, auth |
| Scheduler | Allocates tasks to nodes; controls agents over HTTP (register, heartbeat, pushed actions) |
| Registry | Stores build artifacts your deploys reference |
| Agent | Runs on each node; supervises processes (Tish binary or Docker, per config) |
| Proxy | HTTP ingress: resolves host → backend from deployments, routes, and related tables |
For every runnable binary, ports, and how they fit together, see Platform services. For the cluster REST API (zectre-api), see Zectre API. For a diagram-heavy walkthrough, see Architecture tour.
Web vs CLI
Use the dashboard when you want a visual map of the fleet: what is running where, deployment history, and operational context. Use the CLI when you are in a repo: zectre dev, zectre build, zectre deploy, env sync, and scripting.
Next: Dashboard or jump to CLI quick start.