Used to confirm the current company framing: Eigen Labs as an AI research lab building coordination technologies in the PostAGI world, plus the live corporate site metadata and organization schema
Used to confirm that EigenCloud is publicly presented as An Eigen Labs Project, that the footer routes users into Eigen legal/policy links and careers, and that the broader product shell spans EigenCompute, EigenDA, AgentKit, docs, blog, GitHub, and support channels
Used to confirm the explicit EigenLabs Coordinator role and the note that mainnet alpha currently uses a single EigenLabs-run KMS node in Google Cloud Platform
Used to confirm that EigenCompute currently requires trust in a Single KMS operator (EigenLabs), that infrastructure security / TEE provisioning / KMS operations are listed as Platform/EigenLabs responsibility, and that EigenLabs can theoretically decrypt environment variables in mainnet alpha because it controls the KMS keys
Used to confirm the higher-level operator shell around agents.eigencloud.xyz, email sign-in, Starter/Pro/Enterprise plan selection, and USDC-funded compute-credit workflow
Used to confirm the umbrella product framing: EigenCloud as a unified platform vision bundling EigenDA, EigenCompute, AgentKit, and later first-party / partner offerings on one developer platform
Used to confirm that public implementation and docs stewardship remain tied to the Layr-Labs company repo surface rather than a clearly separate neutral operator layer
Key takeaways from primary sources
EigenCloud’s product docs already made the architecture legible, but this pass surfaced why the company/entity split materially improves the taxonomy: the current live trust path names EigenLabs directly at the coordinator and KMS layers.
The most important company-level fact is not generic branding. It is that the current EigenCompute mainnet-alpha path still depends on a company-run coordinator plus a single company-run KMS node.
The trust-model page is unusually explicit and therefore unusually useful: the docs do not merely imply operator trust; they say the platform currently requires trust in a single EigenLabs KMS operator and that EigenLabs remains responsible for infrastructure security, TEE provisioning, and KMS operation.
AgentKit extends that operator boundary beyond raw compute. Email sign-in, plan selection, compute-credit purchases, and hosted agent surfaces show how quickly a lower-level TEE stack turns into a company-shaped onboarding, billing, and distribution shell.
The EigenCloud marketing site keeps reinforcing that this is one integrated company shell, not just a set of modular primitives: products, docs, careers, legal links, GitHub, blog, and support all roll up into the same Eigen Labs perimeter.
Specific source signals worth retaining
eigencompute-architecture.md is the best source for the exact EigenLabs Coordinator wording and for the mainnet-alpha single-KMS note.
security-trust-model.md is the best source for current operator trust assumptions and for the explicit line that EigenLabs can theoretically decrypt environment variables in the present architecture.
agentkit-overview.mdx is the best source for where the company shell becomes visible to end users: hosted builder, plan tiers, and credit-funded deployment.
eigencloud.xyz is the best source for the public company/product boundary because the footer literally says An Eigen Labs Project and routes into Eigen Labs careers and legal links.
eigenlabs.org is the best source for how the company currently describes itself beyond EigenCloud: a broader coordination-technology and AI lab.
Why this source capture matters
It justifies a separate companies/eigen-labs.md note rather than leaving all of the current operator trust buried inside the projects/eigencloud.md architecture summary.
It clarifies that the present control surface is not only TEE + attestation; it is also a named company that coordinates deployment, runs the KMS, owns the docs/legal shell, and packages the easiest agent-compute workflow.
That distinction will stay analytically useful even if EigenCloud decentralizes further later, because the corpus can now cleanly separate current operator reality from the product’s future-facing verifiability story.