# Amp

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. The same evidence rules apply to Podium and its competitors, but they do not remove this conflict of interest.

Page: https://adecomparison.com/ade/amp/
Website: https://ampcode.com/manual
Research: covered

Method: https://adecomparison.com/method/

Rank by must-haves met, then preferences, then name. Read each finding's checked date. Findings stay published after their scheduled recheck. Checks over six months old may be outdated.

## amp:ACC-01

Finding: Amp offers Mac, experimental Windows and native Linux desktop apps, native phone apps, the web app and CLI. Linux includes a local systemd runner; individual client limitations remain scoped per question.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: mobile_browser, editor_extensions. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs
Locator: Quickstart; Explore
Finding: Amp offers web, macOS, iOS, Android and CLI access to threads; Orbs keep working after closing the laptop.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/apps/windows
Locator: Install; What Works
Finding: Experimental Windows 10 1809+/Windows 11 app for x64 and Arm. Threads and orbs, Windows notifications and taskbar actions are documented.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/apps/linux
Locator: Linux app installation, local runner, tray and differences from Mac
Finding: Amp has a native Linux desktop app with install instructions, desktop integration and a systemd-backed local runner. It supports tray operation and launch arguments; the Linux app lacks Mac Puck windows/dictation and multiple windows.
Retrieved: 2026-11-13

## amp:ACC-02

Finding: Amp supplies its own coding-agent harness across clients and builds prompts/tools around the selected model. Custom agent modes and subagents remain Amp agents; provider subscriptions or models are not third-party coding CLI integrations.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Agent and model choice: first-party sources in this pass did not establish harnesses, custom_adapters, session_integration, mixed_harness_operation. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.

Source: https://ampcode.com/docs/models-and-subagents
Locator: Subagents; Custom agents
Finding: Task and Read Thread subagents have separate context, report summaries and support follow-up work. They cannot communicate directly with one another.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/markdown/models-and-subagents
Locator: Introduction same agent everywhere; Models and Subagents main agent, custom agents and system models
Finding: Amp uses its own agent across web, apps and CLI. The selected model is wrapped in Amp system prompts/tools; Task and Read Thread are Amp subagents. Custom plugin agents choose a model through amp.createAgent rather than selecting a third-party coding CLI harness.
Retrieved: 2026-11-13

## amp:ACC-03

Finding: The pricing guide supports linking ChatGPT and Claude subscriptions. BYOK is a separate inference route. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Subscriptions, API keys and vendor credits: first-party sources in this pass did not establish local_models, account_switching, vendor_account_requirement, provider_restrictions. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

## amp:ACC-04

Finding: The quickstart permits a project without a Git repository. Orbs support GitHub and other HTTPS Git hosts; GitHub private access uses an installed GitHub App.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Onboarding and project prerequisites: first-party sources in this pass did not establish first_task_setup, local_git_without_remote, prerequisite_guidance, managed_cloud_setup, byo_vps_onboarding. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.

Source: https://ampcode.com/docs
Locator: Quickstart; Explore
Finding: Amp offers web, macOS, iOS, Android and CLI access to threads; Orbs keep working after closing the laptop.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/github
Locator: Connection; PR status; GitHub webhooks
Finding: A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.
Retrieved: 2026-11-07

## amp:ACC-06

Finding: Local commands and remote MCP servers are supported. Remote servers can use OAuth or configured headers. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

External tools and extensions: first-party sources in this pass did not establish plugins, custom_tools, instructions_import, integration_owner. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.

Source: https://ampcode.com/docs/collaborate/multiplayer
Locator: Activate multiplayer; Security; MCP servers
Finding: Workspace members can co-prompt an enabled thread and access its Orb or shared runner; access is time-limited and bills the owner.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/customize/mcp
Locator: Local and remote configuration
Finding: Amp manages local and remote MCP definitions with OAuth or headers; no external-tool call was tested.
Retrieved: 2026-11-07

## amp:PLAN-01

