BusDK Update

Managed Git hosting inside your own stack: repos over SSH with Bus identities

BusDK can host Git repositories inside the same stack that runs your services and agents. The early bus-repos and bus-identities work combines a repository catalog, SSH access, and Bus identity principals so people and workers can use Git without depending on an external Git SaaS for every clone or push.

The value is platform completeness under operator control: source code, agent work, and access identities can share the same stack boundary. This is experimental infrastructure, and the current update describes the managed repository and identity shape rather than hosted-Git product parity.

June 20, 2026bus-reposbus-identitiesSSH

In brief

TL;DR

bus-repos now has early repository catalog, lifecycle, remote-template, and SSH transport work for managed Git repositories.
Repository access is tied to the Bus identity model, including worker identity references and binary access-grant contracts.
The maturity is early and experimental; this is a self-hosted Git building block for controlled stack environments.

Managed repositories give BusDK a place to keep Git projects as stack resources instead of treating source control as something that always lives outside the platform. The June 20 work in bus-repos added the repo-side pieces: catalog operations, lifecycle client behavior, canonical sync routes, remote templates, and OpenSSH transport setup.

$ git clone ssh://git@your-bus-host/repos/my-service.git

That surface is meant to make repository access feel native to BusDK deployments. A service can expose repository records from managed storage, and SSH can become the transport a developer or worker uses for normal Git operations. The repository remains a Git repository; the stack supplies the catalog, service boundary, and access path.

The identity side matters because agent work and human work should not need separate access worlds. Around the same date, bus-identities added Bus identity CLI and contract work, credentials modeling, binary access grants, and principal access grant clarification. In combination with the worker identity repo-reference work in bus-repos, repository SSH access can be expressed through Bus identities for people and workers.

Large hosted Git service parity is outside this update. The stack shape is concrete: code, workers, and identities can live inside one controlled BusDK stack, with Git transport available over SSH and repository metadata managed by the stack itself. See docs.busdk.com for BusDK module documentation covering repositories, identities, and stack services.