Home / Get started

Get started with AI Council

No demo call, no sales process. Pick a plan, connect a repository and your agents, and see how they behave on your own code.

Four steps

Step 1
Subscribe
Choose Startup or Standard on the pricing page and set the number of users. You get access to the cloud workspace, or a license key and install guide if you self-host.
Step 2
Connect GitLab or GitHub
Add a token or install the GitHub App, pick the repositories. AI Council analyzes the code and tickets and builds the project graph. Guide
Step 3
Connect your agents
Each developer runs one command that installs the hooks and the MCP server for Claude Code or Codex. Guide
Step 4
Add your first rules
Write down the five or ten rules reviewers keep repeating. From now on the agent sees them before it edits. Guide

Most teams already have all of it.

One ownerA team lead or senior developer who picks the first project and the main rules.
Repository accessGitLab or GitHub. A tracker is optional: GitHub Issues or Redmine.
A modelA subscription or API key for Claude Code or Codex, or an open-source model on your servers connected to Claude Code CLI.
A server, if you self-hostFor a team of up to 15: 16 CPU cores, 64 GB RAM, 200+ GB SSD, no GPU.

Developers' sense of "we got faster" is not a metric. Write down a baseline before you connect, then compare.

Before you connectTime from a new hire's first day to their first merged MR. Share of MRs sent back from review. Hours a week spent fixing AI-written code. Hours seniors spend answering the same project questions.
Weeks 1–4The team works as usual. AI Council records how often agents receive knowledge and rules, what the diff checks catch and what review finds.
Week 4–6Compare against the baseline and decide whether to roll out to more projects. Calculator

Message Dmitrii, the co-founder, on Telegram or LinkedIn. For Enterprise, air-gapped installs or 50+ users, start there too.