DECAPOD CLOUD

Decapod Cloud Admin

Your repositories. Your people. One place.

Sign in to manage your workspace.

Advanced project setup
RepositoryAssigned seatsPurchased human capacityAccess

Commercial terms: Decapod Cloud bills strictly per purchased human contributor seat per enrolled repository. Annual billing applies an exact 8% base term discount, combined with independent 2%/4%/6% volume tiers for paid repositories (3+/6+/10+) and distinct assigned canonical humans (5+/10+/20+) for an 8–20% standard annual savings total (whole-number tiers only; no fractional decimals, coupons, or 3-seat minimum). Zero agent, device, session, or worktree seats. Replacing a departing teammate within existing purchased capacity is free without buying another seat. Mid-cycle capacity additions are prorated immediately; reductions and cadence changes take effect at renewal. Paid overages are OFF by default (excess usage is throttled without overage fees; zero volume, annual, or partner discounts apply to resource usage).

One person assigned to two repositories uses one capacity on each. Agents, devices, sessions and worktrees add no seats. Removing an assignment revokes access without reducing the purchased capacity.

People & repository access

Repository assignments

Members can confirm their workspace number after sign-in. Select a specific linked member and repository; an invitation alone grants no paid assignment.

Workspace members and seats

Review seated workspace accounts, linked code hosts and active repository assignments. Removing a non-owner workspace seat immediately revokes repository assignments without reducing purchased capacity, and the removed person can be re-invited cleanly later. Slot 1 belongs to the workspace owner and cannot be removed here.

    Workspace invitations

    Invitations grant workspace membership. Paid repository assignments are managed separately. Canceling an unused invitation does not remove an accepted member.

      Cloud usage & terms

      Pooled cloud allowances and resource policy

      Human repository seats control who can collaborate on an enrolled repository; cloud storage and compute allowances are pooled across the customer organization rather than partitioned into rigid per-person silos. Retained repository state (active records and history stock) is tracked separately from monthly consumable operations and transfer flows, which reset on monthly allowance periods even when a subscription is billed annually. Per-repository usage remains attributable for visibility, reserve headroom protects normal CLI operations before hard caps, and numerical launch allowance quantities and expansion pack rates remain pending ratification (#59) — this portal never invents unratified numerical quotas or promises unlimited resources.

      Paid resource overages: OFF (default, $0 exposure). Request pressure (rate/concurrency) is strictly protective and never eligible for paid overages.

      Configure resource limits & alerts

        Capacity increases require confirmed payment. Reductions and cadence changes apply at renewal. Ordinary product support is included. Bespoke services and contractual SLAs require a separate agreement. Included resource allowances and expansion terms must be disclosed separately; purchased capacity does not promise unlimited resources.