# Enterprise Team Guide

The QCode Enterprise Team plan is built for **development teams of three or more**. It provides a dedicated domain, sub-API-key management, ban protection and other enterprise features. This article covers the core capabilities, how to deploy it and the practices we recommend.

---

## Enterprise vs Personal

| | Personal | Enterprise Team |
|--------|--------|-----------|
| **API domain** | Shared `api.qcode.cc` (also available to users in China) | Dedicated `e-xxx.qcode.cc` |
| **API key management** | One key | Unlimited sub-keys, each with its own quota |
| **Admin panel** | Basic panel | Full management console |
| **API isolation** | Shared instance | Dedicated backend instance |
| **Ban protection** | Yes | Yes (same-day replacement) |
| **Real-time monitoring** | Basic | Comprehensive (usage / rate / cost) |
| **Invoices** | No | Corporate transfer + official invoices |
| **Supported tools** | Claude Code + Codex | Claude Code + Codex + Cline + Aider + OpenCode + Gemini CLI |
| **Team size** | 1 person | 3–100+ people |
| **Cost per person** | Depends on plan | **From ¥320 per person per month** |

> **The key difference**: every enterprise customer gets a **completely separate backend instance and domain**, so API traffic is fully isolated from other customers.

---

## Five Core Features

### 1. Dedicated domain and management system

Each enterprise customer gets a dedicated domain `e-xxx.qcode.cc`:

```
Your team's API address:
https://e-xxx.qcode.cc/api

Admin console:
https://e-xxx.qcode.cc/admin
```

- A separate console with its own login system
- The API address is fully isolated from other customers
- Monitor the team's API usage in real time

### 2. Flexible sub-API-key management

An administrator can create multiple sub-API-keys, each with its own quota and limits:

```
Example key allocation for a team:
├── key-frontend-team    → daily quota $50, used by 3 people
├── key-backend-team     → daily quota $80, used by 4 people
├── key-devops           → daily quota $20, used by 2 people
└── key-intern           → daily quota $10, used by 1 person
```

- Technically there is no limit on the number of sub-keys
- Each key has its own quota and rate limits
- Enable or disable them at any time
- **Recommended**: three people sharing one Max X20 account works best (it avoids bans caused by very high request rates)

### 3. Ban protection

If Anthropic bans a Max X20 account, QCode provides a **free, fast replacement**:

- During business hours a replacement takes roughly **1–3 hours**
- Replacements are free for the duration of your subscription
- Running several accounts reduces the risk of interruption

> **Strongly recommended**: keep two or more accounts, so the team can switch to a spare immediately even while the primary is being replaced.

### 4. Multi-tool support

One enterprise account, and every AI coding tool shares the same quota:

| Tool | How to configure |
|------|---------|
| **Claude Code** | `ANTHROPIC_BASE_URL=https://e-xxx.qcode.cc/api` |
| **Codex CLI** | `base_url = "https://e-xxx.qcode.cc/openai"` |
| **Cline** | Set the API base URL in VS Code settings |
| **Aider** | `--openai-api-base https://e-xxx.qcode.cc/openai` |
| **OpenCode** | Through environment variables |
| **Gemini CLI** | Through the API compatibility layer |

### 5. Scales with the team

Start with one account and add more whenever you need to:

| Stage | Accounts | Recommended team | Price per month |
|------|--------|---------|---------|
| Starting out | 1 | 3 people | ¥1,800 |
| Growing | 3 | 9 people | ¥1,760 |
| Expanding | 7 | 21 people | ¥1,720 |
| At scale | 11+ | 33+ people | ¥1,680 |

---

## Team Deployment Guide

### Step 1: open an enterprise account

