Category: verifiable compute infrastructure / confidential-compute network / TEE-and-ZK coprocessor platform / serverless and CVM control plane
Summary: Marlin is best understood as a broad confidential-compute and verifiable-execution platform rather than as only an “AI coprocessor” brand. Its current homepage emphasizes scalable coprocessors for decentralized compute, while the official docs and first-party monorepo show a much wider operating surface: Oyster confidential VMs, Oyster Serverless, attestation and verifier services, reproducible-build and networking primitives, Nautilus-style key-management components, operator control planes, onchain contracts and indexers, multi-language SDKs, and adjacent product surfaces such as Kalypso and Relay. That combination makes Marlin look like a compute-control-plane stack for secure offchain execution, not just a single protocol or narrow TEE network.
What it does:
Positions Marlin as a verifiable computing protocol using TEE- and ZK-based coprocessors to delegate complex workloads over decentralized infrastructure
Operates Oyster as a confidential-VM environment for running privacy-preserving applications in hardware-backed enclaves
Offers Oyster Serverless so developers can execute secure functions on demand and pay only for execution time rather than managing dedicated instances
Exposes core concepts such as remote attestation, reproducible builds, secure networking, and key-management flows as first-class docs topics
Ships a large monorepo spanning contracts, indexers, attestation services, operator setup tooling, KMS components, enclave images, networking proxies, serverless gateways and executors, and Rust / TypeScript / Go SDKs
Supports both smart-contract-based and Web2 API-based request flows for secure execution, indicating a hybrid crypto-plus-offchain operating model rather than a purely onchain one
Maintains adjacent ecosystem and product surfaces including Oyster, Kalypso, Relay, and legacy / ecosystem-specific deployment references surfaced through its official site and docs
Key claims:
The homepage meta description says Marlin is a “verifiable computing protocol” featuring TEE- and ZK-based coprocessors for delegating workloads over a decentralized cloud
The homepage FAQ says Oyster is a Marlin sub-network that offers TEE-based coprocessors and allows nodes to be rented individually or used in a serverless pooled mode, with access through smart contracts and Web2 APIs
The homepage FAQ frames Oyster as fast, cheap, and secure relative to heavier cryptographic or blockchain-native approaches, and explicitly invites developers and infrastructure providers into a permissionless network model
The Build with Confidential VMs docs say Oyster’s CVM tooling is for secure, private computation in untrusted environments and foreground remote attestation, reproducible builds, networking, and KMS as core concepts
The Build with Serverless docs say users can execute functions without renting and managing instances directly, can pay only for execution time, and can submit requests through smart contracts or Web2 APIs, including periodic subscription flows
The oyster-monorepo README shows a deep operational stack with attestation servers and verifiers, contracts, indexers, operator control planes, quota monitoring, setup tooling, SDKs, serverless gateway/executor components, secret stores, and networking layers
The official site navigation and footer expose multiple first-party surfaces beyond the current homepage pitch, including Oyster, Kalypso, Relay, docs, research/forum links, hub/ecosystem pages, and GitHub
The combination of CVMs, serverless execution, KMS, operator tooling, and hybrid request paths makes Marlin better categorized as broader confidential-compute infrastructure than as a simple DePIN, AI, or enclave-hosting project
Whitepaper: No single current canonical Marlin whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, Oyster docs, and the first-party oyster-monorepo; see ../whitepapers/marlin-primary-sources-2026-04-30.md.