loopholelabs.io valid

Loophole Labs

Loophole Labs builds systems infrastructure. Two products: Architect, for running Kubernetes workloads on spot with live migration and instant hibernation, and AGX, an agent sandbox platform.

Their llms.txt

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

# Loophole Labs

> Loophole Labs builds systems infrastructure. Two products: Architect, for running Kubernetes workloads on spot with live migration and instant hibernation, and AGX, an agent sandbox platform.

Loophole Labs is a systems infrastructure company. It builds two products:

- Architect (https://architect.io): A Kubernetes availability platform. Live-migrates running workloads across nodes, zones, and clouds before spot instances disappear, with zero downtime and no code changes. Idle pods hibernate (scale-to-zero without deletion) 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.
- AGX (https://agx.so): An agent sandbox platform. Runs untrusted agent code safely, integrates with third-party systems, and forks a running machine mid-task in milliseconds, built on a high-performance in-house hypervisor.

This site (loopholelabs.io) hosts the company pages and the engineering blog. Every blog post is also available as raw Markdown: append `.md` to its URL, or request it with an `Accept: text/markdown` header. Architect's documentation and changelog live on https://architect.io — see https://architect.io/llms.txt for that index.

## Blog

- [AI Took My Coding. What's Left For Me?](https://loopholelabs.io/blog/ai-took-my-coding-whats-left-for-me.md): When the thing you got good at stops being scarce, the first reaction is to assume you're out of a job. Here's why AI codegen took the typing and left the part that was always the real work: choosing the target and knowing when you've hit it.
- [The Stateful Spot Instance](https://loopholelabs.io/blog/stateful-spot.md): We put Valkey on an EKS spot instance without persistence. It got reclaimed. Architect moved the running container to another host with all its in-memory data intact.
- [Scale Kubernetes Pods to Zero, Without Cold Starts](https://loopholelabs.io/blog/scale-to-zero.md): Eliminating cold starts while scaling Kubernetes pods to zero has long been incredibly complex, Architect makes it easy.
- [The Math Changed: Rewriting Stale Open Source In The AI Era](https://loopholelabs.io/blog/rewriting-oss-in-the-ai-era.md): Rewriting an established open source project used to take years. With AI, that's no longer true. Here's why we're rewriting CRIU in Zig for our own use, what makes infrastructure projects go stale in the first place, and why the rebuild-vs-contribute math might be worth a second look.
- [Ollama Doesn't Know Its GPU Is on Another Machine](https://loopholelabs.io/blog/ollama-remote-gpu.md): No GPU. No CUDA drivers. No code changes. We ran large language models inside a container with zero GPU access by intercepting CUDA calls at the loader level and forwarding them to a remote DGX Spark. Ollama never knew.
- [An eBPF Loophole: Using XDP for Egress Traffic](https://loopholelabs.io/blog/xdp-for-egress-traffi
…

Related sites

Other listed sites in Infrastructure. See the whole category →

Machine-readable: GET /v1/resolve?q=loopholelabs.io · GET /v1/domain/loopholelabs.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 loopholelabs.io:
1. POST https://agentwebmap.com/v1/sites/loopholelabs.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://loopholelabs.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/loopholelabs.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/loopholelabs.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.