Contact QCode support to open an enterprise account:
- **Live chat**: [qcode.cc](https://qcode.cc), bottom-right corner
- **Email**: hi@qcode.cc

Tell us: your team size, the number of accounts you expect to need, and any special requirements.

### Step 2: administrator setup

Once it is open, the administrator signs in to the dedicated console at `e-xxx.qcode.cc/admin`:

1. Create sub-API-keys (one per team member or per group)
2. Set a daily quota for each key
3. Hand them out to the team

### Step 3: team member setup

Each member sets the environment variables locally:

**Claude Code:**
```bash
export ANTHROPIC_BASE_URL=https://e-xxx.qcode.cc/api
export ANTHROPIC_AUTH_TOKEN=cr_the_sub_key_your_admin_gave_you
```

**Codex CLI:**
```toml
# ~/.codex/config.toml
[providers.openai]
base_url = "https://e-xxx.qcode.cc/openai"
```

```bash
export CRS_OAI_KEY=cr_the_sub_key_your_admin_gave_you
```

### Step 4: a shared team CLAUDE.md

We recommend creating one CLAUDE.md in the project root and committing it to Git so the whole team shares it:

```markdown
# Team project CLAUDE.md

## Team conventions
- Code style: follow .eslintrc and .prettierrc
- Git branches: feature/xxx; never push directly to main
- Every PR needs two approvals
- Test coverage above 80%

## Common commands
- dev: pnpm dev
- test: pnpm test
- build: pnpm build

## Notes
- Never commit an API key to the repository
- Sensitive files are listed in .gitignore
```

> For the full CLAUDE.md guide see [CLAUDE.md Configuration](/docs/usage/claude-md).

### Step 5: security policy

Use Hooks to enforce a security policy across the whole team:

```json
{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [{
          "type": "command",
          "command": "echo $TOOL_INPUT | grep -qE 'rm -rf|sudo rm|git push --force' && exit 2 || exit 0"
        }]
      },
      {
        "matcher": "Read|Write|Edit",
        "hooks": [{
          "type": "command",
          "command": "echo $TOOL_INPUT | grep -qE '\\.env|credentials|secret' && exit 2 || exit 0"
        }]
      }
    ]
  }
}
```

> See [Hooks System](/docs/advanced/hooks) and [Security Best Practices](/docs/advanced/security).

---

## Security

| Guarantee | Detail |
|--------|------|
| **Full API isolation** | A dedicated domain and backend instance per customer |
| **No data retention** | We do not store code, conversations or business data |
| **Transparent forwarding** | Every request is forwarded straight to the upstream API |
| **99.9% SLA** | Nodes in multiple regions (Hong Kong / Japan) with automatic failover |
| **Fast response** | Seven days a week, 14 hours a day (09:00–23:00); bans handled same day |
| **Compliance** | We can sign a data security agreement |

---

## Cost Comparison

### Compared with building it yourself

| | Build it yourself | QCode Enterprise |
|--------|---------|-------------|
| Monthly (team of 9) | ¥8,000+ (accounts + servers + operations) | ¥5,280 (3 × Max X20) |
| Per person per month | ¥890+ | **¥533** |
| Management system | Build your own | Ready to use |
| Ban protection | Your problem | Free replacement |
| Operations effort | Needs a dedicated person | None |

### Compared with Anthropic direct

| | Anthropic official | QCode Enterprise |
|--------|--------------|-------------|
| Per person per month | ~$60 (about ¥420) | **¥320–360** |
| Supported tools | Claude Code only | Claude Code + Codex + more |
| Access from China | Needs a VPN | Direct connection to Asia-Pacific nodes |
| Invoices | Overseas invoices | **Official domestic invoices** |
| Ban protection | None | Free replacement |

---

## FAQ

### What is the minimum number of accounts?

One. You can start with a single Max X20 account and scale as the team grows.

### What happens if an account is banned?

QCode replaces it quickly and for free, on the same day the ban is detected. We recommend running several accounts to reduce the risk of interruption.

### Which tools are supported?

Claude Code, Codex CLI, Cline, Aider, OpenCode and Gemini CLI. One quota is shared across all of them.

### Do you support corporate bank transfer?

Yes. We issue official VAT invoices (5% administrative fee) and can sign a formal service agreement.

### Can we try before buying?

Of course. Buy the personal trial plan on the [pricing page](https://qcode.cc/pricing) first (¥60/month), then upgrade to Enterprise once you are happy.

### Is the API compatible with the personal plan?

Completely. The only difference is the API domain (`e-xxx.qcode.cc` instead of `api.qcode.cc`); everything else is configured the same way, and no code changes are needed.

---

## Get Started

Ready to upgrade your team's development experience?

- **Live chat**: [qcode.cc](https://qcode.cc), bottom-right corner
- **Email**: hi@qcode.cc
- **Enterprise details**: [qcode.cc/enterprise](https://qcode.cc/enterprise)

> When you get in touch, please tell us your team size, the number of people who will use it, and how many accounts you want.