# Evallot — Sovereign full-custom hosting — traditional, git-connected, AI Site Studio (coming).

Evallot is LayerBrick's hosting platform, built fully custom (no licensed panel). This is the Phase-1 CONTROL PLANE: sites (traditional or git-connected), plans (incl. Managed WordPress), TR/EU region choice at creation (KVKK residency), backups as records, and cross-brand DNS attachment — a site's records publish into the customer's NetDNS zone one-click as a protected managed set under the evallot owner tag. Hosting nodes provision through the Comphive broker in a later phase; every site is honestly pending_infra until real infrastructure exists. AI Site Studio (agentic site builder, Firecracker microVM isolation) is deferred by locked plan.

Authentication: LayerBrick SSO bearer token; the plans catalog is public.

## Endpoints

- GET /v1/plans [public] — Plan catalog (starter, growth, managed-wordpress, custom)
- GET /v1/sites?org_id= [member] — Sites (optional project_id filter)
- POST /v1/sites [admin] — Create site: {org_id, domain, kind: traditional|git, plan, region: tr|eu, git_repo?, project_id?}
- POST /v1/sites/{id}/dns-attach [technical] — Publish the site's records into its NetDNS zone as a protected managed set (owner_tag=evallot)
- GET /v1/sites/{id}/backups [member] — Backup records
- POST /v1/sites/{id}/backups [technical] — Request a manual backup (recorded now; real snapshots need the data plane)
Cross-brand facts an agent should know: one LayerBrick SSO session works on every brand (brands forward bearer tokens to Core's /v1/auth/me); each subdomain proxies Core same-origin at /core-api/*; organizations/wallets/AI-tokens/projects live on Core (albos.tr) — projects are Core-level workspaces resources link to via project_id, validated against Core's GET /v1/projects/{id}. Full platform spec: https://albos.tr/openapi.json and https://albos.tr/llms.txt. Every brand also mounts the uniform service-contract lifecycle surface at /v1/service-contract/*.