Finding: GitHub webhooks can continue threads or spawn Orbs from issues and pull requests.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Intake and external tracker relationship: first-party sources in this pass did not establish local_creation, prompt_intake, external_import, authoritative_tracker, stable_ids, sync, supported_edits, external_roundtrips. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.

Source: https://ampcode.com/docs/github
Locator: Connection; PR status; GitHub webhooks
Finding: A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.
Retrieved: 2026-11-07

## amp:PLAN-02

Finding: Thread artifacts can hold plans and checklists, persisted with the thread. This does not establish acceptance gates. Humans and agents edit the same artifact. Each artifact save creates a revision. Agents merge against a newer artifact revision when a concurrent save prevents their update.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: acceptance_criteria, implementation_links, restart_persistence. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

## amp:PLAN-04

Finding: Amp loads AGENTS.md in the current directory, parents and relevant subtrees, plus personal and system guidance. Workspace global guidance applies to top-level agents, with explicit exclusions for subagents, Puck and raw custom agents.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Shared context and memory: first-party sources in this pass did not establish skills, project_docs, memory, provenance, correction, deletion, freshness, takeover_continuity. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.

Source: https://ampcode.com/docs/customize/agents-md
Locator: Automatic inclusion; global guidance
Finding: Repository, personal and managed guidance has documented inclusion scopes; workspace guidance excludes subagents, Puck and raw custom agents.
Retrieved: 2026-11-07

## amp:PLAN-08

Finding: Artifacts can retain a plan or requirements document with a thread; a dedicated executable requirements schema is not established. Workspace users allowed to open the thread can edit its artifacts. Every selectable agent mode can read and write artifacts using the artifact tool. Every artifact save creates a new revision. Artifacts remain accessible from the thread Artifacts view until deleted.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: approvals, implementation_links, drift_detection, review_integration. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

## amp:COORD-01

Finding: The Orb guide describes several independent tasks running at once, each with its own environment.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Parallel work: first-party sources in this pass did not establish concurrent_sessions, quotas, observed_concurrency, status_visibility. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.

Source: https://ampcode.com/docs/orbs
Locator: Orb spawn pacing; review; follow along
Finding: Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.
Retrieved: 2026-11-07

## amp:COORD-03

Finding: Task executes delegated work and Read Thread summarizes threads. Built-in Task subagents follow the thread's model and effort; custom plugin agents can define model choices. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Inspectable delegation and communication: first-party sources in this pass did not establish cross_harness, orchestration_owner, activation, authentication, live_progress, retained_results, followup, invocation. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.

Source: https://ampcode.com/docs/models-and-subagents
Locator: Subagents; Custom agents
Finding: Task and Read Thread subagents have separate context, report summaries and support follow-up work. They cannot communicate directly with one another.
Retrieved: 2026-11-07

## amp:COORD-04

Finding: Amp saves one schedule per thread; it can run once or repeat, with pause, resume and delete controls. GitHub events can wake existing threads or start new Orbs. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unattended triggers: first-party sources in this pass did not establish recurring_tasks, overlaps, retries, client_independence. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.

Source: https://ampcode.com/docs/github
Locator: Connection; PR status; GitHub webhooks
Finding: A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/automations
Locator: Automations; Manage an automation
Finding: A saved thread schedule wakes the same agent and Orb; one-off, recurring and completion-conditioned runs are documented.
Retrieved: 2026-11-07

## amp:COORD-05

Finding: A snoozed thread surfaces and notifies when it needs an approval or answer.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Intervention and attention: first-party sources in this pass did not establish pause, stop, resume, steer, pending_decisions, escalation, visible_errors, chat_terminal_parity, retained_history. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.

Source: https://ampcode.com/docs/orbs/automations
Locator: Automations; Manage an automation
Finding: A saved thread schedule wakes the same agent and Orb; one-off, recurring and completion-conditioned runs are documented.
Retrieved: 2026-11-07

## amp:COORD-07

