platform>docssolutionspricingcontact

Platform in five minutes

A fast mental model — who talks to whom, and which commands touch which layer.

Actors

  • You — CLI or browser.
  • API — Source of truth for projects, deployments, tasks, env (REST).
  • Scheduler — Decides which node runs what; talks HTTP to agents (register, heartbeat, pushed actions).
  • Agent — Starts workloads, reports health, receives task actions from the scheduler over HTTP.
  • Registry — Stores artifacts the deploy path references.
  • Proxy — HTTP front door; reads routing rows in Postgres and forwards to live task addresses.

One happy path

  1. zectre login — Identity on the control plane (via catalog JWT or legacy).
  2. zectre projects add — Creates platform state + local .zectre/ link.
  3. zectre deploy — Build/upload (per manifest and platform services) produces or references an artifact; the scheduler places tasks on agents; the API updates routes and deployment records the proxy consults on each request.
  4. Dashboard — Watch rollout, task health, and logs from the UI.

When things go wrong

  • 502 / connection errors — Often agent address vs proxy reachability; see Local development.
  • Auth errors after login — Audience / JWKS mismatch; see Auth & catalog.
  • CI deploys stall — Non-interactive shells need explicit link and cluster env; see Linking & projects.

Drill deeper