{ "features_resolved": { "snapshot_any": true, "snapshot_mem": true, "fork": true, "pause_resume": true, "persistent_disk": true, "whole_disk": true, "persist_scope": null, "volumes": false, "auto_stop_idle": true, "long_sessions": true, "custom_image": true, "image_snapshot": true, "image_oci": true, "vm_isolation": true, "docker_inside": true, "nested_virt": false, "root": true, "systemd": null, "browser": true, "desktop": false, "computer_use": false, "code_interpreter": false, "browser_control": null, "desktop_control": null, "browser_and_desktop": false, "anti_bot": false, "captcha_solving": false, "residential_ip": false, "agent_harnesses": true, "ssh": true, "public_ipv4": false, "inbound_https": true, "custom_domain": null, "raw_tcp_inbound": false, "egress_allowlist": true, "open_internet": true, "static_egress_ip": false, "private_network": true, "self_host": false, "byoc": true, "open_source": false, "soc2": null, "hipaa": null, "sso": true, "gpu": false, "arm64": false, "windows": false, "macos": false, "lang_python": false, "lang_node": false, "lang_go": null, "lang_rust": null, "lang_java": null, "gpu_desktop": false, "credential_injection": true, "egress_http_rules": true, "wake_on_request": true, "live_resize": false, "fork_running": true, "memory_snapshot_fork": false, "webhooks": true, "scheduled_wakeups": true, "audit_logs": true, "eu_data_residency": false, "zero_data_retention": null, "scoped_api_keys": null, "spend_limits": null, "mcp_server": false, "usage_api": true, "snapshot_auto": true, "snapshot_on_demand": true, "harness_api": true, "own_agent_api": false, "fast_boot": null, "strong_isolation": true, "ingress_rules": true, "guest_firewall": true, "secret_proxy": true, "secret_proxy_any": true, "volume_attach": false, "volume_shared": false, "sidecar": null, "fuse": true, "kernel_features": true, "burst": null }, "company": { "id": "islo", "checked": "2026-09-30", "company": "Incredibuild Software Ltd. (Islo is Incredibuild's agent-sandbox product)", "ownership": { "value": "subsidiary", "parent": "Incredibuild Software Ltd.", "source": "https://www.prnewswire.com/news-releases/incredibuild-launches-islo-an-agent-sandbox-with-granular-security-and-robust-isolation-bringing-enterprise-controls-to-ai-driven-software-development-302761292.html", "quote": "Incredibuild, the leading provider of SDLC execution acceleration and intelligence, today announced the launch of Islo, a sandbox for AI agents" }, "stage": { "value": "subsidiary", "source": "https://www.incredibuild.com/about-us", "quote": "AI SANDBOX ISLO: The always-on execution layer for AI coding agents · PRODUCT · RELEASED MAY 2026", "confidence": "high", "note": "Islo is a product line launched by Incredibuild in May 2026, not a separately-funded company. Funding figures below are for parent company Incredibuild, which was itself acquired by Fortissimo Capital (a PE firm) in 2018 and later took a large growth investment from Insight Partners." }, "accelerators": [], "total_funding_usd": { "value": 175000000, "status": "estimated", "basis": "Sum of Incredibuild's two reported rounds: $140M (Insight Partners, 2021, primary+secondary per VentureBeat) + $35M (2022, per TechCrunch headline cited by Wikipedia). No dedicated funding has been reported for Islo itself; figure is for the whole parent company and may not reflect net new capital since the 2021 round included a secondary component.", "source": "https://en.wikipedia.org/wiki/Incredibuild", "quote": "Wiggers, Kyle (2021-03-17). \"Grid computing software developer Incredibuild raises $140M\". VentureBeat. ... Lunden, Ingrid (2022-06-27). \"Incredibuild powers up with $35M for gaming and software dev\". TechCrunch." }, "last_round": { "type": "growth (undisclosed series letter)", "amount_usd": 35000000, "date": "2022-06", "leads": [], "status": "confirmed", "source": "https://en.wikipedia.org/wiki/Incredibuild", "quote": "Lunden, Ingrid (2022-06-27). \"Incredibuild powers up with $35M for gaming and software dev\". TechCrunch. Retrieved 2022-12-22." }, "investors": [ "Insight Partners", "Fortissimo Capital" ], "portfolio_listings": [], "revenue": { "value": null, "status": "unknown" }, "employees": { "value": 95, "source": "https://venturebeat.com/business/grid-computing-software-developer-incredibuild-raises-140m/" }, "note": "Islo (islo.dev) is an AI-agent sandbox product launched in May 2026 by Incredibuild, an Israeli grid-computing/build-acceleration company founded in 2002. Incredibuild was acquired by PE firm Fortissimo Capital in 2018, then took a $140M primary+secondary investment led by Insight Partners in March 2021, and a further $35M round in June 2022 (per TechCrunch, via Wikipedia citation; original article page no longer resolves live, so lead investor and exact round type for the 2022 raise could not be independently confirmed within the research budget). No funding, revenue, or headcount figures specific to Islo as a standalone entity have been published; it is best understood as a new product line inside an established, well-capitalized private company rather than a separately financed startup." }, "id": "islo", "name": "Islo", "url": "https://islo.dev/pricing", "category": "agent-sandbox", "isolation": "vm", "modes": [ { "key": "on-demand", "label": "Pay-as-you-go (Team list rates)", "pricing": "resource", "vcpu_h": 0.07, "ram_gib_h": 0.04, "cpu_basis": "alloc", "ram_basis": "alloc", "active_floor": 0, "ram_per_vcpu": [ null, null ], "ram_fixed_per_vcpu": null, "vcpu_options": null, "min_vcpu": null, "max_vcpu": null, "max_ram_gib": null, "sizes": null, "pool_tiers": null, "requires_always_on": false, "always_on_month_per_instance": null, "commit_note": null, "min_billed_seconds": null, "granularity_s": null, "start_fee": 0, "boot_overhead_s": null, "multiplier": 1, "windows_vcpu_h": null, "gpu": {}, "note": "CPU billed per allocated core while running; RAM per provisioned GB; custom integer vcpus/memory_mb/disk_gb with no published limits. Idle-but-running bills at full rate until pause_after_idle fires. Paused/stopped: $0 compute. Basis verified 2026-09-28: CPU \"$0.07/CPU-hour\" billed \"per core while the env runs\"; memory \"per GB you provision\" (https://islo.dev/pricing). pause_after_idle: \"Pause after this many seconds without activity (no exec, file I/O, port traffic, etc.)\" (https://docs.islo.dev/concepts/sandbox-lifecycle.md).", "flags": [], "features": { "isolation": "vm" } } ], "storage": { "included_disk_gib": 0, "disk_gib_month": 0.511, "disk_billed_when_stopped": null, "snapshot_gib_month": null, "paused_ram_billed": false }, "network": { "egress_free_gib": null, "egress_gib": null, "ipv4_month": null, "ipv4_available": false, "internet": { "default": "configurable", "evidence": [ { "quote": "Gateways control how your sandbox connects to external services. A gateway profile is a network policy plus an ordered set of rules", "url": "https://docs.islo.dev/cli/gateways.md" }, { "quote": "No gateway (default)", "url": "https://docs.islo.dev/cli/gateways.md" }, { "quote": "if nothing matches, the profile's `--default-action` decides", "url": "https://docs.islo.dev/cli/gateways.md" } ] } }, "plans": [ { "name": "Free", "fee": 0, "fee_is_credit": false, "included_usd": null, "per_seat": 0, "concurrency": 5, "max_session_h": null, "max_vcpu": null, "max_ram_gib": null, "sizes_allowed": null, "note": "Signup credits, no card; amount unpublished. 5-concurrent cap per launch press coverage (The New Stack), not on islo.dev.", "flags": [] }, { "name": "Team", "fee": 0, "fee_is_credit": false, "included_usd": 0, "per_seat": 0, "concurrency": 50, "max_session_h": null, "max_vcpu": null, "max_ram_gib": null, "sizes_allowed": null, "note": "Pay-as-you-go at list rates; no seat licenses. 50 concurrent running sandboxes per press coverage; paused sandboxes don't count.", "flags": [] }, { "name": "AWS Marketplace Team Starter", "fee": 50, "fee_is_credit": true, "included_usd": 0, "per_seat": 0, "concurrency": 50, "max_session_h": null, "max_vcpu": null, "max_ram_gib": null, "sizes_allowed": null, "note": "$50/month contract = $50 monthly credits ('294 hours compute for most customers'), no refunds; overage handling and rollover unspecified in listing. Concurrency 50 assumed = Team plan ('Team Starter Package'); was null, which let the engine bypass the Team 50-concurrent cap via this plan (verifier 2026-09-28).", "flags": [] }, { "name": "Enterprise / BYOC", "fee": null, "fee_is_credit": false, "included_usd": null, "per_seat": null, "concurrency": null, "max_session_h": null, "max_vcpu": null, "max_ram_gib": null, "sizes_allowed": null, "note": "Custom packages; FAQ: 'You still pay for compute time. BYOC deployment terms may vary.'", "flags": [ "sales" ] } ], "free": { "monthly_credit": 0, "one_time_credit": null }, "features": { "linux": true, "windows": false, "macos": false, "arm64": false, "gpu": false, "gpu_types": [], "snapshot": "mem", "pause_resume": true, "fork": true, "persistent_disk": true, "volumes": false, "auto_stop_idle": true, "max_session_h": null, "custom_image": true, "docker_inside": true, "nested_virt": false, "root": true, "systemd": null, "browser": true, "desktop": false, "computer_use": false, "code_interpreter": false, "agent_harnesses": true, "ssh": true, "public_ipv4": false, "inbound_https": true, "custom_domain": null, "raw_tcp_inbound": false, "egress_allowlist": true, "static_egress_ip": false, "private_network": true, "self_host": false, "byoc": true, "open_source": false, "regions": [ "us" ], "soc2": null, "hipaa": null, "sso": true, "lang_python": false, "lang_node": false, "lang_go": null, "lang_rust": null, "lang_java": null, "gpu_desktop": false, "credential_injection": true, "egress_http_rules": true, "wake_on_request": true, "live_resize": false, "fork_running": true, "memory_snapshot_fork": false, "webhooks": true, "scheduled_wakeups": true, "audit_logs": true, "eu_data_residency": false, "zero_data_retention": null, "scoped_api_keys": null, "spend_limits": null, "mcp_server": false, "isolation": "vm", "image_oci": true, "snapshot_auto": true, "snapshot_on_demand": true, "harness_api": true, "egress_allowlist_level": "domain", "ingress_rules": true, "guest_firewall": true, "secret_proxy": "any-http", "volume_attach": false, "volume_shared": false, "anti_bot": false, "captcha_solving": false, "egress_ip_type": "datacenter", "own_agent_api": false, "max_session_unlimited": true, "open_internet": true, "usage_api": true }, "perf": { "cpu_runs_s": null, "cold_start_ms": null, "burst_tti_ms": null, "dax_s": null }, "perf_source": "No benchmark row: provider is not in ComputeSDK results or the HPC run (as of 2026-09-28). See research/perf-map.json.", "knobs": [ { "id": "pause_after_idle_tail", "label": "Idle tail before pause_after_idle (x session hours)", "kind": "slider", "min": 1, "max": 3, "step": 0.05, "default": 1, "unit": "x", "options": null, "effect": "hours_factor", "modes": [ "on-demand" ], "why": "Idle-but-running sandboxes bill full allocated CPU/RAM until the pause_after_idle lifecycle timer fires; without a policy they bill until deleted, and the policy is immutable after creation. Paused = $0 compute. Factor = (session + idle timer) / session.", "source": "https://docs.islo.dev/concepts/sandbox-lifecycle.md" } ], "caveats": [ "Billing granularity and minimum per start unpublished ('billed per hour' / 'per vCPU-hour'); per-second metering not confirmed.", "Whether disk is billed while paused/stopped is unresolved: FAQ says 'No charge when stopped' but storage is a listed $0.0007/GB-h meter.", "Named snapshot storage price unpublished (snapshot_gib_month null); if billed at the disk rate it would be $0.511/GB-month.", "Disk billed per provisioned GB with no stated free allowance; included_disk_gib=0 reflects that, and the engine should add W.disk x $0.0007/GB-h while running.", "Free (5 concurrent) / Team (50 concurrent) / Enterprise tiers come from launch press coverage (The New Stack, May 2026), not an Islo page.", "Signup credit amount unpublished; Harbor users get $250 one-time via promo code HARBOR250 (not modeled in free.one_time_credit).", "Egress, IPv4 and region pricing unpublished; no public IPv4 product (HTTPS shares + CLI tunnel only).", "Gateway inference (Islo-managed LLMs) draws from the same credits at unpublished token rates.", "Lifecycle policy (pause_after_idle etc.) is immutable after creation; sandboxes without it bill at full rate while idle.", "Heavy paused sandboxes can take 5-7 min to become resumable (third-party report).", "No benchmark data for islo in benchmarks.json.", "Official RL page cost example bills 10-minute tasks pro rata (500 tasks x ~10 min at 4 vCPU / 1 GB / ~2 GB disk = $26.78, ~$0.054/task), so metering is at least sub-hour in practice. Exact granularity and per-start minimum are still unpublished; the engine should not assume hourly rounding.", "Official pages show 300 concurrent Harbor rollouts ('--n-concurrent 300', 'hundreds of concurrent rollouts'), well above the press-reported 50-concurrent Team cap. The cap is probably raisable, but it is still not published on any Islo page." ], "sources": [ "https://islo.dev/pricing", "https://docs.islo.dev/concepts/sandbox-lifecycle.md", "https://docs.islo.dev/cli/sandbox-commands.md", "https://docs.islo.dev/cli/snapshots.md", "https://docs.islo.dev/integrations/harbor.md", "https://docs.islo.dev/api-reference/credits/get-credit-balance.md", "https://docs.islo.dev/api-reference/sandboxes/create-sandbox.md", "https://aws.amazon.com/marketplace/pp/prodview-3eew6wp37ylek", "https://thenewstack.io/incredibuild-ai-agents-sandbox-coding/", "https://www.prnewswire.com/news-releases/incredibuild-launches-islo-an-agent-sandbox-with-granular-security-and-robust-isolation-bringing-enterprise-controls-to-ai-driven-software-development-302761292.html", "https://github.com/madarco/agentbox-provider-islo" ], "fleet": { "default_max_instances": 5, "default_max_vcpu": null, "default_max_gpus": null, "raise": null, "raise_time_days": null, "verification": "Official pricing says signup credits with no card; further screening not published.", "tiers": "Launch coverage reports Free 5, Team 50, Enterprise custom; current official pricing does not republish numeric tier limits.", "notes": "Third-party-reported concurrency: The New Stack launch article, not independently confirmed by current official quota docs. Thus 10/50 via reported Team path only; 300/1,000 custom unverified. Lifecycle docs confirm paused sandboxes do not count toward running quota. Launch article also mentions private beta; confirm current admission. Current self-serve tier activation/increase mechanism is not independently verified, so raise remains null.", "sources": [ "https://thenewstack.io/incredibuild-ai-agents-sandbox-coding/", "https://islo.dev/pricing", "https://docs.islo.dev/concepts/sandbox-lifecycle.md" ], "researched": "2026-09-28" }, "audit_2026_09_29": { "reviewed": 2 }, "feature_evidence": { "snapshot_auto": { "value": true, "source": "https://docs.islo.dev/concepts/sandbox-lifecycle.md", "quote": "When a timer fires, the platform **pauses** the VM: state is snapshotted, compute is released, and the sandbox no longer counts against running-sandbox quotas. Paused sandboxes keep their filesystem and can be resumed.", "note": "Opt-in lifecycle policy set at creation (immutable): pause_after_idle (no exec/file I/O/port traffic) and/or pause_after (active-runtime cap); auto_resume=on_activity resumes transparently on the next exec/file/webhook. Memory included: 'files, processes, and in-memory state are restored on resume' (https://docs.islo.dev/cli/sandbox-commands.md, islo pause). Without a policy nothing pauses automatically.", "checked": "2026-09-29" }, "snapshot_on_demand": { "value": true, "source": "https://docs.islo.dev/cli/snapshots.md", "quote": "Snapshots let you capture the complete state of a running sandbox and restore it later.", "note": "Named snapshots (islo snapshot save / POST snapshots) are filesystem-only ('The snapshot captures the entire filesystem state'), from a running sandbox; restore always creates a NEW sandbox ('Restoring from a snapshot creates a new sandbox'), so they work as templates/forks (many sandboxes from one snapshot). Memory-including state is only via pause/resume of the same sandbox (manual islo pause or API).", "checked": "2026-09-29" }, "harness_api": { "value": true, "source": "https://docs.islo.dev/concepts/automations.md", "quote": "Harness and model live on the `run_agent` step, never in `line.toml`.", "note": "Jobs / factory lines (API + CLI) run a first-party run_agent step with harness codex, claude, cursor or opencode (+ 'custom' exec) and a prompt; runs expose events (islo factory line-run events), follow-ups and mid-stage agent turns (line-run follow-up / agent-turn / ask), steer/stop/retry. Harness list from Islo's own skills repo (harness-models-knowledge.md: '`harness` must be a literal (`codex`, `claude`, `cursor`, or `opencode`)'). Also CLI: 'islo use --agent claude --task \"...\"' starts Claude Code/Cursor/Codex in a persistent background session and resumes Claude Code sessions on reconnect (https://docs.islo.dev/cli/agent-integration.md).", "checked": "2026-09-29" }, "egress_allowlist": { "value": true, "source": "https://docs.islo.dev/cli/gateways.md", "quote": "A gateway profile is a network policy plus an ordered set of rules — each rule matches outbound traffic by host (and optionally path/method) and decides whether to allow it, deny it, or inject credentials before forwarding.", "note": "Gateway profile per sandbox: --default-action allow|deny (default-deny possible), host globs ('*.anthropic.com'), --internet-access true/false (also internet_enabled on create-sandbox). Host-based; no IP/CIDR rules documented. Rules changed after creation need sandbox recreate/reconnect.", "checked": "2026-09-29", "level": "domain" }, "egress_http_rules": { "value": true, "source": "https://docs.islo.dev/cli/gateways.md", "quote": "Restrict to one or more HTTP methods (`GET`, `POST`, …)", "note": "Per-rule path pattern, HTTP methods, rate limit (rpm), and request/response content filters (regex, content-type, size-limit, and an LLM 'judge' filter with Anthropic/OpenAI model per the API reference create-gateway-rule).", "checked": "2026-09-29" }, "ingress_rules": { "value": true, "source": "https://docs.islo.dev/cli/sharing.md", "quote": "Islo lets you create shareable URLs for HTTP services running inside your sandbox.", "note": "Ports are not public by default: you choose a port to share (islo share [port]) with a TTL (default 24h, e.g. 30m-7d) and revoke with islo unshare; shares are public HTTPS URLs (API: 'Create a temporary public share for a sandbox port'), no auth/IP allowlist on the share itself. Non-HTTP access via authenticated islo port-forward tunnel. Incoming webhooks authenticate (HMAC/bearer/basic) before delivering to a port.", "checked": "2026-09-29" }, "guest_firewall": { "value": true, "source": null, "quote": null, "note": "Each sandbox is 'a microVM with its own kernel' (https://islo.dev/sandboxes) with root/sudo (setup scripts use sudo apt-get; Docker inside supported), so iptables/nftables inside should work. Not documented.", "checked": "2026-09-29", "derived": true }, "secret_proxy": { "value": "any-http", "source": "https://docs.islo.dev/cli/gateways.md", "quote": "Credentials never reach the sandbox process — authentication happens at the host/network layer.", "note": "Gateway rules inject a stored provider key as bearer/basic/custom header for any host; integrations cover GitHub, Slack, Anthropic/OpenAI/Cursor and tenant custom services (API key or OAuth). Sandboxes see phantom placeholder env vars (values starting 'islo_p') replaced on egress (islo-labs/skills gateway-integrations.md). AWS: IAM role assumed via STS through the gateway, no long-lived keys in the sandbox (https://docs.islo.dev/integrations/aws.md). Git over HTTPS to GitHub covered; SSH/database protocols not documented. Islo inference (gateway.islo.dev) additionally provides platform-owned model credentials.", "checked": "2026-09-29" }, "volume_attach": { "value": false, "source": "https://docs.islo.dev/api-reference/sandboxes/create-sandbox.md", "quote": null, "note": "Create-sandbox schema has disk_gb but no volume/mount fields; no volume concept anywhere in the docs index. Persistence is via pause/resume and snapshots. Users can self-mount S3 with mount-s3 via the AWS cloud-role integration (third-party FUSE, not a first-party volume).", "checked": "2026-09-29" }, "volume_shared": { "value": false, "source": "https://docs.islo.dev/llms.txt", "quote": null, "note": "No shared volume/filesystem product. Sharing between sandboxes is only via snapshots (copy) or a user-mounted S3 bucket (mount-s3 over the AWS integration, read-write per IAM policy). 'Knowledge' is a versioned document store API, not a filesystem.", "checked": "2026-09-29" }, "nested_virt": { "value": false, "source": "https://islo.dev/security", "quote": "ISOLATION microVM per agent computer. Stronger boundary than containers alone for untrusted or production-adjacent work.", "note": "Not documented either way. Derived: each sandbox is itself a microVM (Firecracker/cloud-hypervisor-style guest); such guests typically do not expose /dev/kvm for nested virtualization, and no docs mention nested virt, running VMs/emulators, or /dev/kvm inside a sandbox.", "checked": "2026-09-30" }, "anti_bot": { "value": false, "source": "https://islo.dev/sandboxes", "quote": "An agent sandbox is an isolated computer where a coding agent runs shell commands, opens a browser, starts services, and calls APIs under policy constraints.", "note": "not offered: outside the product's scope. Islo is infrastructure for coding agents (shell/services/APIs plus a generic browser for testing); no stealth/fingerprinting-evasion feature against bot detection is documented anywhere in the docs, marketing, or gateway pages.", "checked": "2026-09-30" }, "captcha_solving": { "value": false, "source": "https://islo.dev/sandboxes", "quote": "An agent sandbox is an isolated computer where a coding agent runs shell commands, opens a browser, starts services, and calls APIs under policy constraints.", "note": "not offered: outside the product's scope. No CAPTCHA-solving feature is mentioned anywhere in Islo's docs, product, or gateway pages; the product is coding-agent sandbox infrastructure, not a web-scraping/anti-bot service.", "checked": "2026-09-30" }, "egress_ip_type": { "value": "datacenter", "source": "https://docs.islo.dev/cli/gateways.md", "quote": "Routes traffic — proxies through Islo's gateway so requests can be audited and rate-limited.", "note": "Islo runs cloud VMs (also sold via AWS Marketplace) with outbound traffic optionally routed through Islo's own gateway/proxy. No residential or mobile IP option is documented anywhere; egress is standard cloud/datacenter IP space. Not explicitly labeled 'datacenter' on any page.", "checked": "2026-09-30" }, "fork_running": { "value": true, "source": "https://docs.islo.dev/cli/snapshots.md", "quote": "Snapshots let you capture the complete state of a running sandbox and restore it later... Save a snapshot of a running sandbox: `islo snapshot save my-sandbox`... Create a new sandbox from a snapshot using `--snapshot`: `islo use new-sandbox --snapshot before-refactor`", "note": "Snapshot save operates on a running sandbox without stopping/pausing it, and restoring the snapshot creates a brand-new sandbox (clone). The original keeps running throughout, so this satisfies cloning a running machine without stopping it (filesystem-only clone, not memory/processes).", "checked": "2026-09-30" }, "live_resize": { "value": false, "source": "https://docs.islo.dev/api-reference/sandboxes/create-sandbox.md", "quote": "`vcpus` (integer, optional) - `memory_mb` (integer, optional) - `disk_gb` (integer, optional)", "note": "vCPU/memory/disk are set only in the create-sandbox request; no update/resize endpoint or CLI command for changing resources on a running sandbox is documented in the API reference or CLI sandbox-commands page. Resizing appears to require creating a new sandbox (e.g. from a snapshot) with different resources.", "checked": "2026-09-30" }, "own_agent_api": { "value": false, "source": "https://islo.dev/solutions/enterprise", "quote": "Which harnesses and models are supported? Islo is harness-agnostic. Claude Code, Codex, and Cursor run natively, and custom harnesses run on the same infrastructure.", "note": "not offered: outside the product's scope. Islo's API/CLI drives YOUR coding harness (Claude Code, Codex, Cursor, custom) inside its sandboxes (harness_api) — it does not ship its own first-party task/browser/computer-use agent product to drive.", "checked": "2026-09-30" }, "lang_python": { "value": false, "source": "https://docs.islo.dev/concepts/setup-scripts.md", "quote": "Setup scripts prepare a sandbox after sources are cloned but before you start using it — installing language runtimes, syncing dependencies, building tools. ... `islo add python 3.12` # Add the Python recipe pinned to 3.12", "note": "Language runtimes are explicitly something you add via setup scripts/recipes (`islo add python `), not something the docs describe as preinstalled in the default `islo-runner` image. No page states Python ships out of the box.", "checked": "2026-09-30" }, "lang_node": { "value": false, "source": "https://docs.islo.dev/concepts/setup-scripts.md", "quote": "`islo add node 20` # Add the Node recipe pinned to 20", "note": "Same as lang_python: Node.js is added via a setup-script recipe rather than documented as preinstalled by default in the base sandbox image.", "checked": "2026-09-30" }, "public_ipv4": { "value": false, "source": "https://docs.islo.dev/cli/sharing.md", "quote": "Islo lets you create shareable URLs for HTTP services running inside your sandbox.", "note": "No public IPv4 product is documented or priced anywhere (pricing page only lists CPU/memory/storage). Reaching a sandbox is via HTTPS share URLs, `islo port-forward` (local tunnel), or `islo ssh` (proxied SSH via `.islo`) — not a dedicated public IPv4 address.", "checked": "2026-09-30" }, "max_session_h": { "value": "none", "source": "https://islo.dev/sandboxes", "quote": "How long can a computer stay up? Long enough for jobs measured in hours rather than seconds. Sessions survive disconnects and restarts, which is what makes unattended work possible.", "note": "No published hard ceiling on session length. Lifecycle policy fields (`pause_after`, `delete_after`) are optional and user-set at creation (https://docs.islo.dev/concepts/sandbox-lifecycle.md); without them a running sandbox is not automatically stopped, behaving like a VM that runs until you stop it.", "checked": "2026-09-30" }, "persistent_disk": { "value": true, "corrected_from": false, "source": "https://docs.islo.dev/concepts/sandbox-lifecycle.md", "quote": "When a timer fires, the platform **pauses** the VM: state is snapshotted, compute is released, and the sandbox no longer counts against running-sandbox quotas. Paused sandboxes keep their filesystem and can be resumed.", "note": "Contradiction confirmed: card already lists pause_resume:true and snapshot:mem, and lifecycle docs state paused sandboxes 'keep their filesystem'. islo pause / API pause-sandbox (manual or via pause_after_idle/pause_after policy) preserves the full disk+memory state until islo resume. Default is no lifecycle policy set (manual pause/resume only) - there's no auto-delete-on-stop default; disk persists across pause/resume in all cases. Correcting persistent_disk to true.", "checked": "2026-09-30" }, "memory_snapshot_fork": { "value": false, "source": "https://docs.islo.dev/cli/snapshots.md", "quote": "The snapshot captures the entire filesystem state ... Restoring from a snapshot creates a new sandbox", "note": "Named/on-demand snapshots (islo snapshot save, POST /snapshots) are explicitly filesystem-only, not memory - the card's own feature_evidence for snapshot_on_demand confirms this ('Snapshots... are filesystem-only'). The only memory-inclusive state capture is pause/resume of the SAME sandbox (no new sandbox id, no fork). No documented way to fork a running sandbox's live memory state into a new, independent sandbox. Confirms false.", "checked": "2026-09-30" }, "desktop": { "value": false, "source": "https://docs.islo.dev/overview.md", "quote": "Islo gives you persistent, hardware-isolated sandbox environments that stay running... dedicated microVM", "note": "Full docs index (llms.txt) and CLI/API reference cover only exec, files, ports, sessions, SSH, sharing, gateways, snapshots and factory automations - no GUI/VNC/remote-desktop product anywhere. Islo sandboxes are headless Linux microVMs for code/CLI/agent work; no desktop environment is offered. Outside scope of the product.", "checked": "2026-09-30" }, "computer_use": { "value": false, "source": "https://docs.islo.dev/llms.txt", "quote": "Sandbox Commands: Islo CLI commands for creating, managing, and executing code in secure sandbox environments.", "note": "No screenshot/mouse/keyboard-control API or computer-use tool documented anywhere in the docs index, CLI reference, or API reference (checked sandbox-commands.md, create-sandbox.md, agent-integration.md). Product surface is exec/files/ports only. Confirms false.", "checked": "2026-09-30" }, "volumes": { "value": false, "source": "https://docs.islo.dev/api-reference/sandboxes/create-sandbox.md", "quote": "disk_gb (integer, optional) ... memory_mb (integer, optional) ... vcpus (integer, optional)", "note": "Create-sandbox schema has only a per-sandbox disk_gb; no volume/mount/attach field anywhere in the API. This matches the card's own feature_evidence for volume_attach/volume_shared (both false: 'no volume concept anywhere in the docs index'; persistence is via pause/resume and snapshots, plus a third-party S3 FUSE mount). Confirms false.", "checked": "2026-09-30" }, "mcp_server": { "value": false, "source": "https://docs.islo.dev/overview.md", "quote": "These docs are also available as an MCP server at https://docs.islo.dev/_mcp/server — point your AI agent at it to query Islo docs without leaving the editor.", "note": "The only MCP server Islo publishes is a documentation-search server for querying the docs themselves; there is no first-party MCP server exposing sandbox create/exec/file operations as MCP tools (agent integration is via SDK/CLI/API and islo-labs/skills, not MCP). Confirms false as a sandbox-control MCP server.", "checked": "2026-09-30" }, "gpu": { "value": false, "source": "https://docs.islo.dev/llms.txt", "quote": "Sandbox Lifecycle... Setup Scripts... Gateway Inference... Harbor... CLI Overview... Sandbox Commands...", "note": "GPU is never mentioned in the full documentation index, create-sandbox schema (vcpus/memory_mb/disk_gb only, no gpu field), CLI reference, or changelog. Card's own mode entry already has gpu:{} (empty) and gpu_types:[]. Confirms false.", "checked": "2026-09-30" }, "windows": { "value": false, "source": "https://docs.islo.dev/overview.md", "quote": "Isolation | Shared kernel | Hardware-level ✓ - dedicated microVM", "note": "Sandboxes are Linux microVMs (images are OCI/Docker images, e.g. ghcr.io/islo-labs/islo-runner:latest); the CLI installer supports macOS/Linux as the *client* machine only, not as a sandbox guest OS. No Windows sandbox guest offered anywhere in docs. Outside scope of a Linux-only microVM sandbox.", "checked": "2026-09-30" }, "macos": { "value": false, "source": "https://docs.islo.dev/getting-started/installation.md", "quote": "Install Islo CLI on macOS or Linux using the one-liner script.", "note": "macOS/Linux support refers to the local CLI client, not the sandbox guest OS - sandboxes run as Linux microVMs from OCI images. No macOS guest sandbox is offered. Outside scope of a Linux-only microVM sandbox product.", "checked": "2026-09-30" }, "self_host": { "value": false, "source": "https://docs.islo.dev/api-reference/sandboxes/create-sandbox.md", "quote": "POST https://ca.compute.islo.dev/sandboxes", "note": "All sandbox/compute operations go through Islo-operated regional endpoints (ca.compute.islo.dev, api.islo.dev); the only enterprise custom option documented is BYOC (bring-your-own-cloud, still Islo-managed/billed per the card's Enterprise plan note: 'You still pay for compute time'), not a self-hosted/on-prem deployment of the full Islo control plane. No self-hosting docs found. Confirms false.", "checked": "2026-09-30" }, "open_source": { "value": false, "source": "https://github.com/islo-labs", "quote": "background-agents: An open-source background agents coding system (fork); skills: islo.dev skills; langchain-islo: Islo (islo.dev) sandbox integration for Deep Agents", "note": "islo-labs' public GitHub repos are SDK integrations, skills, and example/tooling projects (langchain-islo, claude-managed-agents, skills, recipes, reward-hack-bench) - none of them is the core sandbox/VM platform (compute engine, control plane, hypervisor). The platform itself (api.islo.dev / ca.compute.islo.dev) is closed-source SaaS. Confirms false.", "checked": "2026-09-30" }, "eu_data_residency": { "value": false, "source": "https://docs.islo.dev/api-reference/tenants/list-tenant-compute-regions.md", "quote": "\"regions\": [ { \"key\": \"us-west\", \"label\": \"US West\", \"api_url\": \"https://ca.compute.islo.dev\", \"ws_url\": \"wss://ca.compute.islo.dev\", \"is_default\": true } ]", "note": "The regions API's own example response lists only a US West region, matching the card's regions:[\"us\"]. No EU region key or EU data-residency claim found on any Islo page. Confirms false.", "checked": "2026-09-30" }, "static_egress_ip": { "value": false, "source": "https://docs.islo.dev/cli/gateways.md", "quote": "Applies network policies — controls which external endpoints the sandbox can reach... Routes traffic — proxies through Islo's gateway so requests can be audited and rate-limited.", "note": "Egress is host/path-rule based through Islo's shared gateway proxy; no page (gateway docs, gateway/security marketing pages, AWS integration) mentions a fixed/static outbound IP address a customer could allowlist. Absence across all egress-control docs indicates the feature isn't offered.", "checked": "2026-09-30" }, "arm64": { "value": false, "source": "https://docs.islo.dev/getting-started/installation.md", "quote": "Linux | aarch64 | Supported (musl builds)", "note": "That table is architecture support for the local Islo CLI client (macOS/Linux, incl. Apple Silicon), not the sandbox guest. The sandbox create API (vcpus/memory_mb/disk_gb only, no architecture field) and all docs/pricing pages never offer an ARM64 sandbox instance type; only one (x86_64-based) sandbox image family is described. Derived absence, not an explicit denial.", "checked": "2026-09-30" }, "usage_api": { "value": true, "source": "https://docs.islo.dev/api-reference/credits/get-credit-balance.md", "quote": "Get credit balance endpoint in API reference; sandboxes are individually metered for vCPU-hours and GB-hours at documented rates", "note": "granularity: per-sandbox; cost: yes; Islo bills per allocated vCPU-hour and provisioned GB-hour while running. Credit balance API provides account-level balance; per-sandbox usage is available through created sandbox objects with their resource allocations and runtime, enabling per-sandbox billing calculation.", "confidence": "high", "checked": "2026-10-01" }, "sso": { "value": true, "source": "https://docs.islo.dev/cli/authentication.md", "quote": "You authenticate via Google, email, or SSO.", "note": "Login runs through Descope's hosted authorization page ('Opens your default browser to the Descope authorization URL'), which offers SSO alongside Google and email. The protocol (SAML/OIDC), IdP list and which plan unlocks it are not published; islo.dev/solutions/enterprise, /security and /pricing do not mention SSO.", "checked": "2026-10-14" } }, "locations": [ { "country": "US", "state": "CA", "city": "California", "provider_region": "us-west", "self_serve": true, "choosable": true } ], "locations_source": "https://docs.islo.dev/api-reference/tenants/list-tenant-compute-regions.md", "locations_quote": "Compute regions available to the authenticated tenant. Example response shows: {\"regions\": [{\"key\": \"us-west\", \"label\": \"US West\", \"api_url\": \"https://ca.compute.islo.dev\"}]}", "locations_checked": "2026-10-01" }