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

# Podium vs Sno Station

> 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

48 criteria sourced for both products; 36 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.

- Podium source checks: 2026-11-06. Details: https://podium.do/compare/agents/products/podium/index.md
- Sno Station source checks: 2026-11-16. Details: https://podium.do/compare/agents/products/sno-station/index.md
- Rubric: https://podium.do/compare/agents/rubric/index.md
- Canonical HTML: https://podium.do/compare/agents/podium-vs-sno-station/
- Machine-readable JSON: https://podium.do/compare/agents/podium-vs-sno-station/data.json
- Methodology: https://podium.do/compare/agents/methodology/

## Access and agent choice

### ACC-01: Client access

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Command-line product: the sno CLI, Reach and skills run on Linux (x86-64, ARM64), macOS (Intel, Apple silicon) and WSL2 and operate inside Claude Code, Codex, Cursor, Hermes Agent and OpenClaw. sno squad is a full-screen terminal view; Claude Code and Cursor status lines and a tmux bar show who needs you. A hosted sno.ai dashboard exists for the account (closed). No desktop GUI, native Windows, mobile apps or browser work client.

### ACC-02: Agent and model choice

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sno Station embeds no harness. It installs memory, skills and Reach into five third-party harnesses (Claude Code, Codex, Cursor, Hermes Agent, OpenClaw), launches their terminal commands in tmux or ACP seats, and runs mixed-vendor pairs. Model choice belongs to each agent; Self Learning/REM engines have their own model setting.

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

- **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.
- **Sno Station**: Sourced (sourced); support: partial. Checked 2026-11-16 (6 days old); not separately cross-checked. Agents run under the user's own subscriptions or keys; sno subscription-quota-check reads Codex and Claude Code quota without spending it and Cursor optionally. Sno itself has a free account with weekly allowance and a dollar balance for its hosted memory/Self Learning engine, or can use the user's own agent mode when that is used up.

