Loading
Platform · Company operations
TeamOS
Projects, people and work time in one self-hosted app: tasks, chat, attendance, leave, timesheets and payroll.
- Self-hosted platform · Extension of open source
- 2026
TeamOS — Website Relaunch
About TeamOS
Introduction
Small teams usually run their day across a project tool, a chat app, an attendance sheet and a payroll spreadsheet that never quite agree. TeamOS brings them into one self-hosted app without making routine project work any heavier. It started from Kaneo, an open-source project manager, and extends it with a company layer — people and departments, clock in and out, leave, timesheets, payroll with overtime, expenses and an audit log — plus realtime chat, a privacy-respecting desktop activity agent and an AI workspace assistant.
Details
- Project
- TeamOS
- Timeframe
- 2026
- Type
- Self-hosted platform · Extension of open source
Stack
- React
- Hono
- PostgreSQL
- Drizzle
- Tauri
- Rust
- WebSockets
- Docker
TeamOS is built on Kaneo, the open-source project manager by Andrej Acevski, used under the MIT licence. The company layer, chat, desktop agent and AI assistant were added on top.
- Problem
- Project work, attendance, leave and pay live in separate tools, so managers reconcile them by hand and nobody has one picture of who is doing what.
- What we built
- An extension of an open-source project manager with a company layer, realtime chat, a Tauri desktop agent that reports the app in use and idle state rather than anything on screen, and an AI assistant that proposes changes for a person to approve.
- Outcome
- Deployed and self-hosted, with configurations for Docker, Dokploy, Coolify and Helm.
- assistant tools: 36 from Kaneo, 17 added
- 53
- database tables added to Kaneo’s 39
- 46
- new API modules for the company layer
- 19
- leave types, from annual to parental
- 7
Inside the workspace.
The app a small company runs its projects, people and working day from, rebuilt here in code from its own screens. Pick a page, or click the sidebar.
TeamOS — Dashboard
A dashboard that fits the role
Built-in presets give an assignee their own day and tasks, a team lead who is in and what is late, and an owner the same plus where the hours and salaries go. A tile opens what is behind its number in place.
- Today, Last 7 days, Last 30 days
- Focus, team and company presets
- Requests, overdue tasks, projects at risk
- Team right now, from the desktop app
Recreated from the TeamOS interface in its default dark theme. Labels, columns and statuses are the app’s own; the workspace, people, projects, tasks, messages, hours and money are samples, and the chat images are CC0 photographs.
The parts, up close.
Pieces of the workspace at full size, in the app’s own colours.
Board
A task card that answers at a glance
Key, assignees, labels, priority, subtasks, checklist and due date, coloured by how close the date is.
Ask TeamOS
An assistant that proposes, then waits
Claude reads the workspace and suggests a set of changes. Nothing happens until a person ticks the ones to keep and applies them, and applied changes can be undone.
Workflow
One colour per kind of status
Grey waits, amber moves, violet is being checked, green is finished. Five priorities sit beside them.
Leave
Seven kinds of leave
Requests go to an approver. Every kind but unpaid counts against the yearly allowance.
Desktop app
The working day, in the sidebar
In the desktop app the day runs at the foot of the sidebar: how long, since when, and how much is left.
Live
What someone is on, not what is on their screen
A running timer outranks the app in front. The desktop app reports only app names and website domains, and whether the person is active or idle.
Agent keys
Keys for your own agents
A key lets Claude Code or any MCP app act as you, limited to the scope it was made with.
What went into it.
- 01
Company layer
People directory, departments, clock in and out, leave requests, timesheets, payroll with overtime, expenses and an audit log.
- 02
Realtime & desktop
Channels, direct messages and read receipts, plus a desktop agent that reports the app in use, a website’s domain and active or idle state — never keystrokes, screenshots or window titles.
- 03
AI workspace assistant
An assistant that reads the workspace through 53 tools and proposes changes for a person to approve. It runs on Claude Code or any OpenAI-compatible provider.
How it is built.
The running parts
- API
- Hono with Better Auth and Drizzle, a scheduler for the per-minute jobs, and MCP routes for agents.
- Web app
- React on Vite with TanStack Router and Query, in twenty languages inherited from Kaneo.
- Desktop
- Two Tauri apps: a standalone activity agent, and a desktop shell that adds notifications and a tray icon around the same tracker.
- Data
- PostgreSQL, with Redis optional when more than one instance runs. Files are stored in the database or in Cloudflare R2.
- Deployment
- Self-hosted, with configurations for Docker Compose, Dokploy, Coolify and Helm.
The hard parts
- 01
Activity without surveillance
Every five seconds the agent reads two things: how long since the last input, and the name of the app in front — plus the website’s domain when that setting is on. No keystrokes, screenshots or window titles. Samples merge into spans of at most five minutes, wait on disk and upload in batches.
- 02
Clocking out the people who forgot
A job each minute closes a session after the configured idle or offline time and backdates the clock-out to the last real activity. Coming back within the window reopens the same session; a manual clock-out or approved leave stops it clocking anyone in.
- 03
Time, attendance and pay that agree
Clocking out stops a running task timer. Overtime is the time present beyond the scheduled day, paid at an hourly rate worked out from the salary. Money is held in whole minor units, and an open session is never paid.
- 04
An assistant that cannot exceed its user
Each request gets a temporary key that is deleted afterwards: read-only while proposing, task scope when applying. Its tools call the same API as the person, so the role checks are the real ones, and payroll, audit and member management stay out of reach.
- 05
Staying close to upstream
Kaneo’s package names and settings are kept as they are, and every addition lives in its own folder, so the fork stays readable against the project it came from.
Envie de voir plus ?
Start here
Have a problem worth solving?
Tell us what is slow, manual or missing. You will hear back within one working day — then get a written scope and a fixed quote, or an honest no.
brief.md
- # New project brief
- ## What is slow, manual or missing?
- - [x] Written scope
- - [x] Fixed quote
- - [x] Or an honest no
Reply within one working daySend brief