ScaiGit

ScaiGit is self-hosted Git repository infrastructure for the ScaiLabs ecosystem — hosting, mirroring, CI hooks, and native integration with the rest of the platform (identity via ScaiKey, secrets via ScaiVault, agents via ScaiGrid).

This namespace is freshly bootstrapped. Real content lands here as the ScaiGit team ships. Watch this space for setup guides, API references, and integration recipes.

What ScaiGit provides#

• Repository hosting — public and private Git repositories with fine-grained access control, backed by the same identity system as the rest of ScaiLabs.
• Mirroring — keep repositories in sync with upstream sources on GitHub, GitLab, or any Git remote. Automatic, hookable, verifiable.
• CI hooks — post-receive triggers that fan out to ScaiFlow pipelines, ScaiForge builds, or arbitrary webhook targets.
• Identity integration — sign in with ScaiKey OIDC; enforce team-based access with the same groups that gate the rest of the platform.
• Secrets integration — CI jobs can pull short-lived credentials from ScaiVault at build time; never bake secrets into repositories.
• Web + API + Git+SSH transports — clone over HTTPS or SSH, browse in the web UI, script against the REST API.

Where it fits#

ScaiGit is a platform primitive: it sits alongside ScaiKey (identity), ScaiVault (secrets), and ScaiDrive (storage) as one of the foundations other ScaiLabs products build on. Team workflows on ScaiCore, ScaiExchange, and ScaiCMS all flow through ScaiGit for source-of-truth versioning.

For operators#

Setup, deployment topologies, backups, replication, and observability will land under /docs/scaigit/operating/.

For users#

Cloning, pushing, PR flow, branch protection, and CLI recipes will land under /docs/scaigit/using/.

For integrators#

REST API, webhooks, event streams, SSH keys, and CI-side helpers will land under /docs/scaigit/api/.

Status#

More content lands here as the ScaiGit team ships.