Zones and Nuclei

Zones

A Zone is a geographic region operated as a single unit. Each Zone has a primary datacenter, independent connectivity, and health metrics isolated from others.

• uk-wlv-1 — Wolverhampton, UK (active)
• de-ham-1 — Hamburg, DE (active)
• us-nyc-1 — New York, US (active)
• us-dfw-1 — Dallas, US (active)
• in-bom-1 — Mumbai, IN (active)
• cz-prg-1 — Prague, CZ (planned)
• ca-ywg-1 — Winnipeg, CA (planned)
• us-orl-1 — Orlando, US (planned)

States

• ativa — accepts placement of new workloads.
• planejada — under construction. No workloads.
• manutencao — scheduled window. Existing workloads keep running; new placement is diverted to other Zones.
• degradada — ongoing incident. For Projects with multi-zone or multi-region resilience, traffic is redirected to other Zones.
• fora — unavailable. Public status at tesserra.io/status.

Nuclei

Within each Zone, a Nucleus is the cluster or server that hosts resources. Today, Nuclei serve AI agents via Ollama. Compute and other resource types are gradually migrating to the same execution plane.

Relevant Nucleus fields:

• nome — human-readable identifier;
• url — authenticated internal endpoint;
• zona_id — relationship to the Zone;
• ativo and ultimo_ping — operational health;
• set of available Agents (AI models).

Placement

When a Compute is provisioned with replicas_min=N, replicas_max=M in a Project with resiliencia: multi-zona, the platform:

• lists Zones in ativa state;
• within each Zone, orders Nuclei by current load and ultimo_ping;
• distributes replicas across distinct Zones, respecting min and max limits;
• on Zone failure, autoscaling rebuilds capacity in remaining Zones.

On Pro+ plans you can restrict a Compute to a set of Zones (explicit placement). Restriction to specific Nuclei is supported only on Enterprise contracts.