Code & AI agent sandboxes: read the guide

OpenComputer

Open coreSandbox

The platform for long-running agents. Define an agent like a serverless function. Choose your model. We handle the runtime.

Homepage Docs Pricing Repository

Scanned 12 Oct 2026 · Schema v5 · features v21

From: $20/mo
Usage-based, one meter set for both layers: (1) model tokens passed through at provider API rates (zero with your own Codex subscription), (2) machine time billed per second while a session/sandbox runs. Plans are PREPAID usage credit with a 10× multiplier; running out drops you to PAYG rates.
Free tier: Not documented
$10 free credit to start (PAYG). No perpetual free tier.
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: —
No current hosted region inventory or selector found. Prior sandbox docs/examples are now 404 and not reused as residency evidence. Self-host placement is operator-controlled.
Capabilities: 15 / 61
20 partial · 26 fail · 0 not assessed
Agent readiness: 11/11 · 9/11
read · drive, pre-login surface

Advertised for

Managed TypeScript serverless AI agents with durable sessions · Scheduled/webhook/Slack/GitHub triggered agent tasks · BYO harness Linux sandboxes · Code execution and coding agents · Browser automation on a Linux machine

Built for

Developers, then technical

· CLI-first onboarding (`npm i -g @opencomputer/cli`, `opencomputer deploy`)
· code hero (agent.ts with useModel/useTool)
· vocabulary: KVM, microVMs, checkpoints, per-second billing

01 Pricing Usage-based, one meter set for both layers: (1) model tokens passed through at provider API rates (zero with your own Codex subscription), (2) machine time billed per second while a session/sandbox runs. Plans are PREPAID usage credit with a 10× multiplier; running out drops you to PAYG rates.

Tier	EntryPAYG	Pro	Max	TopEnterprise
Price	usage-based ($10 free credit)	$20/mo	$200/mo	Custom
Includes	Model calls at API rates, machine time per second, scale to zero when idle, no monthly commitment.	Prepaid: 'Your $20 becomes 10× the usage credit'; credit covers model calls and machine time; bring your Codex subscription so model calls cost nothing.	10× prepaid credit at scale — 'Enough to keep 10+ default machines running around the clock'.	Your own cloud or VPC, self-hosted connections, volume pricing and higher limits, SSO, audit log, priority support.

Free tier: $10 free credit to start (PAYG). No perpetual free tier.

per-second machine time by memory/vCPU tier (quoted per minute) + per-token model passthrough·Card required: unconfirmed·opencomputer.dev

Overages: When prepaid credit runs out, usage continues at the same PAYG rates. Additional persistent cross-sandbox disks are advertised as forthcoming; no current additional storage/egress charge found.

02 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Virtual machinehypervisor, or nothing at all

Persistence

unknown

Snapshots / forks

Advertised checkpoints/fork; hosted semantics unknown

Resources & limits

Storage

Hosted sandbox disk guarantees unknown; advertised max disk 8/16/32 GB by baseline size

Limits & quotas

Hosted implementation limits unknown; advertised baselines/burst sizes and disk maxima recorded

GPU

No GPU offering found on current public pages/docs; not a confirmed runtime prohibition.

Access

Deploy interface

clisdkapitemplate

SDK languages

TypeScript (@opencomputer/sdk 2.3.0; sandbox root and portable /agents client; @opencomputer/agent authoring) and Python (opencomputer-sdk 1.1.0 sandbox SDK). Agent authoring is TypeScript.

Network & secrets

Egress controls

Managed outbound connections constrain credentialed requests; general sandbox firewall unknown

Secrets

Managed agent connections use write-only origin/method/path-scoped secret injection, outside prompts/source/runtime; separately configurable runtime variables are encrypted at rest but visible to agent code/tools/processes. Bare-sandbox proxy placement/behaviour is unconfirmed because its docs return 404.

Bring your own cloud

Enterprise tier: 'Your own cloud or VPC, self-hosted connections'. Otherwise self-host the OSS core in your own AWS/Azure/GCP account.

Placement & use

Jurisdiction

unknown

Advertised workloads

Managed TypeScript serverless AI agents with durable sessionsScheduled/webhook/Slack/GitHub triggered agent tasksBYO harness Linux sandboxesCode execution and coding agentsBrowser automation on a Linux machine

03 Capabilities 15 pass · 20 partial · 26 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 1/11

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Partially supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Partially supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Partially supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Not supported

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Partially supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Not supported

Networking & delivery 0/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Partially supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Partially supported