Finding: The Dial provides low, medium, high and ultra modes; plugins can define custom agents.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Workflow flexibility and orchestration visibility: first-party sources in this pass did not establish quick_task, growing_epic, presets, natural_language, in_run_changes, live_roles, retained_relationships, discoverability, auth_friction. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.

Source: https://ampcode.com/docs/models-and-subagents
Locator: Subagents; Custom agents
Finding: Task and Read Thread subagents have separate context, report summaries and support follow-up work. They cannot communicate directly with one another.
Retrieved: 2026-11-07

## amp:RUN-01

Finding: The CLI can run Amp on the user's own machine. Users can supply their own Orb compute through amp orb provider and a dispatch program. Orb execution can be hosted on user infrastructure; this is not self-hosting the Amp control plane. Orbs are per-thread machines that continue working when the laptop closes. The size table lists per-Orb CPU, memory and 60 GB disk; default-size rules vary by project and plan.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: hybrid, provisioning, payer, region, expiry, client_disconnect, other_device_continuation. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs
Locator: Quickstart; Explore
Finding: Amp offers web, macOS, iOS, Android and CLI access to threads; Orbs keep working after closing the laptop.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/sizes-and-costs
Locator: Available sizes; Billing; When an Orb pauses
Finding: Hosted sizes and hourly rates are published and billed by minute; idle pause stops charges. Enterprise self-hosted pricing changes after November 13.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/self-hosted
Locator: How It Works; Caution; infrastructure table
Finding: An outbound provider runs user-supplied spawn/pause/delete dispatch. Docker and Kubernetes examples retain disk but not memory. Self-hosted Orbs still connect to Amp.
Retrieved: 2026-11-07

## amp:RUN-02

Finding: Runner worktree creation also creates a named branch. A runner creates a Git worktree and branch for a new thread; worktrees separate files without asserting a security sandbox. A documented Docker provider example runs each Orb as a container; this is a self-hosted execution option. Each Orb thread has a fresh isolated working environment; the shared terminal uses the same filesystem as that thread's agent. Docker-backed Orbs do not preserve memory across pause; terminals and desktop processes are lost on wake. Each runner worktree has its own working files and branch.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: checkout, vm, os_sandbox, network, secrets, security_boundary. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs
Locator: Orb spawn pacing; review; follow along
Finding: Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/self-hosted
Locator: How It Works; Caution; infrastructure table
Finding: An outbound provider runs user-supplied spawn/pause/delete dispatch. Docker and Kubernetes examples retain disk but not memory. Self-hosted Orbs still connect to Amp.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/cli/runners
Locator: Start a Runner; Create a Worktree
Finding: Runners serve local or remote directories. New Worktree creates a sibling checkout and branch; threads can archive and remove only clean worktrees.
Retrieved: 2026-11-07

## amp:RUN-03

Finding: Docker-backed Orb services restart when a portal is reopened after wake; terminal and desktop process state is not restored. An idle Orb wakes with conversation, files and services retained; worker-crash recovery was not tested. Docker-backed Orbs retain disk but lose terminal and desktop process state when paused.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: client_disconnect, worker_crash, expiry, transcript_reload, process_reconnect, state_reconstruction, duplicate_actions, manual_repair, multi_day_continuity. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs
Locator: Orb spawn pacing; review; follow along
Finding: Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/self-hosted
Locator: How It Works; Caution; infrastructure table
Finding: An outbound provider runs user-supplied spawn/pause/delete dispatch. Docker and Kubernetes examples retain disk but not memory. Self-hosted Orbs still connect to Amp.
Retrieved: 2026-11-07

## amp:RUN-04

