Team Edition Guide

The complete guide to the QCode Team Edition: dedicated domain, sub-key management, service assurance, multi-tool support, deployment and security

Need an API key? Sign up →·Endpoints & base URLs →

The QCode Team Edition is built for development teams of three or more. It provides a dedicated domain, sub-API-key management, service assurance and other enterprise features. It is measured in team quota × units: 1 unit = $4,000 per month, 35 concurrent, 3–5 people recommended. This article covers the core capabilities, how to deploy it and the practices we recommend.

Team Edition vs Personal¶

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

3. Service assurance¶

When a service issue comes up, QCode handles it and restores service the same day:

• The unit of measure is team quota × units: 1 unit = $4,000 per month, 35 concurrent, 3–5 people recommended
• For higher concurrency or more quota, add more units
• For the exact service terms, see the /enterprise page

4. Multi-tool support¶

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

5. Scales with the team¶

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

The price per person is not fixed; tiered prices are on the /enterprise page.

Team Deployment Guide¶

Step 1: open an enterprise account¶

Contact QCode support to open an enterprise account:

• Live chat: qcode.cc, bottom-right corner
• Email: hi@qcode.cc

Tell us: your team size, the number of units 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:

export ANTHROPIC_BASE_URL=https://e-xxx.qcode.cc/api
export ANTHROPIC_AUTH_TOKEN=cr_the_sub_key_your_admin_gave_you

Codex CLI:

# ~/.codex/config.toml
model_provider = "qcode"

[model_providers.qcode]
name = "qcode"
base_url = "https://e-xxx.qcode.cc/openai"
wire_api = "responses"
env_key = "QCODE_API_KEY"

export QCODE_API_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:

# 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.

Step 5: security policy¶

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

{
  "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 and Security Best Practices.

Security¶

Cost Comparison¶

Compared with building it yourself¶

Pricing¶

Billed per token; per-model rates are listed at qcode.cc/models. The Team Edition is quoted per unit; tiered prices are on qcode.cc/enterprise.

FAQ¶

What is the minimum number of units?¶

One. 1 unit = $4,000 per month, 35 concurrent, 3–5 people recommended; add units as the team grows.

What if there is a service issue?¶

QCode handles it and restores service the same day. For higher concurrency, you can add more units.

Which tools are supported?¶

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

Do you support corporate bank transfer?¶

Yes. Corporate bank transfer is supported and we can sign a formal service agreement.

Can we try before buying?¶

Of course. Buy the Starter plan ($9/mo) on the pricing page first, or a Pay-as-you-go Pack (from $4, see How to Choose a Plan), then upgrade to the Team Edition 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, bottom-right corner
• Email: hi@qcode.cc
• Team Edition details: 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 units you want.

Enterprise →