When the studio outgrows its first team
More people, more projects, outside companies and a hiring plan. kumo keeps them on one set of people, permissions and data.
Access that holds
Everyone sees exactly their part
- Groups, not page linesRoles, teams, disciplines and companies decide what each person sees; the most specific grant wins.
- Outside companiesAn outsourcer is a group like a team; work orders go to the company or to one person, and they see only their project.
- GuestsInvite someone to one project only, and share a publisher space by link.
- SCIMKeep people in step with your identity provider.
- Row-level securityEvery record is checked against the reader’s groups by the database itself.
- Your own serverRun the team server on a machine you own, in Docker, or use ours.
Run the studio
Hiring, people and leave in the same place
Openings and candidates, interviews with scorecards, a careers page Google lists, people’s records, leave and review cycles, readable only by the people who may.
- Hiring Openings, candidates by stage, interviews with scorecards and referrals, with a public careers page that Google for Jobs lists and a job feed.
- Finding people GitHub's public people search, and shortlists and outreach drafted by the assistant for a person to send.
- Joining and leaving Onboarding and offboarding automations, turned on from People.
Plan & produce
Many projects, one view of production
Milestones and scenarios per project, goals across the studio, and one Calendar for everyone, with the budget beside the milestones it pays for.
- The board Columns, swimlanes, task types per discipline, bulk edit, and a card that turns a column at a time on a phone.
- Milestones and Gantt Dependencies, a compact timeline where back-to-back milestones share a row, and pull or merge requests linked on each task.
- Sprints Sprint planning with velocity and cumulative flow read from the board itself.
Discord & integrations
Bring the tools you already run
Ten project tools sync both ways while teams move; Notion and Confluence import into the wiki; Sentry stays in step with the Bugs page; the API and signed webhooks reach the rest.
- Meetings Calendar meetings published as Discord events, with a notes page for each one.
- Stand-ups Asked and gathered in Discord.
- Commands and buttons /bug from any channel, review verdicts and new tasks from a button.