Custom domainsBring-your-own domain via CNAME/DNS.

Partially supported

Public preview URLsShareable per-deploy / per-branch URLs.

Partially supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Partially supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Not supported

Email send / receiveSend and/or receive email from the workload.

Partially supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 4/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Not supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Supported

SSH accessDirect SSH into workloads.

Partially supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Supported

Git deployDeploy from a Git repo / push-to-deploy.

Partially supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 4/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Not supported

MCP clientActs as an MCP client / consumes MCP tools.

Supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Partially supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Supported

BYOK for LLMsBring-your-own LLM provider keys.

Partially supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Not supported

Data 1/4

First-party databasePlatform-provided managed database.

Supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 3/6

Scheduled tasksCron / scheduled job primitive.

Supported

Durable workflowsDurable execution / long-running workflow primitive.

Supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Partially supported

Organisation & security 2/9

Built-in authPlatform-provided authentication / IAM for workloads.

Partially supported

SSO / SAMLEnterprise single sign-on.

Partially supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Partially supported

SharingShare a running workload/resource via link (optionally gated).

Partially supported

BYOCRuns inside the customer's own cloud account.

Partially supported

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not supported

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

Proposed, not verified

Capabilities the scan saw but the registry does not track yet. A key is admitted only once two distinct products exhibit it. These are not scored.

Runtime vertical resize / automatic burstlive-resize
“Pick a baseline machine; it bursts to its peak size automatically under load and drops back when done. Burst time is billed at the peak rate.” opencomputer.dev
Managed agent harness / serverless agent deploymentsmanaged-agent-runtime
“OpenComputer is a managed runtime for agents defined as code.” docs.opencomputer.dev
Interruptible sandboxes (SDK option)spot-instances
“/** Create a Burst Sandbox. Disk is preserved across infrastructure restarts; processes may restart. */” github.com

04 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

11/11

8 full · 3 partial · 100% of applicable checks

llms.txt
Supported
“opencomputer.dev/llms.txt (9.6 KB) links docs, dashboard, GitHub, docs llms.txt, guides + blog as .md — substantive, though its product/pricing copy is stale (meta.scan_issues).”
llms-full.txt
Supported
“docs.opencomputer.dev/llms-full.txt: 280895 bytes, 38 current agent/agents-SDK pages, comprehensive for its current index. Previous sandbox docs disappeared; see scan_issues.”
robots.txt AI policy
Partially supported
“robots.txt: named Allow for Googlebot/Bingbot/Twitterbot/facebookexternalhit + 'User-agent: * Allow: /'; no AI UA named — silent default-allow.”
JSON-LD
Partially supported
“Homepage JSON-LD is a single minimal WebSite object.”
Sitemap
Supported
“Current /sitemap.xml contains 32 URLs; robots.txt points to it.”
Meta tags
Supported
“title + meta description + full OG + Twitter card present and descriptive.”
Markdown negotiation
Supported
“Current /agents/overview with Accept: text/markdown returns HTTP 200, content-type text/markdown; request headers and body retained.”
Content efficiency
Supported
“Current homepage readable text 6487 bytes / 69027 HTML bytes = 9.40% (scripts/styles excluded), above 5% full-credit threshold.”
Docs discoverable
Supported
“'Docs' in header nav, plain <a> links to docs.opencomputer.dev.”
Machine-readable pricing
Partially supported
“Current rendered homepage plans and sandbox machine table are parseable; apex llms.txt still publishes incompatible old tiers, so partial credit retained.”
No anti-bot wall
Supported
“No challenge on successfully fetched current landing, agent docs, privacy, blog or gh sources. Sandbox docs return true 404, not an anti-bot wall.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

9/11

6 full · 3 partial · 82% of applicable checks