Finding: Install shared dependencies in .agents/setup. A matching prepared project snapshot is reused for up to 72 hours. Snapshots capture repository and setup changes and can be deleted from settings or CLI. Long-running processes belong in .amp/services.yaml or systemd, not setup. Shared setup and runtime use different credentials; setup credentials are removed before snapshotting. A matching project snapshot skips setup; freshness is limited to 72 hours and supported Git host checks. .agents/resume runs after activation and wake for authentication, repair or reconnect; successful automatic repair is not independently tested.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: ports, collisions, remote_setup. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs/customizing
Locator: Orb Lifecycle; .agents/setup; .agents/resume; Services
Finding: Project snapshots reuse dependencies up to 72 hours. Setup and resume scripts have distinct credentials and lifetimes. Services are declared separately; failed setup is visible in Setup Log.
Retrieved: 2026-11-07

## amp:RUN-05

Finding: Setup stops after 20 minutes; a failed or timed-out setup does not publish a refreshed snapshot.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: time_limits, turn_limits, token_limits, spend_limits, retries, provider_failures, enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs/sizes-and-costs
Locator: Available sizes; Billing; When an Orb pauses
Finding: Hosted sizes and hourly rates are published and billed by minute; idle pause stops charges. Enterprise self-hosted pricing changes after November 13.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/customizing
Locator: Orb Lifecycle; .agents/setup; .agents/resume; Services
Finding: Project snapshots reuse dependencies up to 72 hours. Setup and resume scripts have distinct credentials and lifetimes. Services are declared separately; failed setup is visible in Setup Log.
Retrieved: 2026-11-07

## amp:RUN-07

Finding: A thread's dollar indicator opens detailed usage; this is documented, not reconciled against invoices.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Per-task API and compute cost: first-party sources in this pass did not establish task_cost, session_cost, child_cost, epic_cost, harness_aggregation, billed_vs_estimated, tokens, subscription_allowance, provider_reconciliation, compute_cost, refresh_delay, alerts, export. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

## amp:RUN-08

Finding: After a burst of twenty metered Orb starts per user, later starts queue at one every five minutes.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Compute-aware scheduling and verification: first-party sources in this pass did not establish concurrency, cpu_ram, backpressure, host_awareness, check_reuse, check_deduplication, bounded_tests, cancellation, fairness, recovery, shared_limits. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.

Source: https://ampcode.com/docs/orbs
Locator: Orb spawn pacing; review; follow along
Finding: Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.
Retrieved: 2026-11-07

## amp:TEAM-01

Finding: Workspace members can chat with each other in the thread. Workspace teammates can prompt together in an enabled multiplayer thread. Further scoped facts are recorded in the atomic answers.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Live human collaboration: first-party sources in this pass did not establish visibility, comments, presence, ordering, conflicts, attribution, plan_restrictions, owner_online. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.

Source: https://ampcode.com/docs/collaborate/multiplayer
Locator: Activate multiplayer; Security; MCP servers
Finding: Workspace members can co-prompt an enabled thread and access its Orb or shared runner; access is time-limited and bills the owner.
Retrieved: 2026-11-07

## amp:TEAM-02

Finding: Member and Admin roles are documented; Admin manages membership, billing, settings and policies and can view private threads. Admins invite members; member email-invitation rights are configurable. Teams list SAML/OIDC SSO; Enterprise adds SCIM. Enterprise supports directory sync of members and groups. A non-enterprise workspace needs a paid Megawatt or Gigawatt member for SAML/OIDC SSO; Enterprise does not require a paid member tier.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: project_roles, task_roles, unauthorized_access, revocation. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/collaborate/workspaces
Locator: Members; Personal vs. Workspace
Finding: Member uses shared resources; Admin also manages membership, billing, settings and policies and can inspect private threads. Enterprise adds narrower roles.
Retrieved: 2026-11-07

## amp:TEAM-03

Finding: Multiplayer starts with a seven-day duration, can end early and expires automatically. Stopping runner sharing ends multiplayer on threads created on it.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Approvals and temporary access: first-party sources in this pass did not establish command, tool, network, secret, delivery, approver_identity, allow, deny, tunnels, defaults, safer_modes, enforcement. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.

