Fundraising Fox

Architect

8 known investors

Architect provides live migration and hibernation technology for stateful Kubernetes pods running on spot instances, enabling cost reduction of up to 90% compared to on-demand pricing without dropping connections or losing data. The platform targets cloud infrastructure teams running Kubernetes on AWS EKS and similar environments.

Also known as Architect Β· architect.io

Investors Β· 8

Company profile

researched Aug 2026

Architect (architect.io) offers software that lets stateful Kubernetes workloads run on cloud spot instances. When a spot instance is about to be reclaimed, Architect checkpoints the pod's full running state β€” memory contents, open sockets and in-flight work β€” and restores it on a fresh spot node, so the workload resumes where it left off. The company's site states that migration takes roughly 10 seconds, with no dropped connections and no data loss, and that stateful workloads that previously required on-demand or reserved instances can run on spot at claimed savings of 2-3x, or up to 90% cheaper than on-demand.

The product targets workload types the company describes as the largest on-demand line items on cloud bills: session stores, message brokers, in-memory databases and AI agent memory. A demonstration on the site shows a single Valkey instance with no persistence and no replicas surviving a node drain that simulates a spot interruption, with session data intact after the pod is rescheduled on another node. The same checkpoint/restore mechanism also supports in-place hibernation of idle pods: the pod remains scheduled and registered with the Kubernetes API, attached to its Services with PVCs still mounted, while consuming no compute, and wakes in under 50 ms with no image pull, init or JVM warmup. Architect states this scale-to-zero behavior runs alongside the Horizontal Pod Autoscaler and increases node packing density.

Integration is described as configuration-only, with no application code changes: users add pod annotations under the architect.loopholelabs.io namespace (specifying managed containers, scale-down durations and network monitoring) and set the pod's runtimeClassName to runc-architect. Stated requirements are Kubernetes 1.33 or later, EKS on AL2023, and at least two nodes.

Business model

Architect distributes software installed into a customer's own Kubernetes cluster; the site directs prospects to try it in their cluster and read documentation. The sources do not state pricing or contracting terms.

Traction

The only traction evidence in the sources is a self-published demonstration of a Valkey pod surviving a simulated spot reclamation. No customer names, deployment counts or revenue figures are disclosed.

Latest developments

The website documents current product requirements of Kubernetes 1.33+, EKS with AL2023, and a minimum of two nodes, and describes both live migration across spot nodes and in-place hibernation for scale-to-zero.

β–ΈFull profile β€” market position, technology, go-to-market, geography, history, risks & controversies

Market position

Architect positions itself around a specific gap in spot-instance economics: stateless workloads can already tolerate spot reclamation, while stateful workloads are kept on on-demand or reserved instances because in-memory state and connections are lost on eviction. The available sources do not name competitors or provide market share information.

Stated differentiators are preservation of in-memory data, open connections, queued messages and in-flight transactions across spot reclamation events; no application code changes; and sub-50 ms wake-from-hibernation without cold-start penalties such as image pulls, init containers or JVM warmup.

Technology

The core technology is checkpoint/restore of running containers: Architect captures memory, open network sockets and in-flight work before a spot node is reclaimed and restores the state on a new node, migrating open connections rather than dropping them. It is delivered through a custom container runtime class (runc-architect) plus pod annotations, and the same mechanism powers in-place hibernation of idle pods that preserves API registration, Service attachment and mounted PVCs.

Go-to-market

Self-serve, developer-oriented motion: the website offers a quick start for EKS clusters, public documentation, and a low-friction integration requiring only annotations and a runtime class rather than application changes.

Teams running stateful workloads on Kubernetes in AWS EKS clusters β€” including session stores, message brokers, in-memory databases such as Valkey, Postgres, ClickHouse and AI agent memory β€” that currently pay on-demand or reserved pricing for stability.

Geography

Not stated in the sources; the product is documented for AWS EKS clusters.

History

The sources do not provide founding date, funding history or corporate milestones for architect.io. Pod annotations and a terminal label on the site reference "loopholelabs" / architect.loopholelabs.io, indicating the product's namespace, but the sources do not further explain the relationship.

Risks & controversies

Performance figures (up to 90% savings, ~10-second migration, sub-50 ms wake, zero data loss) come solely from the company's own website and are not independently verified in the sources. The product's stated requirements are narrow β€” Kubernetes 1.33 or later on EKS with AL2023 β€” which limits applicable environments. No funding, team, customer or revenue information is available in the sources reviewed.

Compiled by commissioned research from 8 cited public sources β€” announcements, filings, and press listed under research sources below.

Key figures

latest reported
Cost of stateful workloads on spot vs. on-demand (claimed)Jan 20252-3x cheaper
Cost reduction vs. on-demand instances (claimed, up to)Jan 202590%
Hibernated pod wake time (claimed)Jan 2025under 50 ms
Live migration time (claimed)Jan 2025~10 seconds

Company-reported or press-reported figures, each dated to when it was claimed β€” not independently audited.

In the news

β–ΈResearch sources Β· 8

primary sources listed

8 public sources were cited for this profile; the first-party ones are listed here.

Frequently asked questions

What does Architect do?
Architect live-migrates and hibernates stateful Kubernetes pods so they can run on spot instances without data loss.
Who are Architect's investors?
Architect's investors include Comcast Ventures, Next Coast Ventures, Coinbase Ventures, Galaxy Ventures, Kindred Ventures, Strobe Ventures, Third Kind Venture Capital, VanEck.