---
summary: One isolated ScaiGit per organisation, with its own address, database, storage
  and runners.
title: Instances
path: concepts/instances
status: published
---

# Instances

ScaiGit runs as one instance per organisation. An instance is a complete
forge of its own — web interface, git over HTTPS and SSH, database, file
storage, search index, CI runners and agent interface — kept separate from
every other organisation's. Each instance has its own database, and each CI
job runs in its own microVM.

## Why one per organisation

Isolation by design rather than by configuration. Your repositories,
users and audit trail live in your instance only, and an instance can be
upgraded, moved or installed on premises as one unit. Managed and on-premises instances run the
same software.

## Names

Every instance has a canonical address, `https://<name>.scaigit.scailabs.ai`.
An organisation can also use its own domain, for example
`https://git.example.com`, and choose which of the two is the main one; the
other redirects to it. Clone addresses, links in e-mail and sign-in all use
the main address. SSH works on port 22 on either name.

## One console for all instances

Administrators and reviewers use one console at
<https://scaigit.scailabs.ai/console/>. After signing in it lists the
instances you may administer. Everyone can use it to manage their
[SSH keys](/docs/scaigit/guides/ssh-keys), which then work on every instance
they use.

## Where your data lives

Instances run in ScaiLabs' Dutch data centres. Databases are backed up
continuously with point-in-time recovery for 14 days; repositories and other
files are backed up daily to separate storage.