Source: https://ampcode.com/docs/collaborate/multiplayer
Locator: Activate multiplayer; Security; MCP servers
Finding: Workspace members can co-prompt an enabled thread and access its Orb or shared runner; access is time-limited and bills the owner.
Retrieved: 2026-11-07

## amp:TEAM-04

Finding: Enterprise admins can access authentication event audit logs; comprehensive application audit logs remain internal. Each artifact save creates a revision and Share identifies the last editing thread agent. Artifacts export to Markdown, HTML or PDF; threads export to Markdown or owner-only JSON. Artifacts are editable, with a revision made for each save. Deleting a thread deletes its artifacts. A stale agent artifact write is refused when another revision was saved; the agent must merge its changes.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: approvals, discussion, decisions, cross_user_persistence, cross_session_persistence. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

Source: https://ampcode.com/security
Locator: System Components; Data Security and Retention; Audit Logs; Assurance
Finding: Amp describes a cloud control plane without self-hosted deployments, GCP storage, separately controlled training, thread deletion, SOC 2 Type II and authentication audit logs.
Retrieved: 2026-11-07

## amp:TEAM-05

Finding: The Changes pane offers all changes, uncommitted changes or a selected commit. The commit picker supports the right arrow key to read a commit message. Commits carry an Amp-Thread-ID trailer linking a code change back to its conversation.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: pending_reviews, evidence_navigation, comments, request_changes, shipping_guidance, effort, missed_evidence, narrow_screen, context_switching, roles. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

## amp:TEAM-06

Finding: Colleagues use the same thread and Orb or shared runner while multiplayer is active; disconnect takeover was not tested.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Colleague takeover and continuity: first-party sources in this pass did not establish ongoing_takeover, session_history, decisions, artifacts, permissions, runtime_context, owner_disconnect, ownership, attribution, context_loss, harness_transfer. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.

Source: https://ampcode.com/docs/collaborate/multiplayer
Locator: Activate multiplayer; Security; MCP servers
Finding: Workspace members can co-prompt an enabled thread and access its Orb or shared runner; access is time-limited and bills the owner.
Retrieved: 2026-11-07

## amp:SHIP-01

Finding: The thread's Changes view shows the diff, alongside files, services and conversation. Thread artifacts retain plans, reports and notes. The Artifacts tab groups multiple documents in folders. Artifact links in the transcript open the document in its thread. Artifacts and their uploaded images remain with the thread; deleting the thread deletes its artifacts. A child thread can edit or copy an accessible parent artifact, then notify its thread of the change.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: screenshots, recordings, previews, test_outputs, reviewer_outputs, revision_links, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs
Locator: Orb spawn pacing; review; follow along
Finding: Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

## amp:SHIP-02

Finding: Default Ship asks the agent to run the full test suite. The documented agent instruction ignores a failing test only after confirming that it fails on the base branch too. This describes a prompt, not an independently enforced gate. A project can configure Ship Behavior or write a Custom Ship prompt.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: lint, types, ci, independent_review, spec_checks, required_checks, requirement_conflicts, enforced_policy. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs/shipping
Locator: Default Ship Flow; Ship Behavior; Restack Changes
Finding: Default Ship commits, rebases, runs tests and pushes to the base branch. Push to Branch changes the destination; Custom Ship is a configurable prompt. Substantive conflicts require confirmation.
Retrieved: 2026-11-07

## amp:SHIP-03

Finding: Push to Branch ships to a feature branch instead of the base branch. Default Ship commits uncommitted files before rebasing and pushing. Orbs can push branches and open PRs using a connected GitHub identity. Default Ship rebases on the latest base branch and repeats after a concurrent push. The agent resolves conflicts and asks the user before proceeding on substantive conflicts. A PR linked by thread URL or ID appears in the thread title bar with open, draft, queued, merged or closed status.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: worktrees, comments, ci_response. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/github
Locator: Connection; PR status; GitHub webhooks
Finding: A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/shipping
Locator: Default Ship Flow; Ship Behavior; Restack Changes
Finding: Default Ship commits, rebases, runs tests and pushes to the base branch. Push to Branch changes the destination; Custom Ship is a configurable prompt. Substantive conflicts require confirmation.
Retrieved: 2026-11-07

