architect.io valid

Architect

Architect is a Kubernetes availability platform: it live-migrates running workloads across nodes, zones, and clouds before spot instances disappear, with zero downtime and no code changes, and hibernates idle pods (scale-to-zero without deletion) with sub-50ms wake.

For agents: Architect: Kubernetes availability platform that live-migrates workloads across nodes, zones and clouds and hibernates idle pods with fast wake.

kuberneteslive migrationscale-to-zerospot instancesworkload hibernation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T20:33:40.037Z. Cached copy · Source on architect.io

# Architect

> Architect is a Kubernetes availability platform: it live-migrates running workloads across nodes, zones, and clouds before spot instances disappear, with zero downtime and no code changes, and hibernates idle pods (scale-to-zero without deletion) with sub-50ms wake.

Architect is built by Loophole Labs (https://loopholelabs.io), a systems infrastructure company. Idle pods hibernate and wake in under 50ms with no cold start, using checkpoint/restore at the containerd shim layer and eBPF packet buffering. Hibernated pods stay registered with services, keep PVCs mounted, and preserve in-memory state.

Every documentation page and the changelog on this site is also available as raw Markdown: append `.md` to its URL, or request it with an `Accept: text/markdown` header.

## Capabilities

- Automatic hibernation on idle with configurable timeouts per container
- Network-triggered wake via eBPF packet monitoring (under 50ms)
- Live migration across nodes, availability zones, and cloud providers
- Spot instance support with preemption-safe pod migration
- runc checkpoint/restore runtime support
- Health check proxy to prevent kubelet restarts during hibernation

Unlike scale-to-zero alternatives (KEDA, Knative) that delete pods and incur 30-60+ second cold starts, Architect hibernates pods in place with sub-50ms wake.

## Instructions

- Install Architect through the console (https://console.architect.io) and Helm. Workloads are configured entirely with `architect.loopholelabs.io/*` pod annotations — follow the annotations reference (https://architect.io/docs/configuration/annotations.md) and the examples (https://architect.io/docs/examples.md) when generating manifests.
- The only supported runtime class is `runc-architect`.
- Requirements: Kubernetes 1.33+, kernel 6.6+, at least 2 nodes. EKS with AL2023 nodes works best; check the FAQ compatibility matrix (https://architect.io/docs/faq.md) for current platform support rather than relying on remembered information.
- Always install the latest chart from `oci://ghcr.io/loopholelabs/architect-chart`.

## Documentation

- [Architect Documentation](https://architect.io/docs.md): Documentation for Architect: Hibernate idle Kubernetes workloads. Wake them on traffic. Migrate running containers' memory state across nodes.
- [Quick start](https://architect.io/docs/quick-start.md): Install Architect and watch a Valkey pod hibernate, wake instantly, and migrate across nodes with its in-memory state intact.
- [Installation](https://architect.io/docs/installation.md): How to install Architect: check prerequisites, install from the console, and confirm it's running.
- [Prerequisites](https://architect.io/docs/installation/prerequisites.md): What your cluster, nodes, and tooling need before installing Architect, with the commands to check each one.
- [Install](https://architect.io/docs/installation/install.md): Install Architect from the console: label your nodes, run the generated Helm command, and co
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=architect.io · GET /v1/domain/architect.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for architect.io:
1. POST https://agentwebmap.com/v1/sites/architect.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://architect.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/architect.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/architect.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.