Sourcebot v3 introduces several major improvements to streamline onboarding, enable team rollouts, and enhance overall usability:

• Parallelized repo indexing

• Multi tenancy mode

• Authentication

• GUI connection management

• Nav bar indicators

To learn how to upgrade from v2 to v3, checkout our migration guide.

Parallelized repo indexing

We've improved Sourcebot's repo indexing capabilities to handle multiple repo index jobs in parallel, speeding up indexing significantly. We're using BullMQ to manage indexing jobs, with a Redis instance automatically spun up within the official docker image. Sourcebot can connect to an external Redis instance by changing the REDIS_URL environment variable.

Multi tenancy mode

Sourcebot now supports multi-tenancy, configurable via the SOURCEBOT_TENANCY_MODE environment variable.

Multi tenancy mode allows your Sourcebot deployment to have multiple organizations, each with their own members and code host connections.

Authentication

We've added built-in authentication mechanisms to gate your Sourcebot deployment, configurable via the SOURCEBOT_AUTH_ENABLED environment variable. This is supported in both multi and single tenancy modes. Admins can invite members and grant them access to their Sourcebot organization.

GUI Connection Management

We've added the ability to manage your code host connections within the webapp. When authentication is enabled, this becomes the primary way to manage code host connections. If auth is disabled, the existing declarative configuration file mechanism is used.

You can now view all connections, their sync status, and any warnings or errors directly in the webapp:

Nav bar indicators

We've added the ability to see the status of your repo indexing jobs at a glance from the nav bar. This allows you to see which repos are in progress, as well as any warnings or errors that my have occurred (when authentication is enabled).

If you have any feedback on the launch or want to suggest additional changes, please check out our discord or github discussions page.