## amp:SHIP-04

Finding: Default Ship writes directly to the base branch after rebasing; PR approval and merge-policy enforcement are not established. Ship behavior is a project-configured agent prompt. The source does not establish an immutable authorization boundary.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: approve, release, deploy, exact_revision. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/orbs/shipping
Locator: Default Ship Flow; Ship Behavior; Restack Changes
Finding: Default Ship commits, rebases, runs tests and pushes to the base branch. Push to Branch changes the destination; Custom Ship is a configurable prompt. Substantive conflicts require confirmation.
Retrieved: 2026-11-07

## amp:SHIP-05

Finding: The thread records linked PRs when the PR description includes its thread URL or ID.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Completion evidence and rollback: first-party sources in this pass did not establish commit_links, build_links, deployment_links, delivery_status, retained_evidence, rollback, revert, stale_approval_invalidation. No draft PR, failed-gate, stale-approval, rollback or six-task batch-review fixture was run. Described actions do not prove delivery authority.

Source: https://ampcode.com/docs/github
Locator: Connection; PR status; GitHub webhooks
Finding: A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.
Retrieved: 2026-11-07

## amp:OWN-01

Finding: Amp access is covered by the limited, revocable service license in its custom terms. The hosted service is governed by Amp License Terms; an open-source server license was not established.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: hosted_extensions, source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/terms
Locator: License; Intellectual Property
Finding: Amp grants a revocable, nontransferable service license and reserves proprietary rights. This is a custom service license, not an open-source license.
Retrieved: 2026-11-07

## amp:OWN-02

Finding: Amp explicitly says it does not offer self-hosted deployments of its control plane. Self-hosted Orbs are execution workers. Threads export to Markdown, with full JSON available to the creator. Thread export formats are Markdown and JSON; artifacts export Markdown, HTML and PDF. Thread transcripts can be exported; importing an exported history was not established.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: vendor_dependencies, import, cancellation, account_independence. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/threads
Locator: Changes; Export a Thread; Artifacts
Finding: Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.
Retrieved: 2026-11-07

Source: https://ampcode.com/security
Locator: System Components; Data Security and Retention; Audit Logs; Assurance
Finding: Amp describes a cloud control plane without self-hosted deployments, GCP storage, separately controlled training, thread deletion, SOC 2 Type II and authentication audit logs.
Retrieved: 2026-11-07

## amp:OWN-03

Finding: Local code snippets and context can be sent to Amp Server and model providers. Prompts and conversation history are sent to Amp Server and then inference providers. Authentication audit logs are available to Enterprise admins; internal application logs are not exposed to admins. Enterprise workspace threads remain until the enterprise contract ends, including after the author leaves. Deleting a thread also deletes its associated Orb, usually within seconds. Training can be toggled in Settings Privacy; workspace enabling requires admin approval. Amp Server stores data in a multi-tenant Google Cloud Platform project; its primary infrastructure is hosted in the US, and no narrower region is stated. Personal provider subscription terms and data controls apply independently of Amp training settings.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: credentials, artifacts, subprocessors, telemetry_disclosure, telemetry_defaults, telemetry_controls, consent_prompt. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/security
Locator: System Components; Data Security and Retention; Audit Logs; Assurance
Finding: Amp describes a cloud control plane without self-hosted deployments, GCP storage, separately controlled training, thread deletion, SOC 2 Type II and authentication audit logs.
Retrieved: 2026-11-07

## amp:OWN-04

Finding: Public tiers are Hobby free, Megawatt $20/month, Gigawatt $200/month, Teams at no additional workspace charge and custom Enterprise. Team members retain individual tiers; model/tool and Orb usage are separately metered.