Public API
Supported
“Current /agents/api documented management REST API; official sandbox SDK source exposes REST endpoints. Removed sandbox API pages are not used.”
OpenAPI spec
Not supported
“No linked public spec in current /agents/api docs; docs /openapi.json returns HTTP 404 (fetch-manifest).”
MCP server
Not supported
“Current agent docs describe consuming HTTPS MCP servers, not a product-management endpoint. Apex .well-known/mcp remains a homepage shell after foxcrawl retry; no documented alternative found.”
SDK packages
Supported
“Official TypeScript (@opencomputer/sdk) and Python (opencomputer-sdk) SDKs + @opencomputer/agent.”
Auth documented
Supported
“Current /agents/api: x-api-key authentication; organization keys and project-scoped session access documented.”
Self-serve credentials
Partially supported
“`oc login` / `opencomputer login` browser device flow ('give me the link to sign in') or dashboard keys — a human approves; no programmatic key issuance.”
Webhooks
Supported
“Current agent webhooks/event subscriptions documentation and SDK README: signed/retried/redeliverable sandbox lifecycle webhooks (Preview).”
CLI tool
Supported
“Current repository README documents TypeScript opencomputer CLI; skills/opencomputer/README.md documents sandbox oc CLI.”
Error model
Supported
“JSON error envelope `{ error: { code, message } }` with stable codes + status table.”
Rate limits documented
Partially supported
“429 'Too many requests; retry after Retry-After' documented; no numeric limits or rate-limit headers.”
Agent config files
Partially supported
“Current repository skill README: npx skills add diggerhq/opencomputer. One installable skill surface; apex AGENTS.md returns homepage shell.”

05 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 5

Claude Code Anthropic
Supported
“Works with Claude Code, Codex, Cursor, and 30+ other AI agents that support the [Agent Skills](https://agentskills.io) standard.”
Source github.com
`npx skills add diggerhq/opencomputer` installs a skill that drives the `oc` CLI; homepage also offers 'Copy the prompt for Claude Code'.
Codex CLI OpenAI
Supported
“Works with Claude Code, Codex, Cursor, and 30+ other AI agents that support the [Agent Skills](https://agentskills.io) standard.”
Source github.com
Homepage 'Copy the prompt for … Codex'. Separately, a Codex SUBSCRIPTION can be connected as the model account (BYOK) — that is model access, not the harness.
Cursor Anysphere
Supported
“Works with Claude Code, Codex, Cursor, and 30+ other AI agents that support the [Agent Skills](https://agentskills.io) standard.”
Source github.com
OpenCode opencode
Supported
“Works with Claude Code, Codex, Cursor, and 30+ other AI agents that support the [Agent Skills](https://agentskills.io) standard.”
Source github.com
Homepage onboarding prompt for driving the OpenComputer CLI from the coding agent.
OpenClaw Peter Steinberger
Supported
“Works with Claude Code, Codex, Cursor, and 30+ other AI agents that support the [Agent Skills](https://agentskills.io) standard.”
Source github.com
The vendor's own Clawputer SKU runs openclaw on OpenComputer long-lived compute (orchestrator kind).

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

06 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions —

Regions are not disclosed on the public surface.

No current hosted region inventory or selector found. Prior sandbox docs/examples are now 404 and not reused as residency evidence. Self-host placement is operator-controlled.

Legal

Privacy notice

07 Open source Apache-2.0 · fetched by machine, not quoted from marketing

Licence & repository

Licence: Apache-2.0OSI
Primary language: TypeScript
Stars: 563
Forks: 65
Created: 9 Dec 2025
Archived: No

Activity

Last commit: 12 Oct 2026
Latest release: v0.6.0.49 · 28 Sep 2026
Issues open / closed: 12 / 37 · 76% closed

217 GitHub releases; latest v0.6.0.49 on 2026-09-28, with release notes. Repository pushed 2026-10-12T19:58:26Z. TypeScript SDK 2.3.0 and Python SDK 1.1.0 version separately.

Fetched via gh on 12 Oct 2026.

Self-hosting

Methods: source-buildterraformcomposeother
You operate: postgresredisobject-storage

Operator path: provision KVM-capable Linux workers, cloud resources and baked images; run control plane/worker services with Postgres, Redis, S3-compatible storage and secrets. SELFHOSTING.md documents QEMU/KVM sandbox cells on Azure/AWS (GCP development path), not an end-to-end self-host recipe for the managed Serverless Agents layer. The repository also includes an AWS Lambda MicroVM backend with an 8-hour maximum lifetime; this is backend code, not evidence of which backend serves hosted accounts.

Documentation signals 7/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
Not supportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

08 Company & presence Facts only, not scored

Company

Headquarters: unknown
Founded: Digger GitHub org created 2020-09-15; opencomputer repo created 2025-12-09.
Team size: unknown
Hiring: unknown

Activity

Last release: v0.6.0.49 (2026-09-28); repo pushed 2026-10-12T19:58:26Z github.com
Last blog post: Public blog index reachable; no reliable newest-post timestamp established in current capture. Retained article: "What it takes to run an AI coworker on iMessage" (2026-05-22). opencomputer.dev

Presence 4

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from opencomputer.dev's unauthenticated pages, docs, pricing and repository on 12 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Sandbox products →