Use case

Teamwork

Several people work on the project. You need roles and boundaries: not everyone should have access to everything, and not everyone may publish outside.

Situation

Organisations, roles, repository access, access keys and connectors — under the owner’s control.

What gets in the way

  • Several people work on the project — roles and boundaries are needed.
  • Not everyone should have access to every repository.
  • You need control over who publishes to the source repository.
  • Access tokens must not be scattered around shared places.
  • Organisations and clients must not see each other’s data.

Solution 01

Organisation, roles and isolation

Members join an organisation with the roles of owner and user — the owner manages membership and boundaries. Each organisation is physically isolated from the others: clients and teams do not see each other’s data.

About members
Organisation, roles and isolation

← scroll the frame →

Organisation members with owner and user roles.

Solution 02

Repository access and publishing tokens

Rights are granted per project, space or individual repository — not everyone has access to everything. Publishing to the source repository is done by whoever holds the right, and each person keeps their own access tokens, encrypted and never shown back — so they do not have to be scattered around shared places.

About roles and access
Repository access and publishing tokens

← scroll the frame →

Repository access and publishing tokens — under the owner’s control.

Solution 03

Connectors — your own git, without handing over tokens

If your code lives in a private or self-hosted git (behind a firewall), the team connects it through a connector — an agent you run in your own network. It links your git to the platform over an outbound connection, and the access token stays with you and never reaches us. Integrations with the team’s trackers and knowledge sources are installed into the same connector.

About connectors
Connectors — your own git, without handing over tokens

← scroll the frame →

Connectors: connected agents and the repositories they serve.

Outcome

The team works together, while access, publishing and connecting your own git stay under the owner’s control.

The first step changes nothing in the code

Start with a question about your project

Connect a repository and ask the system how your code is built: it reads the source code and answers in minutes, changing nothing. A starting balance is provided to try it out.

Companies and sole traders can pay by bank transfer and receive closing documents