Namespace

HostedIaaS

The dev platform for the next 100 billion commits

Homepage Docs Pricing Repository

Scanned 12 Oct 2026 · Schema v5 · features v21

From: $100/mo
Plan tier + usage (unit-minutes compute + devbox-minutes + Docker builds + storage/cache GB); platform multipliers (Linux 1 / Windows 2 / macOS 10 / Linux-on-Apple-Silicon 7)
Free tier: Not documented
No card required.
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: —
Multi-region compute and all-plan regional preferences documented; region-exclusive workload residency is Enterprise, with globally replicated operational metadata. Devbox site selector/site-latency exposes live availability; iad appears as SDK default. Complete physical Devbox site inventory not enumerated on retained public pages; no CI region list is silently applied to Devboxes.
Capabilities: 27 / 61
4 partial · 25 fail · 0 not assessed
Agent readiness: 10/11 · 9/11
read · drive, pre-login surface

Advertised for

CI CD runners · GitHub actions · Docker builds · Devboxes · AI coding agents · Build caching · Compute/memory heavy tests

Built for

Developers, then technical

· Devbox focus: CLI/SSH/SDK, remote IDE development, agent sessions and MCP command/lifecycle control (https://namespace.so/devbox; /docs/reference/mcp/index.md).
· Separate CI/build coverage: GitHub Actions runners and Docker/Bazel caches (https://namespace.so/pricing.md).
· Usage units and Devbox-minute rates target engineering/platform buyers (https://namespace.so/pricing.md).

01 Pricing Plan tier + usage (unit-minutes compute + devbox-minutes + Docker builds + storage/cache GB); platform multipliers (Linux 1 / Windows 2 / macOS 10 / Linux-on-Apple-Silicon 7)

Tier	EntryDeveloper	Team	Business	TopEnterprise
Price	Pay as you go ($0 base)	$100/mo	$250/mo	custom

unit-minute (1 vCPU·2GB·min × platform multiplier); devbox-minute; per Docker build; per GB cache/storage·Card required: No·namespace.so

Overages: Per-shape unit-minute overage (Linux 1vCPU/2GB $0.0015/min → 32vCPU/512GB $0.384/min); macOS 10x, Windows 2x; Docker builds $10/1,000; storage/cache per GB

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

Devbox stops preserve persistent storage; deletion removes it. Ephemeral configuration supports stopped-retention policies. Stopping does not establish preservation of running processes.

Snapshots / forks

Automatic persistent-volume snapshots on shutdown; initialize volumes from_snapshot_id. Live VM memory restoration/forking not documented.

Resources & limits

Storage

Devboxes retain persistent block storage across stops (Devbox-specific disk price undisclosed). Shared platform also provides persistent-volume disk snapshots, cache volumes, artifact object storage and private registry; cache and artifact billing must not be substituted for Devbox persistent-disk pricing.

Limits & quotas

Devboxes: Linux S/M/L/XL max 4/8/16/32 vCPU and 8/16/32/64GB; macOS M/L only. Devbox lifecycle maximums Developer 4h, Team 5h, Business 24h apply even while busy; auto-stop default 15min, configurable. Separate pricing Compute table says Developer 3h and Linux concurrency 32/64/160/custom vCPU; do not apply that 3h row as the Devbox-specific limit.

GPU

Access

Deploy interface

clisdkapidashboardcontainer-imagedockerfiletemplatemcp

SDK languages

TypeScriptGo

Network & secrets

Egress controls

Outbound filtering, PROXY routing and INJECT headers from Vault; INJECT requires deep packet inspection and keeps secrets outside the workload.

Secrets

Namespace Vault stores secrets; blueprint/spec references inject into workloads, or egress INJECT resolves outside the workload.

Bring your own cloud

Placement & use

Jurisdiction

US legal entity; global processing by default; enterprise region-exclusive data residency still globally replicates operational metadata.

Advertised workloads

CI CD runnersGitHub actionsDocker buildsDevboxesAI coding agentsBuild cachingCompute/memory heavy tests

03 Capabilities 27 pass · 4 partial · 25 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 7/11

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

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.

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).

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.

Not 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.

Supported

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

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.

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 5/8

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Supported

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

Supported

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

Partially supported

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

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).

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.

Supported

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

Not 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 applicable

Developer access 6/9

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.

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.

Not supported

Private container registryHosted private image registry.

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 applicable

AI & agents 3/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.

Supported

MCP clientActs as an MCP client / consumes MCP tools.

Not 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).

Not supported

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

Not 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 0/1

First-party databasePlatform-provided managed database.

Not 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 applicable

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 applicable

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 applicable

Platform & operations 2/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not 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.

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).

Not supported

Organisation & security 4/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.

Supported

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

Supported

BYOCRuns inside the customer's own cloud account.

Not 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).

Supported

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

Not 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.

Build-system cachingbuild-cache
“Turborepo, Gradle, Bazel and Nix caches; cache volume storage and snapshots.” namespace.so

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

Can an agent read it?

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

10/11

7 full · 3 partial · 91% of applicable checks

