>docsplaygroundgithubdeploy

Zectre Platform

Architecture and services of the Zectre Platform.

The Zectre Platform is a Nomad-inspired orchestration layer for Tish native binaries and Docker images (on nodes that have container support enabled). Details also live on zectre.

Architecture

Clients (zectre, Web UI)
    ↓
Control Plane: zectre-api, zectre-scheduler, zectre-registry
    ↓
Workers: zectre-agent (one or more nodes)
    ↓
Proxy: zectre-proxy (ingress / load balancing)

Services

ServiceRole
zectre-apiREST API gateway (apps, auth, deployments, builds, etc.)
zectre-schedulerJob scheduling, allocation, deployment orchestration
zectre-agentRuns and supervises Tish binaries and, when enabled, Docker containers
zectre-proxyReverse proxy, dynamic routing, cold start handling
zectre-registryArtifact storage for compiled binaries
zectre-buildBuilds Tish source on the platform

Quick start (local stack)

In the zectre-platform repo:

just setup
just run-all

Custom domains

You can map your own domains (e.g. api.example.com) to an application’s latest deployment for a given environment.

  1. Dashboard: Open your app → Domains → Add custom domain. Enter the domain and environment (e.g. production).

  2. API: POST /api/v1/apps/{id}/custom-domains with body { "domain": "api.example.com", "environment": "production" }.

  3. DNS: Point the hostname (A or CNAME) at the platform proxy. Routing uses the Host header.

Default app URLs use the platform’s domain pattern (e.g. myapp-default.<platform-domain> in development); custom domains are additional.

See also

Improve this documentation