Where TimerOS is headed.

What we’re building next, grouped by how close it is — from what’s already shipped, to what’s in active development, to committed work, to the longer-term direction. We don’t commit to dates publicly. Every release, down to the last bug fix, is written up in the Changelog.

We’d rather under-promise and ship. So the board below is grouped by how certain we are — a few things are in active build, more are committed but undated, and the rest are still directions we’re exploring. Nothing here is a guarantee of timing, and an idea can move between stages as priorities change.

DoneBuilding nowUp nextExploring
TimerOS Workspace
Pipeline
In active buildBuilding now
Sharper time mapping
macOS desktop app
iOS mobile app
Up next · coming soon
Support knowledge baseSSO / SAMLAudit logDedicated support
Exploring · future
Deeper AI integrationAutonomous AI employees
3 building · 4 queued · 2 exploringShips → Changelog
Stage 00Done

Shipped

Already live. Every release is written up in the Changelog.

Personal notebook

A notebook of your own inside TimerOS, for the thinking that never had anywhere to live. Keep as many as you like, each one a canvas rather than a page — draw on it, write on it, drop images onto it. Yours by default, and shareable with colleagues in your workspace when you want somebody else to see one — it does not reach your clients.

Allocating tracked time to tasks

The hours on a task come only from time that was really tracked — the number you used to be able to type in is gone, along with everything it quietly fed. Performance shows what a day, a week, a month or a year of your tracked time was booked to and how much of it was booked to nothing at all, and that unassigned time can be given to a task there or from the task itself. Because tracked time is stored a day at a time, allocating draws from particular days, newest first, and lists every day it will take from before anything is written. Your client sees the result per task, rounded, with the date it was last worked out.

Incident war rooms

Live rooms in the support section for coordinating an incident or an urgent change. Open one on the record itself and everyone working it has one place to be: a shared canvas to draw the failure on, a conversation, a timeline of what happened, and — above the roster of who ever joined — who has the room open right now and who is typing. Whoever joins picks a role and a team from lists set when the room was opened, so it is clear who is coordinating and who is investigating. Resolving the incident closes the room by itself; deleting it takes the room and its history with it. Named contacts from the affected client can be brought in too, each set to watch or to draw, seeing the shared canvas and the timeline and nothing else.

Project whiteboard

A shared canvas on every project. The people assigned to the work and the client draw on it together — freehand, shapes, text and sticky notes — and see each other’s strokes and cursors as they happen, in the desktop app, the web dashboard and the client portal alike. A sketch worth keeping becomes a revision, frozen at the moment it is saved: a client approving one is approving what is in front of them, not a board that has moved on since. They approve or reject with a note, and restoring a revision puts the board back for everyone at once. Pictures too: paste, drag or pick one onto the board, then move and resize it like anything else.

Automatic time mapping to project tasks

Tracked time files itself against the right task. The timer reads what you’re working on — on your device, nothing leaves it — and books the hours to the matching task or subtask, or leaves them as plain productive time when there’s no clear match. When it knows the project but not the task it offers a one-click suggestion rather than guessing, and it books nothing for a window it can’t account for. Tie the websites and apps a project lives in to it, pin a task yourself from the timer bar, and move any booked block in two clicks.

Project presets

A catalogue of ready-made project plans — website design, Android and iOS app development, SaaS MVP, e-commerce launch, brand identity, marketing, SEO and more — each arriving with its milestones and tasks already laid out. Start from one, edit it to fit the job, and save your own.

TimerOS 1.0 — public launch

The first public release: Windows desktop app, web dashboard, client portal, projects, teams, invoicing and reporting.

Chat

Built-in messaging across the desktop app, web dashboard and client portal — a conversation with every client, group chats that include the client contacts you choose, and staff-only chats and direct messages.

Dedicated status page

status.timeros.ai — live service health checked every minute from outside our own network, with 90-day history and monthly uptime.

Custom portal domains

Connect your own domain to the client portal, with copy-paste DNS records and live verification.

Two-factor authentication

TOTP two-factor for workspace users and client portal contacts.

Offline time tracking

The desktop timer keeps running when your connection drops and syncs back up when you reconnect.

Stage 01Building now

In progress

Actively in development right now — the next things to land.

Sharper automatic time mapping

The next round of work on task matching, driven by measurement on real machines rather than guesswork: recognising more of the work it currently stays silent on, booking less of what it can’t properly account for, and noticing when you’ve actually switched tasks — so the minutes after a break stop going to whatever came before it. Still entirely on your device, still a suggestion whenever it isn’t sure.

macOS desktop app

A native macOS build of the desktop client, with the same timer bar and dashboard as Windows.

iOS mobile app

A native iOS build of the mobile dashboard, distributed via the Apple App Store.

German & Bulgarian translations

Full German and Bulgarian localisation of TimerOS — the first languages beyond English.

Social sign-in for client portals

Let your clients sign up and log in with Google, LinkedIn, X, and more — an option for workspaces that turn on public portal registration, alongside the usual email and password.

Stage 02Up next

Coming soon

Committed work — scoped and queued, after the current stage.

Public API

A documented HTTP API so you can integrate TimerOS with your own tooling. Held until the data model settles — publishing endpoints now would freeze a shape that is still changing, and we would rather ship it late than break what you build on it. Reference lands at /docs when it does.

Support knowledge base

A searchable knowledge base in the support section — guides, FAQs, and troubleshooting articles your team and clients can self-serve.

SSO / SAML

Single sign-on via SAML and your identity provider, so larger organizations can centralize access and enforce their own login policies.

Audit log

A detailed record of who did what across the workspace — for compliance, security reviews, and accountability.

Dedicated support

Priority support for Enterprise organizations — a named point of contact and faster response times.

Stage 03Exploring

Future

Less committed — the direction we’re heading, not promises.

Deeper AI integration

AI woven further through TimerOS — sharper activity classification, summaries, and assistance across every surface.

Autonomous AI employees

Full AI employees that operate in their own virtual environment — taking on tasks end-to-end alongside your team.

AI assistant connector (MCP)

A read-only connector that lets an AI assistant you already use answer questions about your own workspace — hours by client, where a project stands, who has room next week — over the Model Context Protocol. It would reach projects, tasks, clients and time totals only: never activity monitoring, payroll, leave or chat, and never more than the person whose key it uses can already see. It comes after the public API rather than instead of it — the credential and the read surface have to exist first.

More languages

Beyond the German and Bulgarian translations already underway, broader localisation is on the future list.

Deeper integrations

Connectors to common tools used alongside TimerOS — calendars, chat, and accounting.

More features in existing surfaces

The five surfaces — desktop, web, mobile, portal, admin website — will keep gaining features as the product matures.

Have a feature request? Email [email protected].