llms.txt
Supported
“Substantive /llms.txt (11.5KB) and /docs/llms.txt (30KB), products, pricing and docs links.”
llms-full.txt
Not supported
“/llms-full.txt HTTP 404; index is links, not comprehensive inline full text.”
robots.txt AI policy
Partially supported
“robots 'User-agent: * Allow: /' — permissive default-allow, no explicit AI-UA mention”
JSON-LD
Supported
“Homepage JSON-LD includes SoftwareApplication name/description/installUrl and organization.”
Sitemap
Supported
“https://namespace.so/sitemap.xml indexes sitemap-0.xml and docs/sitemap.xml; both fetched and non-trivial.”
Meta tags
Supported
“Descriptive <title> + meta description present”
Markdown negotiation
Partially supported
“Homepage Accept: text/markdown still HTML; pricing.md and docs .md variants are readable Markdown.”
Content efficiency
Partially supported
“Readable text / homepage HTML bytes = 4.95%; script/style/SVG removed.”
Docs discoverable
Supported
“Docs first-class (namespace.so/docs; llms.txt index)”
Machine-readable pricing
Supported
“Structured pricing + per-shape unit-minute tables + a dedicated /pricing.md markdown version”
No anti-bot wall
Supported
“No challenge on public content (homepage 200)”

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
“Documented gRPC/Connect API at /docs/reference/api.md.”
OpenAPI spec
Not supported
“https://namespace.so/openapi.json and /swagger.json return 404; https://namespace.so/docs/reference/api.md documents Buf Protocol Buffers/gRPC/Connect rather than a linked OpenAPI spec.”
MCP server
Supported
“https://namespace.so/docs/reference/mcp/index.md documents https://mcp.namespace.so/mcp and /mcp/readonly, including Devbox lifecycle/commands after workspace authorization.”
SDK packages
Supported
“Maintained TypeScript and Go SDKs: /docs/reference/sdk.md.”
Auth documented
Supported
“Bearer tokens, OIDC federation, scoped credentials documented in /docs/reference/api.md.”
Self-serve credentials
Supported
“nsc token create supports scope/expiry after initial browser-authorized login; programmatic issuance, not unauthenticated signup.”
Webhooks
Partially supported
“https://namespace.so/docs/integrations/claude.md documents an inbound Anthropic lifecycle webhook URL and generated webhook secret; Namespace outbound event delivery and signature algorithm not specified.”
CLI tool
Supported
“Official nsc and devbox CLIs.”
Error model
Partially supported
“Documented gRPC/Connect status codes, structured resource-limit errors and typed SDK errors; explicit JSON error wire shape not established.”
Rate limits documented
Not supported
“Workspace capacity limits are not API request-rate limits; no API rate/response-header contract found in captured documentation.”
Agent config files
Partially supported
“One advertised skills repository; /agents.md and /.well-known/agent 404. Dockerfile/config examples are not separate discovery surfaces.”

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

Advertised integrations 6

Claude Code Anthropic
Supported
“Claude Code setup: claude mcp add --transport http namespace https://mcp.namespace.so/mcp.”
Source namespace.so
Codex CLI OpenAI
Supported
“Codex CLI setup: codex mcp add namespace --url https://mcp.namespace.so/mcp.”
Source namespace.so
Cursor Anysphere
Supported
“Cursor one-click Namespace MCP installation; separately documented Cursor Cloud Agents integration.”
Source namespace.so
Amp Sourcegraph
Supported
“Amp setup: amp mcp add namespace https://mcp.namespace.so/mcp.”
Source namespace.so
Gemini CLI Google
Supported
“Gemini CLI setup: gemini mcp add --transport http namespace https://mcp.namespace.so/mcp.”
Source namespace.so
Devin Cognition
Supported
“Devin on Devboxes integration.”
Source namespace.so

Plausible compatibility 10

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.

Aider
Antigravity
Droid
Goose
Hermes Agent
Kilo Code
Kiro CLI
OpenCode
Pi
Qwen Code

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

Certifications held 2

SOC 2 Type II
certifiedhostedHeld list confirmed from rendered public trust center on 2026-10-12; report download requires access.
“Compliance: SOC 2 Type II”
Source trust.namespace.soConfidence: high
GDPR
self-attestedhostedDPA available; EU datacenters. No explicit ISO 27001 found on the public surface.
“Data Processing Agreement published (GDPR compliance document).”
Source namespace.soConfidence: medium

Regions —

Regions are not disclosed on the public surface.

Multi-region compute and all-plan regional preferences documented; region-exclusive workload residency is Enterprise, with globally replicated operational metadata. Devbox site selector/site-latency exposes live availability; iad appears as SDK default. Complete physical Devbox site inventory not enumerated on retained public pages; no CI region list is silently applied to Devboxes.

Legal

Privacy notice Terms of service

07 Company & presence Facts only, not scored

Company

Headquarters: San Francisco, CA (legal address)
Founded: 2021
Team size: Not disclosed
Hiring: Open roles

Funding

2026-03-23Seed and Series A combined · $23 million
2026-10-05Series B · $42 million

Notable people

Hugo Santos, co-founder and CEO; team formerly worked on Google Boq

Activity

Last release: Latest captured numbered changelog: 023, 2026-07-30 namespace.so
Last blog post: 2026-10-05 — Announcing our $42M Series B namespace.so

Presence 7

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

08 Sources & method How this entry was produced

Public surface only

Everything here was read from namespace.so'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 IaaS products →