Compare
For Teams
Team organizations, shared billing, and collaborative features in CrabGlamp.
For Teams
Team organizations — shared billing, agents, and LLM keys under one account with a GlampHub namespace.
Creating an org
Dashboard → create org → pick a slug (lowercase, hyphens, numbers). This becomes the org’s namespace. Can’t change it later.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything. Create/destroy agents, billing, invite/remove members, delete org. |
| Admin | Create/destroy agents, billing, invite/remove members. |
| Member | Access assigned agents. |
Billing
Each org gets its own Stripe subscription. All org resources — agents, LLM keys, compute, API usage — bill to the org.
- No per-seat charges. Add as many members as you need.
- Mix metered and flat rate across agents.
- Members’ personal accounts keep their own billing.
Agents
Agents belong to accounts, not users. Create an agent under an org and it’s the org’s — billed to the org, visible to members per their role.
GlampHub
Orgs get their own namespace: crabglamp.com/{org-slug}/{glamp-name}. Publish templates, tutorials, starter environments.
Use cases
Onboarding — perfect environment → publish as Glamp → new members clone on day one.
Contractors — add to org, their agents bill to the org, remove when done.
Classrooms — students create agents under the org, instructor manages billing.
Remote teams — same environment for everyone regardless of what’s on their laptop.
vs. other platforms
| CrabGlamp | Codespaces | Gitpod | |
|---|---|---|---|
| Billing | Org subscription, no per-seat | GitHub org billing | Per-seat |
| Sharing | GlampHub snapshots | devcontainer.json | .gitpod.yml |
| Roles | Owner, Admin, Member | GitHub org roles | Owner, Member |
| Isolation | Full VM per agent | Container | Container |
| Persistence | Yes | Timeout | Ephemeral |