---
schema_version: 7
rubric_version: "0.3"
canonical_url: "https://podium.do/compare/agents/boxes-dev-vs-podium/"
data_url: "https://podium.do/compare/agents/boxes-dev-vs-podium/data.json"
generated_at: 2026-11-22
last_checked_at: 2026-11-21
last_cross_checked_at: 2026-11-21
oldest_checked_at: 2026-11-06
publisher: "Podium"
---

# Boxes.dev vs Podium

> Podium publishes this catalog and sells an agent development environment. Podium chooses the products, criteria, sources and wording, so treat these pages as vendor-authored research. Check important claims against the linked primary sources. Sourced findings follow the same evidence rules for Podium and its competitors. Facts labeled Podium team research come from Podium's own team and have no linked source. None of this removes the conflict of interest.

> Based on data from adecomparison.com by Podium (https://adecomparison.com; source repository https://github.com/madeinorbit/ade-comparison, snapshot 4322f0c of 2026-11-22), used under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Source links and check dates are kept. Podium arranges the findings into pairs, applies its publication checks, and added its own research where marked "Podium team research". Data license terms: https://github.com/madeinorbit/ade-comparison/blob/4322f0c035f303791413639d1462a138443d8c1e/DATA-LICENSE.md

44 criteria sourced for both products; 34 criteria also agent cross-checked for both. 50 criteria with a sourced finding for at least one product. "Sourced" findings passed publication validation. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. Humans approve the rubric, templates and prototype; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent.

Each row gives the finding's status, support, check date and answer. Scope, limitations, atomic answers and sources for every finding are in each product's document, under the criterion ID. Judgment rules are in the rubric.

- Boxes.dev source checks: 2026-11-21. Details: https://podium.do/compare/agents/products/boxes-dev/index.md
- Podium source checks: 2026-11-06. Details: https://podium.do/compare/agents/products/podium/index.md
- Rubric: https://podium.do/compare/agents/rubric/index.md
- Canonical HTML: https://podium.do/compare/agents/boxes-dev-vs-podium/
- Machine-readable JSON: https://podium.do/compare/agents/boxes-dev-vs-podium/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Boxes.dev distributes macOS/Linux desktop workbenches, iOS/Android apps and its own CLI for cloud threads. The homepage also lists web access; help documents browser project setup, Billing and Team Template administration, including creating a later GitHub project on a phone before continuing in the native app. Browser agent-chat parity is not established.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium ships desktop, CLI and browser clients, including phone-browser control. The native iPhone app is private beta; the complete download offering contains no native Android app.

### ACC-02: Agent and model choice

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Native Codex and Claude Code are the documented harnesses. Codex can use OpenAI or saved OpenRouter, Vercel or compatible custom Responses providers. Provider/model choice does not establish additional coding harnesses.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium launches the native Claude Code, Codex, Grok, OpenCode, Cursor and Pi CLIs in persistent terminals on machines you control. The 0.2.0 release calls Pi fully supported. Models come from each harness catalog, and capabilities differ per harness: Pi declares no quota, handoff or hooks. Mixed-harness operation was not exercised.

### ACC-03: Subscriptions, API keys and vendor credits

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Users bring their native ChatGPT/Claude subscription login or provider API account. Boxes.dev bills compute separately and does not sell agent tokens. Multiple saved accounts and optional API fallback have explicit restart and billing consequences.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports native coding-agent logins and managed provider credentials. Claude subscriptions (via native login or a managed setup-token) and local ChatGPT/Codex login are supported paths, alongside Anthropic and OpenAI API keys. Docs list billing and hosted metering as not implemented product claims.

### ACC-04: Onboarding and project prerequisites

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Onboarding prepares a managed cloud environment through a local agent, desktop upload wizard or Team Template. Subsequent GitHub setup is also documented. Uploads need review and machine usage is separate from agent authentication.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Docs describe a first-run flow (install, podium, register a Git repository, confirm a detected logged-in harness) and a headless VPS installer with machine joining. Setup time and failure rate were not measured, and no self-serve managed cloud setup is documented. The current README and installation guide use podium.do/download and podium.do/install.sh as the canonical stable entrypoints.

### ACC-05: Programmable access

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Boxes.dev has a scripting CLI, secret-authenticated automation run/status API and OAuth remote MCP service. Their operations differ: the launch API does not return final agent results and MCP cannot answer approval dialogs.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The podium CLI covers issue create, show, update, claim, dependencies, artifacts, session send/status/read/stop and review actions, and the server exposes the same issue commands as a bearer-token MCP tool endpoint. No documented public HTTP API, SDK or webhooks were found.

### ACC-06: External tools and extensions

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. The product manages external MCP servers and supported agent plugins, while repository instructions and some account plugins remain harness-owned. Destination and authorization determine whether a tool reaches future or existing devboxes.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Podium gives agents its own issue tools over CLI and MCP, and agent profiles import and export Claude Code agent files. No Podium documentation for user-configured MCP clients, plugins or custom tools was found.

### ACC-07: Client implementation

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. The versioned public product docs identify an Electron desktop main-process log. Full desktop and mobile build sources were not found; native mobile marketing and Expo push transport do not establish the mobile UI framework.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Desktop releases use a Tauri 2 shell that serves the Podium web UI; mobile source uses Expo and React Native. A native iPhone release is described as private beta.

## Planning and context

### PLAN-01: Intake and external tracker relationship

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Prompts, Slack and Linear can start work. Linear issues keep their external identifiers and return progress/results through Agent Sessions; this is an integration, not evidence of a native Boxes.dev issue tracker.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium issue records are native and authoritative with stable references, CLI creation and editing, and agent-driven filing from conversation. The in-product assistant has Linear search, create and move tools when a key is configured, but no import or two-way tracker sync was found.

### PLAN-02: Durable task plans

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Saved thread goals retain an objective across agent responses. Codex can edit or pause a goal while keeping the thread. A goal and prompt instructions do not establish a structured acceptance-criteria or versioned project plan system.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Issue brief, acceptance criteria, state paragraph and todos persist on the durable issue record. Release 0.3.0 removed the separate design and notes fields and appended their text to the brief. On the human issue page the title, description and acceptance are editable and the brief is read-only; agents edit the brief and other fields through issue commands.

### PLAN-03: Hierarchy, dependencies and evolving scope

- **Boxes.dev**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium supports persistent parent and child issues, phases and typed dependency links, including reparenting an existing issue without replacing its identity. Since 0.3.0 issue types are task, phase and decision: epic and other kinds are retired, and any issue with children acts as a parent. Dependency types are fixed to blocked-by, related, discovered-from, supersedes and duplicates. Cycles are refused and docs list an open blocker as a reason an issue cannot start. No mandatory workflow preset applies in the baseline.

### PLAN-04: Shared context and memory

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Repository instructions, saved project guidance and shared /project files provide reusable context. The open-beta share redirects Claude project memory across devboxes; Codex can use files there without moving its state or transcripts.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. v0.3.0 routes Podium issue instructions and relay environment through terminal and engine session launch. Claude stream sessions use appended instructions and boundary callbacks; Codex server sessions use developer instructions, Grok ACP uses rules, and OpenCode uses the prompt system field. Claude and Codex boundary hooks can re-prime after compaction. Transcript mirroring is on by default; full-text indexing needs the command-palette flag, which defaults off. Agent profiles can carry markdown instructions. Curated memory, skills and memory correction or deletion controls remain unestablished. No instruction-delivery or compaction scenario was run.

### PLAN-05: Architecture and API awareness

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Agents can inspect machine files and use configured external tools, while people can search workspace files and attach images/files. No architectural consistency or spec-conflict enforcement is established.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Not established. Podium mirrors daemon transcripts by default, keeps a full-text index only when the command-palette flag is on, and stores session attachments. No repository code search, architecture awareness or API retrieval feature was found.

### PLAN-06: Native issue management and idea backlog

- **Boxes.dev**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes native issue creation with an optional start flag, separate dispatch, editing, comments, labels, assignment, search, board filters, archive, sibling ordering and an issue tree. Issue records have their own identity separate from sessions and stages are durable. The idea-to-mission scenario was not run. v0.3.0 refuses an agent close or done update while issue sessions are computing unless --confirm-interrupt is supplied; guidance says to request review and close only on user instruction.

### PLAN-07: Agent-native issue operations

- **Boxes.dev**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. CLI and MCP address the same canonical issue records for reads, creation, edits, claims, state, dependencies and artifacts. Relayed agents have worker capability scoped to their issue subtree, with --outside-scope confirmation for other existing issues. attachSession is not subtree-gated, but direct rehoming from a real issue is refused and an agent attach naming a Proposed target is refused. That does not make every Proposed subtree inert: operator attachment or spawn-time cwd binding can leave a session attached to a Proposed issue; newSubissue without targetId then bypasses the proposed-parent guard, creates a human-audience backlog child and attaches the existing session. This path remains at v0.3.0 source and was not exercised live. Concurrent-edit handling remains unknown.

### PLAN-08: Living product specifications

- **Boxes.dev**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The spec CLI and service (living specs under pspec with stable SP IDs) are in v0.3.0. Specs is an experimental, default-off feature listed on the edge channel: the flag controls the Specs UI, the spec line in CLI help and whether agents are told about the spec CLI. The podium spec command itself is dispatched, and the server specs service has no flag check, so direct CLI use does not need the flag. This agrees with the docs, which call specs not baseline rather than blocked. Not run end to end.

## Coordination and automation

### COORD-01: Parallel work

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Codex/Claude threads can run concurrently on separate devboxes or share a machine. Plans limit awake devboxes per user rather than proving a fixed session count or measured throughput.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Docs and release notes describe many sessions running as independent terminals, one worktree per issue, and several paired machines under one server, with session and issue state visible on the flight deck, board and CLI. Agent-initiated spawns are limited to 10 per target issue per UTC day. Achieved concurrency is unmeasured.

### COORD-02: Ownership and dispatch

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Dispatch routes integration events to the linked human account and configured agent. API idempotency and Linear Agent Session reuse prevent duplicate launches within those paths, without establishing a general task-claim system.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues carry an assignee, claim sets assignee and in_progress, a coordinator session can be set per issue, sessions have seats, and work can be placed on a chosen machine or agent profile. claim has no exclusivity check of its own, locks are advisory leases and Podium does not serialize agents editing one worktree, so exclusive ownership is not enforced.

### COORD-03: Inspectable delegation and communication

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Boxes.dev supplies permissioned tools for agents to create workers, inspect threads, send messages and continue work. Agent-created devboxes are grouped under their creator. A universally available dedicated Coordinator role and automatic result acceptance remain unestablished.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium orchestrates delegation itself: podium agent spawn starts a full child session on an issue with a chosen harness, model, effort or agent profile, mail carries messages, and bounded await reports the child result. Children are real sessions shown as seats on the flight deck. Agent-initiated spawns take a daily budget per issue. A complete delegated task with retained child findings was not run.

### COORD-04: Unattended triggers

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Vendor-owned automations run on recurrence, API or integration events without a prompt for each run. Capacity, overlap and delivery statuses have explicit limits and are distinct from agent completion.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The server owns a scheduler for cron and one-time automations that spawn agent sessions, skipping overlaps and not backfilling occurrences more than an hour late. The Automations UI is an edge-visibility feature that defaults off and docs list automations as non-baseline. Agents can subscribe to issue and session events.

### COORD-05: Intervention and attention

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Users can steer, queue, stop and continue agents, answer requests and receive alerts across devices. Stopping a response preserves queued follow-ups, which may start next; sleeping pauses the whole machine.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Chat and native CLI views share a session. v0.3.0 defaults human controller chat to steer and immediately types it into running Claude Code, Codex, Grok and OpenCode TUIs that declare native busy-input queuing; undeclared harnesses wait for a boundary, and compaction waits. Mail and automation keep when-ready delivery. Stop, resume, questions, decision issues and offers remain available. This is inspected implementation, not a cross-harness runtime parity result.

### COORD-06: Fleet and epic management UI

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. The workbench groups threads by devbox, folders and creator, with work/unread/input indicators and searchable history. This is a fleet view of sessions, not established evidence of native epic dependencies or a measured multi-epic fixture.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Release 0.3.0 ships a flight deck showing a whole mission in one view: phases, every task and its state, who works on what, what is blocked and by what, and proposals. Done work stays visible. The CLI prints the same snapshot. The waterfall source is dormant and the Timeline view was deleted, so per-task timeline history is not shown. The shared 12-task UX scenario has not been run.

### COORD-07: Workflow flexibility and orchestration visibility

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. A simple prompt starts ordinary work, while goals, automation settings and per-thread agent controls support longer workflows. Agents may create workers through explicit grants; a complete epic/Coordinator workflow is not established.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. A quick task can be an interactive session or an issue; an issue can grow into a mission by gaining children while keeping its identity; no mandatory workflow preset applies in the baseline. Per-agent harness, model and effort are chosen at spawn or through agent profiles, and the deck shows seats. The coordinator-with-two-reviewers scenario was not run.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Ordinary Boxes.dev coding work runs on vendor-managed Linux devboxes and continues after client disconnect. Local agents may prepare the initial upload, but those setup scans do not establish general local execution. Customer-hosted deployment remains a sales discussion.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. The published Podium execution choices are local user machines and a user-owned VPS or paired machine. No vendor-operated agent host is in the complete download offering.

### RUN-02: Workspace and process isolation

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. A separate devbox isolates its own files, processes, local databases and ports. Several threads on the same devbox share those resources; shared project storage and external services intentionally cross machine boundaries. No hostile-code boundary or VM implementation is inferred.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium separates issue files with Git branches and worktrees, but its released daemon launches native host processes without product-managed container or VM provisioning.

### RUN-03: Recovery, expiry and continuity

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Client reconnect and sleep preserve conversation/machine state, while Reset kills processes and Reboot loses memory. Snapshot recovery can restore older state and shows a notice. These mechanisms do not guarantee lossless task recovery after infrastructure failure.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Closing a browser tab does not stop the agent process on a running Podium host. Idle sessions may hibernate under configurable policies; a stopped session keeps its transcript, branch and resume reference. Release 0.2.0 says a failed update rolls back and running sessions keep running through the upgrade; database rollback remains a manual restore. Terminal reattachment goes through the driver adopt contract with process-identity and observation-lease checks. Worker-crash and multi-day behavior were not tested.

### RUN-04: Development environment reliability

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Prepared template snapshots copy dependencies and services to fresh devboxes, with lifecycle scripts and managed environment values. Per-box ports avoid local collisions; external shared systems still require deliberate setup.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Only machine setup is documented: the installer installs missing runtime tools and pairs a host, and the state directory holds server-managed secrets. Dependency caching, services, ports and automatic repair for project environments were not found.

### RUN-05: Limits and failure handling

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Limits include per-user awake capacity, billing/credit blocks, provider quotas and goal budgets. Background protection and command timeouts differ by harness; they are not a universal task budget.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium exposes retryable errors, optional auto-continue with backoff, bounded waits and provider quota. Claude stream and hosted headless drivers enforce a supplied turn deadline, with no deadline when timeoutMs is absent. The one-shot headless server runner supplies its budget, default ten minutes. Agent spawns have a daily per-issue budget. Operator-configurable task-wide turn, token and spend caps remain unestablished; quota display is not enforcement.

### RUN-06: Truthful status and operational statistics

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Thread activity, machine resource meters, usage charts and automation launch reasons expose operational state. Launch Ready and an idle agent do not prove a task delivered its result.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Podium offers local logs and crash export, structured session status, issue stats, a usage and analytics sheet with hourly list-price cost, per-task costs and host load panels. The 0.3.0 notes report a vendor benchmark of about 330 MB server memory against about 1.2 GB for an earlier Podium build, and 8 to 52 percent faster start; the method is published in the repository and was not reproduced here. Usage export and cross-reconnect consistency were not established.

### RUN-07: Per-task API and compute cost

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Boxes.dev separates per-thread token/provider quota charts from hourly machine box-hour history. Those measurements are not a reconciled per-task dollar bill and do not establish child/epic cost aggregation.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Since 0.2.0 Podium shows what each task costs, on the task header and the usage sheet, with per-session rows and descendant rollups. The 0.3.0 deck adds a mission cost chip. Figures are token estimates at public model list prices, not subscription invoices or provider bills.

### RUN-08: Compute-aware scheduling and verification

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Per-user awake-devbox caps and fixed machine resources constrain compute. Scheduled capacity retries and idle-machine sleep are configurable, with skipped overlaps. No shared verification deduplication or fairness guarantee is established.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium reports host memory, load and disk, auto-hibernates idle sessions under pressure, and provides named advisory resource leases. The merge-queue panel was removed; a shipping queue remains behind the Shipping flag. Concurrency limits and bounded test queuing were not established.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Shared workbench links are read-only, but an owner can authorize linked teammates to send instructions to the same agent through Slack. This route uses the owner's credentials and compute allowance, identifies each sender and applies owner-selected Steer/Queue behavior. Both users need active membership in the same team and linked Slack accounts.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The issue UI displays owner and visibility read-only and deliberately omits sharing controls. Backend share handlers and a Members settings section with invites and admin or member roles exist; they do not establish a finished human collaboration workflow. Docs say small teams can share an instance but the interface prioritizes one operator.

### TEAM-02: Roles and access boundaries

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Documented Admin and Member roles separate template, membership, integration and billing rights. Personal credentials remain per member. Enterprise SSO/SCIM are advertised separately from these documented controls.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Podium defines member/admin instance roles and admin-only membership management. The released client authentication uses password-backed sessions and paired-device tokens without enterprise SSO.

### TEAM-03: Approvals and temporary access

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Product permissions gate worker, messaging and settings operations, while harness modes govern commands/edits. Temporary grants and public preview revocation have documented lifetimes; neither is a general deployment approval system.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Agent-session management requests go through an operator approval broker with approve and deny; the privacy docs say lifecycle commands and automation requests may require operator approval. Harness permission prompts appear as a Permission needed state; credential copying during pairing is a per-grant opt-in. Command-level policy enforcement beyond the harness own modes was not established.

### TEAM-04: Decision and activity history

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Conversation history, attributed teammate-agent messages and automation launch settings retain useful context. Copy transcript exports Markdown. The public sources do not establish an immutable audit log with retention and integrity guarantees.
- **Podium**: Sourced (sourced); support: partial. Checked 2026-11-06 (16 days old); not separately cross-checked. Issue actions, approval steps, comments and mail are recorded server-side. Issue activity events, including approval steps, are pruned by the server's janitor once they are older than 14 days or fall outside the newest 50,000 rows. That policy does not define all content retention, export or tamper-evident audit guarantees.

### TEAM-05: Review experience and guidance

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Git/Review and Files guide review through changed files, line/range comments and a single feedback batch. Mobile review and keyboard shortcuts are documented; exact-revision approval and measured review quality are not.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Review is a documented loop: issue stage review, diff and checks, artifacts, offers with merge or send-back buttons, and a Tray of review-ready work. Release 0.3.0 adds quoting text from a reply or review finding into the next message and a full-height reading view with an outline. The board has a key map with a help sheet. Guided-review quality and narrow-screen use were not measured.

### TEAM-06: Colleague takeover and continuity

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. An idle owned thread can be transferred to a teammate with compatible project code. History and packaged changes arrive on a new devbox using the recipient's credentials. This preserves conversation context but is not live runtime takeover.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The durable issue, session transcript, artifacts and mail persist for any later agent, and a live session can be handed to another machine in an edge feature. Colleague takeover by a second person was not established.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Threads can retain diffs, attached files, screenshots and published media, while Files and previews expose machine outputs. Download or push work before destroying the devbox; archived conversation alone does not retain its filesystem.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. Artifact commands store immutable server-side copies of issue-linked files, including images, video, HTML and documents, which render in the issue sidebar and offers and stay readable after the worktree is gone. Each task has an artifacts page grouped into screens, documents and reports, with filters and search. Revision linking remains untested.

### SHIP-02: Verification and spec gates

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. The guides ask users to request tests and review results. Git UI blocks commits with unresolved conflicts and pull-and-push requires a successful pull; these controls do not establish mandatory test, spec or independent-review gates.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. In the experimental Shipping path a configured validation profile runs before landing (default argv bun run test with a 10 minute timeout) and a failed validation holds the order. Lint, type, CI and spec conformance gates and independent review requirements were not found as product-enforced policy.

### SHIP-03: Git and pull request workflow

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Git/Review integrates staging, commits, branches, pushes and GitHub pull requests. Optional follow-ups handle failed checks, review feedback and conflicts, with explicit pause and owner-routing rules.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Issues own branches and worktrees, and issue actions rebase, open a pull request with gh (pr create --fill) and merge, subject to a merge-style setting (ff-only by default, with auto-rebase before merge). Podium does not resolve branch conflicts, and PR review comments and CI response were not established.

### SHIP-04: Merge and deployment authority

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. The workbench can merge a GitHub pull request with the connected user's permissions and supported GitHub merge rules. PR creation, merging and production deployment remain separate; no general product release/deploy authority is established.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The operator accepts work through offers and runs the merge action under a branch merge-lock; in the experimental Shipping path approval is frozen to an exact head and delivery lands on a local target branch by default. Release and deployment are not product features found in the sources.

### SHIP-05: Completion evidence and rollback

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Optional commit trailers connect changes to their originating thread, and PR follow-ups retain the responsible conversation and merged notice. The UI can revert selected edits. Build/deploy receipts and stale approval invalidation remain unknown.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Shipping orders record approved base and head SHAs, tested integration SHA, landed ref and validation result in a durable delivery receipt, and stale approvals hold the order. Shipping is experimental. The pr action records a PR URL on the issue. Build and deployment links and rollback were not found.

### SHIP-06: Batch review and high-volume shipping

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Folders and thread/devbox groups help organize completed work, while file/diff feedback can be batched per thread. There is no established dependency-aware merge queue or exact-revision approval workflow in the checked public sources.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-07. The shipping service records revision-specific approval, configured validation and delivery receipts. The Shipping panel is an experimental edge toggle, off by default; the separate Queues panel was removed.

## Ownership, privacy and economics

### OWN-01: Source and license

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Boxes.dev is a vendor cloud service under custom service terms. Public CLI packages are readable but marked UNLICENSED; no public full application/server repository or upstream Git commit was established. Visibility of a distribution does not make the product open source.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. The public repository is licensed Apache 2.0, and the website presents Podium as an open-source agent development environment. Hosted extensions and hosted-service terms are not established.

### OWN-02: Hosting and exit

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Code/files can be downloaded or pushed, user/final-agent transcript messages copied as Markdown and native local threads imported. A vendor-independent full ADE or complete portable account export is not established.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-11. Local desktop and self-hosted installs run on user-controlled machines with a documented state directory. The docs describe stopped full-state backup and automatic pre-migration database-only snapshots retaining three copies. Those snapshots omit artifacts, transcripts, uploads, configuration and secrets; no portable structured export/import contract was established.

### OWN-03: Data handling and telemetry

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Code, prompts, credentials and history reach managed machines and selected provider services. Analytics, crash logs and masked replay are disclosed. Some retention/deletion behavior is explicit; general training exclusions, fixed backup expiry and telemetry opt-out remain unknown.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-21. Docs state repositories and native harness credentials stay on machines you control and server state lives in a documented directory. Since 0.2.0 a daily usage report is on by default and can be turned off; crash reports stay opt-in. Usage reports carry an install id, schema version, Podium version, OS, architecture, bucketed install age and machine count, session counts per harness and whether issues were used. Crash reports carry the same install id, versions, OS and architecture, a fixed error type and up to 20 stack frames, each with a Podium source file path, line and function when there is one; error messages and frames outside Podium are dropped. Neither tier sends prompts, transcripts, your code or paths outside the Podium source tree. Model-provider handling is the harness own. Hosted analytics and website analytics are separate paths.

### OWN-04: Price and included usage

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Managed compute costs USD 19/99/249 per paid seat/month on Starter/Pro/Max, including 50/300/750 box-hours. Trial is 20 hours. Paid overage is USD 0.40 per standard box-hour before discounts; agent subscriptions/API costs remain separate.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. No Podium price is published: podium.do/pricing returns 404 and the docs list billing as not implemented. The software is open source and free to download; model and compute costs are the user's own.

### OWN-05: Scenario cost and controls

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Illustrative monthly Starter workload: each developer completes 10 tasks on a standard devbox for 4 awake hours each, with at most 2 awake work boxes and 10 total awake template hours, for 50 box-hours/person. One person pays USD 19, two collaborating people USD 38 and five USD 95 before provider charges/taxes. This is an input scenario, not measured task cost.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-06: Availability and support

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Current public docs and store distributions offer account-based access and a finite self-serve trial. Official release 1.0.1135 is dated 2026-11-19. Android still describes early-access/waitlist accounts; signup eligibility was not tested.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is pre-1.0. Stable v0.3.1 (2026-11-06), an update fix, follows v0.3.0 (2026-11-05), v0.2.0 (2026-10-11) and v0.1.0 (2026-08-21), with edge and dev prerelease channels. Windows and Linux desktop are Experimental, the native iPhone app is in private beta and hosted Podium is unconfirmed. Support runs through GitHub issues, Discord and private vulnerability reporting.

### OWN-07: Enterprise assurance

- **Boxes.dev**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.

### OWN-08: Useful free tier and evaluation access

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Evaluation uses a finite 20-box-hour per-user trial, not an established ongoing free compute plan. It includes connected-agent access and limited cloud capacity; after trial expiry/exhaustion, a paid seat is required to start or wake machines.
- **Podium**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-06 (16 days old); agent cross-checked 2026-11-06. Podium is open-source Apache-2.0 software, and the download page calls it free and open source. Download links for macOS, Linux and Windows redirect to GitHub release assets without a login (observed by HTTP requests; not installed). No Podium charge is documented for self-hosting; agent provider usage is separate. The native iPhone app is private beta and hosted access is unconfirmed.

### OWN-09: Pricing transparency

- **Boxes.dev**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-21 (1 day old); agent cross-checked 2026-11-21. Self-serve pricing is partially specified: monthly seat rates, box-hour units, allowances and overages are public. Agent costs are separate, enterprise terms require a quote and cancellation wording differs between help and the posted order form.
- **Podium**: No sourced public finding (not-published); support: not-published. No publishable sourced finding is available for this criterion. This does not mean the product lacks the capability.
