# Getting started

Codebahn is managed Git hosting with built-in CI, running on EU-only infrastructure. It is built on [Forgejo](https://forgejo.org), so if you have used GitHub or GitLab you already know how most of it works.

This page is the full path from account creation to your first green CI run. Seven steps, around 15 to 20 minutes total.

## 1. Sign up (~1 min)

Go to [codebahn.net/user/sign_up](https://codebahn.net/user/sign_up), pick a username, and provide your email. You confirm with a code emailed to you. There is no password anywhere in the flow. You'll land on your dashboard.

Before you go further, turn on [two-factor authentication](/docs/two-factor-authentication/). It takes two minutes and protects the account that owns your code.

## 2. Choose your plan (~1 min)

**Solo** is for individual developers: €9/month with 52 GiB storage. **Crew** is for teams: €9 per seat per month plus €10 for the team, with 1,000 CI minutes per seat. A payment method is required for both: Solo subscribes from account settings, Crew when you create the organization. See [billing and limits](/docs/billing/) for the full plan table, the money-back policy, and overage pricing.

## 3. Push your first repository (~5 min)

Click **New Repository** (inside your org for Crew, or on your profile for Solo). Repos are private. Add an SSH key under **Settings > SSH / GPG Keys**, then push:

```bash
git remote add origin git@codebahn.net:your-org/your-repo.git
git push -u origin main
```

The same ed25519 key you use with GitHub or GitLab works here. To verify the server's host-key fingerprint before connecting, see [SSH host keys](/docs/ssh/). You'll see your code in the repository view.

Already have repos elsewhere? [Import from GitHub](/docs/migrate-from-github/) instead, with issues and pull requests; [GitLab](/docs/migrate-from-gitlab/) and [Forgejo](/docs/migrate-from-forgejo/) imports work the same way.

## 4. Set up CI (~5 min)

Add a workflow file and push. If you already have `.github/workflows/`, Codebahn picks it up and runs it on EU runners. Otherwise, create a new `.forgejo/workflows/ci.yml` with the examples in the CI guide. Both plans include hosted CI: Solo has 200 minutes a month, Crew 1,000 per seat, pooled; [top-ups](/docs/billing/#top-ups) add more to either. You'll see a green check on the Actions tab.

Full guide: [Set up CI](/docs/set-up-ci/).

## 5. Connect an AI assistant (~2 min)

Add `https://codebahn.net/mcp` to your MCP client. The first request opens an OAuth flow in your browser; approve it once and you are set. Your repos, issues, pull requests, and CI become accessible from your editor. You'll see your repos listed when you ask the assistant.

Full guide: [MCP server](/docs/mcp/).

## 6. Install the CLI (~1 min)

Run `curl -fsSL https://releases.codebahn.net/cli/install.sh | sh`, then `codebahn auth login` to authenticate via OAuth. You'll have repos, pull requests, issues, and CI in your terminal. The CLI is open source and auto-updates.

Full guide: [CLI](/docs/cli/).

## 7. Invite your team (~1 min)

This step applies to Crew plans. Open your org's **Members** tab and invite people by email or username, picking the team they join. A team invite is email-bound, so the person you invite can sign up directly. You'll see pending invites and teammates joining your org.