Teams & collaboration

darting.dev is multi-tenant from the ground up: accounts, teams that share projects, and usage metered and enforced per person.

Accounts

Sign in with GitHub. The same login grants the repo scope, so your sign-in doubles as the git credential used to clone and push your private repos — there's no separate connect step. Manual tokens remain available as a fallback. GitHub App & authentication covers the credential paths in detail.

Teams

Every account gets a personal team where you're the manager, and you can belong to more than one. Team members share projects — anyone on the team can open a project's threads and pick up the work. Who can do what is covered in roles & permissions.

Private threads

Not everything should be shared. A thread you create as private stays visible only to you, even though it lives in a shared project.

Usage & limits

End-to-end usage is metered per person — both LLM tokens and sandbox wall-time, since the compute runs in the cloud. Admins set per-user caps; crossing one pauses your runs until it's raised or the period rolls over. Usage & limits covers the meters, the Usage tab, and how to keep the bill down.

What stays private

LLM API keys live server-side and are never exposed to the browser. Git tokens are stored per user. Sandboxes are isolated per thread and torn down after use.