Verification: sourced
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: seat_minimum, trial, taxes. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/sizes-and-costs
Locator: Available sizes; Billing; When an Orb pauses
Finding: Hosted sizes and hourly rates are published and billed by minute; idle pause stops charges. Enterprise self-hosted pricing changes after November 13.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/markdown/pricing
Locator: Amp Tiers; How Usage Is Charged
Finding: Hobby is recurring free with no included usage. BYO subscriptions/keys incur no Amp fees outside Enterprise. Megawatt costs $20/month with $20 usage and 750 a1.small Orb hours; compute and credits remain separate.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/markdown/pricing
Locator: Amp Tiers table; How Usage Is Charged; Enterprise. Page lastModified 2026-11-11.
Finding: The complete public tier table lists Hobby free, Megawatt $20/month, Gigawatt $200/month, Teams at no additional charge and custom Enterprise. Usage and Orbs are separately metered. Members keep individual tiers; the public table has no separate per-seat workspace fee or one-time license.
Retrieved: 2026-11-13

## amp:OWN-07

Finding: Amp publicly states SOC 2 Type II certification; the underlying report was not inspected. Vendor security statement only; certificate issuer, validity period and report scope were not independently verified.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: iso_scope, iso_issuer, iso_validity, soc2_scope, soc2_period, report_access, verification_date. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/security
Locator: System Components; Data Security and Retention; Audit Logs; Assurance
Finding: Amp describes a cloud control plane without self-hosted deployments, GCP storage, separately controlled training, thread deletion, SOC 2 Type II and authentication audit logs.
Retrieved: 2026-11-07

## amp:OWN-08

Finding: The Hobby tier is recurring free; model usage and hosted compute may still cost money. Self-hosted Orbs and own subscriptions or API keys have no Amp fee for individuals and teams; infrastructure and provider costs remain. Hobby includes no usage. Own subscriptions and API keys have no Amp token fees or limits outside Enterprise; provider limits still apply.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, paid_only, early_access, free_scenarios, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/markdown/pricing
Locator: Amp Tiers; How Usage Is Charged
Finding: Hobby is recurring free with no included usage. BYO subscriptions/keys incur no Amp fees outside Enterprise. Megawatt costs $20/month with $20 usage and 750 a1.small Orb hours; compute and credits remain separate.
Retrieved: 2026-11-07

## amp:OWN-09

Finding: Agent usage is billed in credits and Orb compute by the minute. Megawatt includes $20 agent usage and 45,000 minutes of a1.small Orbs monthly. Paid credits permit continued model and tool usage beyond the monthly allowance. Enterprise self-hosted Orbs are free until November 13, then billed at 100% of the published standard price; Hobby, Individual and Teams remain free for this platform charge. The guide states no provider API markup for individuals and non-enterprise workspaces. Paid credits require no paid tier or commitment. Enterprise uses custom pricing.

Verification: agent-cross-checked
Checked: 2026-11-07
Scheduled recheck: 2026-11-21
Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown.
Surface: Amp web, Mac and iOS; Amp CLI; Amp Orbs
Version: Public sources checked 2026-11-07; no installed release tested

Unknown after the targeted first-party documentation, release and repository pass: cancellation, transparency_classification. No configured product fixture was run; documentation does not establish successful hands-on behavior.

Source: https://ampcode.com/docs/pricing
Locator: Amp tiers; How usage is charged; Enterprise; Notes
Finding: Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/orbs/sizes-and-costs
Locator: Available sizes; Billing; When an Orb pauses
Finding: Hosted sizes and hourly rates are published and billed by minute; idle pause stops charges. Enterprise self-hosted pricing changes after November 13.
Retrieved: 2026-11-07

Source: https://ampcode.com/docs/markdown/pricing
Locator: Amp Tiers; How Usage Is Charged
Finding: Hobby is recurring free with no included usage. BYO subscriptions/keys incur no Amp fees outside Enterprise. Megawatt costs $20/month with $20 usage and 750 a1.small Orb hours; compute and credits remain separate.
Retrieved: 2026-11-07