### ACC-04: Onboarding and project prerequisites

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. One line (curl -fsSL https://sno.ai/install | sh) or telling an agent "install sno.ai from GitHub" installs sno and sets up Sno Station for every agent found; then onboarding asks which engine and whether to link a free account. Works on any folder the agents can use; timed tasks need a once-a-minute user service (Homebrew packages on macOS). No managed cloud or VPS installer.

### ACC-05: Programmable access

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Every command accepts --json and agents drive Sno through the sno CLI, Reach (cards, rings, inbox) and installed skills; there is no network API, SDK, MCP server or webhook for control. The memory service exposes a local sidecar to the plugins.

### ACC-06: External tools and extensions

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sno is not an MCP client: it installs hooks, skills, a Claude plugin and memory plugins into each harness, which supply their own MCP/tool connections. Skills (39) are the extension mechanism; instruction import is the skills themselves.

### ACC-07: Client implementation

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Terminal tooling: shell scripts and a Rust receiver for Reach (apps/reach/net), TypeScript/Node memory service and observability packages, a Rust sno launcher (closed source) and tmux; no desktop or mobile GUI.

## Planning and context

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Tasks start from a prompt to an agent, sno reach pair "task", Agent Email task cards, timed tasks written next to progress records, or a charter/work order from the pl/charter skills; there is no tracker import or sync.

### PLAN-02: Durable task plans

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The charter skill writes a task charter with success checks, deliver-proof records real-run answers to each check and handoff-checkpoint writes a verifiable progress record; documents are files edited by agents. No plan editor UI or revision history beyond files/git.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The chief-of-staff model gives a hierarchy of owner > COS > project leads (PL) > up to five executors, each owning one charter; there are no task dependencies, epics or readiness states in a product data model, and work-order steps are sequential skill conventions.

### PLAN-04: Shared context and memory

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Strongest area: one encrypted local memory shared by all five harnesses (remember/recall/correct, retiring replaced facts), per-harness hooks that add context to prompts, 39 shared skills and nightly Self Learning that proposes skill changes a human accepts. Modes: local-first, agent-native, rem-enhanced (cloud processing).

### PLAN-05: Architecture and API awareness

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Memory recall injects up to three relevant items per prompt and a short repository brief per chat; embeddings and chunking packages exist; there is no code index, architecture check or external knowledge connector.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No native issue or idea backlog: work lives in charters, Reach cards, progress records and each agent's own conversation.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agents exchange tasks as Reach cards and Agent Email with accepted/completed/failed replies and use progress records, but no durable issue IDs or fields shared with a human view exist.

### PLAN-08: Living product specifications

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No living product-specification feature: memory and charters are not maintained requirements with drift checks.

## Coordination and automation

### COORD-01: Parallel work

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Multiple agent seats run concurrently as tmux windows or ACP sessions (reach pair starts two; chief of staff runs up to five executors per project lead); sno squad shows needs-you/working/finished across local agents.

### COORD-02: Ownership and dispatch

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Work is assigned by sending a task to an agent address; Reach transfer cards give one current owner; peer-review rounds are capped; no queues, routing rules or enforced exclusive claims beyond a seat lock.

### COORD-03: Inspectable delegation and communication

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Product-supplied coordination: sno reach pair starts an implementer and an independent reviewer who settle findings; the /cos Chief of Staff skill delegates to project leads and executors over Reach with inbox, rings and sentinels; call waits for replies, send leaves tasks. Roles are skills on third-party harnesses; no built-in coordinator model.

### COORD-04: Unattended triggers

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Finish timed tasks start an agent at a named time (once, daily, weekly) via a user-level once-a-minute service; heartbeat watches long runs; Self Learning runs nightly; timed tasks start Claude Code and Codex only; no event triggers.

### COORD-05: Intervention and attention

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Humans steer in each agent's own window; sno squad flags agents needing approval or answers; the status line and tmux bar say who needs you; rotate-agent hands over before quota ends; no pause primitive.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. sno squad (full-screen or JSON) lists agents grouped as Needs you, Working and Finished with project, task text and age; work discovery follows Reach headers; no epics, dependency graph or workload analytics.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No mandatory workflow: say a task to an agent, run pair, or use /cos for the full chain; natural language is the interface through skills; per-seat vendor and model can be chosen; the UI is terminal text and sno squad.

## Execution and reliability

### RUN-01: Laptop-independent execution

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Everything executes on the user's own computers (local tmux/ACP seats); agents on other machines can message each other over LAN or Tailscale when each runs Reach; timed tasks need the computer on. Sno operates no compute; the hosted account only provides allowance/dashboard.

### RUN-02: Workspace and process isolation

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Seats are separate tmux windows in the same folder with approval prompts off; the chief-of-staff procedure requires exactly one linked git worktree per executor by default; no containers, VMs or OS sandbox of its own.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Interrupted work resumes in the same conversation, a rebuilt one from the saved brief, or is reported lost; messages wait for an agent that was cut off; handover on quota exhaustion; timed tasks stay due until started; a full computer restart has not been through a real test.

### RUN-04: Development environment reliability

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sno does not manage workspace dependencies, caches, services, ports or secret injection for agent work; e2e-environment-preflight and medic are checks only.

### RUN-05: Limits and failure handling

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. peer-review has hard round caps (3 code, 5 plan, 1 tests) and kills runs idle for 15 minutes; rotate-agent triggers at 2% quota; development tasks carry wall-time budgets in skills; no spend or token limits enforced by the product.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Local observability events (scrubbed) with consent levels, sno station export/audit, doctor and medic, sno stats (allowance, review catches, lessons, memories), away-brief and catch-report; usage dollars/allowance for Sno's own service; no per-agent token/cost statistics.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. sno subscription-quota-check shows remaining subscription quota without spending it and sno usage shows Sno's own allowance and balance; no per-task/session API spend; subscription marginal cost is not shown as zero.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Few resource controls: COS caps five executors per PL, one seat spawn lock per address, medic checks free space; no CPU/RAM scheduling, queues or check reuse.

## Human collaboration and control

### TEAM-01: Live human collaboration

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Single-owner tool: agents collaborate with each other, not multiple humans; no shared sessions, comments, presence or co-prompting among people.

### TEAM-02: Roles and access boundaries

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No organization, roles, SSO or provisioning; the optional hosted account is individual.

### TEAM-03: Approvals and temporary access

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Approvals are the harness's own; Sno surfaces waits in sno squad, defaults pair seats to approval prompts off, writes nothing to permissions for timed runs, and offers consent levels for what leaves the computer.

### TEAM-04: Decision and activity history

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Local hash-chained observability events with consent.change audit events, exportable and checkable with sno station audit; Reach mail threads; no user attribution beyond the owner and no immutability promise beyond the hash chain.

### TEAM-05: Review experience and guidance

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Review is agent-to-agent: peer-review sends work to a different agent in a fresh session, findings are filed once in a ledger with human-set status, and away-brief summarises for the owner; there is no diff or PR review UI.

### TEAM-06: Colleague takeover and continuity

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Agent takeover is first class (handoff with exact commit, rotate-agent, take-over by another agent from a progress record); human takeover by another person is not a documented feature.

## Verification and delivery

### SHIP-01: Retained artifacts and outputs

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Retained outputs are Reach mail threads, progress records, review findings ledgers, away-brief pages, deliver-proof records and optional evidence folders; no gallery, screenshots, recordings or previews.

### SHIP-02: Verification and spec 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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Checks are skill conventions: "done" counts only when each charter success check is answered by a real run (deliver-proof check), peer-review is required review by a different agent with round caps; no CI or lint gates enforced by product code.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Sno does not manage branches, commits, pull requests or CI itself: agents run git; COS rules describe worktree and merge procedure.

### SHIP-04: Merge and deployment authority

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No merge, release or deploy authority features; "It delivers. You ship." (README).

### SHIP-05: Completion evidence and rollback

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Handovers record exact commits and deliver-proof records command results per charter step; away-brief reports done/stuck/waiting; no PR, build or deployment links, rollback or revert features.

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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: unsupported. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. No batch review/delivery queue: one-page away-brief and catch-report summarise outcomes, but there is no queue, risk filters or exact-revision approvals.

## Ownership, privacy and economics

### OWN-01: Source and license

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. sno-station (memory, Reach, heartbeat, docs) and sno-station-skills are Apache-2.0 public repositories; the sno CLI launcher is distributed as binaries with the statement "The source is not public" although released under Apache-2.0; the sno.ai hosted account/engine is closed.

### OWN-02: Hosting and exit

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Core runs on user machines with a locally encrypted memory store and local exports; a Sno account is optional but unlinked computers get a tenth of the free allowance; hosted REM and Self Learning engines require Sno cloud unless the user's own agent mode is used; sno station export saves events; memory export files are encrypted.

### OWN-03: Data handling and telemetry

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Memory stays local and AES-256 encrypted; consent levels off/metadata-only/full control uploads (CLI README says full is the default, the observability package says metadata-only); REM Enhanced and default Agent Native upload memory text/sessions to the user's space in Sno cloud; logs are content-free; model prompts go to the user's providers; Sno states it does not receive the database or key.

### OWN-04: Price and included usage

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The software is free open source; the hosted Sno engine gives a weekly free allowance (a tenth until the computer is linked) then a dollar balance; prices, currency, interval and trial terms are not published in the repositories or site pages checked.

### OWN-05: Scenario cost and controls

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. The open-source tooling costs nothing; hosted allowance beyond free and the agents' own subscriptions or API costs cannot be priced from public data.

### OWN-06: Availability and support

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Public since 2026-09-18, rapid releases (2.0.0 on 2026-11-04, 2.0.2 on 2026-11-16), GitHub issues and design-partner template, security@sno.ai for vulnerabilities; no response-time commitments or status page.

### OWN-07: Enterprise assurance

- **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.
- **Sno Station**: 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

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Open-source download and a free sno.ai account; local use needs no payment; a weekly free hosted allowance applies; agents and compute are separate; no card requirement documented.

### OWN-09: Pricing transparency

- **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.
- **Sno Station**: Agent cross-checked (agent-cross-checked); support: partial. Checked 2026-11-16 (6 days old); agent cross-checked 2026-11-17. Partially specified: free allowance and a dollar balance exist (sno usage), but units, limits, overage rates and minimums are not published.
