xeve started as a solo tool — personal analytics for one person. But developers do not work alone. Teams ship code together, and understanding team-level patterns is just as valuable as understanding your own.
How Teams Work
Creating a team takes 10 seconds. Go to your dashboard, click "Create Team," name it, and you get an invite link. Share the link with your team — no email invitations needed, no approval workflows. Click the link, join the team, done.
This was a deliberate design choice. Email-based invitations add friction and fail when people use different emails for work accounts. A simple link is faster and more reliable.
What Teams See
Team dashboards show aggregated metrics:
- Total team coding hours — how much the team coded today, this week, this month
- Average productivity score — the team-wide productivity trend
- Top team projects — which codebases the team is spending the most time in
- Activity heatmap — when the team is most active, visualized across the week
Privacy by Design
Individual data stays private. Team members cannot see each other's specific app usage, window titles, music, health data, or personal metrics. The team dashboard shows only aggregated numbers — totals and averages across members.
This is non-negotiable. xeve is a personal analytics tool first. Teams are an opt-in layer on top, and they never compromise the privacy of individual data.
Row-Level Security
Team data isolation is enforced at the database level via Supabase RLS policies. Team members can only query aggregate functions that return team-wide totals. Direct access to another member's rows is impossible — the database rejects the query before it executes.
Use Cases
Teams work best for small engineering groups (2-10 people) who want lightweight visibility into collective productivity without the overhead of enterprise tools. No Jira, no project management, no sprint ceremonies. Just data.
- Startup teams — see if the team's coding output is increasing week over week
- Open source maintainers — understand contribution patterns across collaborators
- Accountability groups — developers who want shared motivation without surveillance
Create your first team from the team dashboard.