Teamspective cut median CI time from 10 to 4.5 minutes with Avrea
Results snapshot
Median CI run: 10 minutes → 4.5 minutes (2.2x faster)
Jobs start on push, with no visible queue time
Migration: connect GitHub and change the runner labels
Support replies within minutes in a shared Slack channel
About Teamspective
Teamspective is a leadership enablement and people analytics platform. It helps managers act on employee feedback about engagement, performance, and collaboration, using company guidelines. Managers can access it in Slack and Teams.
The company was founded in Helsinki by a team of four. Co-founder Ian Tuomi leads technology.
- Industry: HR tech, leadership enablement
- Stack: GitHub Actions, sharded test suite on 4 vCPU Linux runners
Before: Ten minutes per CI run
Teamspective’s application stack includes TypeScript, React, Node.js and PostgreSQL. The team runs a sharded test suite on 4 vCPU Linux runners through GitHub Actions.
Teamspective used to run CI on GitHub-hosted runners, with a median run of about ten minutes. Its experienced engineers have plenty of autonomy to make decisions and ship changes quickly. But with pull requests arriving throughout the day, they kept waiting for CI to catch up.
Ian Tuomi, who leads technology at Teamspective, wanted to cut that wait.
Connect GitHub and change the runner labels
The team connected its GitHub account to Avrea and changed the runner labels in its workflows. They could keep using GitHub Actions and their existing test setup, with Avrea providing the runners. Caching worked out of the box, so there was no separate cache configuration to sort out before getting started.
Ian had a direct line to Avrea’s engineers through a shared Slack channel. Replies came within minutes, and the team followed through quickly. The straightforward setup and responsive support made the switch easy to get going with.
From ten minutes to four and a half
- Median CI run: 10 minutes → 4.5 minutes
- Jobs start on push, with no visible queue time
CI now takes less than half the time, cutting five and a half minutes from the median run. Jobs start without a visible queue, and the team spends less time waiting for CI to finish.
Ian also appreciated the dashboard: job status and overall statistics were easy to see, with detailed logs available when needed.
“It's been working so smoothly that after a while I almost forgot we'd even switched, because I stopped thinking about CI”
Ian Tuomi, Co-founder, Teamspective
