FAQ

Traditionally when talking about git repos and organizing source code, people choose between monorepo and polyrepo setups. Josh erases the distinction between the two. Our thesis is: this distinction is only a product of organization structures and poor tooling. With Josh, repository boundaries are dynamic — any sub-view of a repository can be materialized on-demand and become a new workspace for developers to work in and contribute. These dynamic boundaries can span multiple projects, teams, and even companies, while our data model provides built-in access control and preserves the collaborative and distributed nature of Git.

Josh Integration Queue is a merge queue implementation that enables users to maintain a unified Git repo across multiple separate code hosts (forges). Unlike existing merge queue implementations, Josh Integration Queue is not constrained by boundaries of a single repository, and can evaluate commit admission conditions across multiple forges.

Yes — all Josh tools and subprojects are built on top of Git, and work with Git repositories and remotes natively.

No — up until today, Josh is fully bootstrapped, without any external investment.

We offer consulting services, helping companies scale and improve their Git repositories and workflows.