For the complete documentation index, see llms.txt. This page is also available as Markdown.

Prerequisites & requirements

Everything you need before installing self-hosted AI Architect, for both Standalone and Enterprise deployments.

Accounts and keys

Requirement
Where to get it

Bito API key

alpha.bito.ai/home/advanced (Settings โ†’ Advanced Settings)

Git provider token

Your Git provider (see Git provider access below)

LLM key (optional)

Only if you bring your own model (see LLM options below)

1

Git provider access

A personal access token (PAT) lets AI Architect clone and index your repositories. Git authentication is PAT-only. SSH and OAuth helpers are not supported. Both cloud and enterprise (self-managed) editions are supported for every provider. Click a provider name to create the token before you install:

Provider
Editions supported
Token type
Scope / permission
Also provide

GitHub.com ยท GitHub Enterprise Server

Classic PAT (fine-grained not supported)

repo

-

GitLab.com ยท GitLab Self-Managed

Personal access token

api

-

Cloud

API token

Repository read

Your account email

Bitbucket Data Center / Server

Self-managed

HTTP access token (your instance โ†’ Profile โ†’ HTTP access tokens)

Repository read

Your username

dev.azure.com ยท Azure DevOps Server

Personal access token

Full access

Your organization name

Enterprise or self-managed instance (for example github.company.com)? During install, answer yes when asked whether this is an enterprise version of your provider, and enter your custom domain.

2

LLM options

By default, AI Architect uses Bito's LLM, covered by your Bito API key. To bring your own key (BYOK), configure one provider during install, or later with bitoarch update-llm-config. Click a provider name to create the credentials:

Provider
What you provide

API key

API key

API key. Model optional

API key and endpoint URL (for example https://<resource>.openai.azure.com)

AWS access key ID, secret access key, and Bedrock region

Service-account key JSON (file path or inline), project ID, and region (for example us-central1). Model optional

API token and model name (@provider/model). Gateway URL optional (defaults to https://api.portkey.ai/v1)

API key

  • Portkey is an exclusive gateway. When set, it handles all routing, and other providers are not used.

  • With an Anthropic key, indexing costs approximately $1 per MB of indexable code.

  • There is no basic-indexing-only mode. A Bito or custom LLM key is required.

For model selection and how to change providers later, see Custom LLM configuration.

Hardware requirements

Size the host by the number of repositories you plan to index:

Tier
Repositories
vCPU
Memory
Storage

Minimum

up to 25

12

24 GB

500 GB

Ideal

25-100

16

48 GB

1.5 TB

Enterprise

100+

32+

128+ GB

2-4 TB+

  • For repositories larger than 5 GB, add roughly 50% more memory and storage.

  • Keep total allocated memory under roughly 75% of host memory.

  • Indexing produces CPU and memory peaks above steady state, so the tiers include headroom.

Right-sizing by scale: run bitoarch config edit env and tune CIS_REPO_LIMIT (default 50, maximum 500) and CIS_REPO_SIZE_LIMIT (default 1 GB per repository) to match your workload.

Network requirements

AI Architect keeps your code and knowledge graph inside your environment, but it must reach a small set of endpoints. If you run behind a corporate firewall or proxy, allow the following.

Outbound (egress) over HTTPS 443

Destination
Purpose
When

*.bito.ai

License and entitlement validation (always), plus Bito LLM inference unless you use BYOK

Install and runtime

docker.io (bitoai/*) or mirror

Container image pulls

Install and upgrade

Your Git host

Repository cloning

Indexing

Your LLM provider endpoint

LLM inference, only if BYOK

Runtime

Your Jira / Confluence host

Insights, only if enabled

Runtime

*.descope.com and your IdP

SSO, only if enabled

Runtime

Inbound (ingress)

Expose only the MCP server: https://localhost:5001 (Standalone) or port 5001 behind TLS / your ingress (Enterprise). Keep all other services (5002-5006) internal.

Behind a proxy (Standalone)? Export proxy variables before installing and exclude the internal service names:

Configuration file locations

File
Contents
Find it with

.env-bitoarch

Secrets and resource/port settings

bitoarch config path env

.bitoarch-config.yaml

Repository and ticket-tracker configuration

bitoarch config path repos

Last updated