Split View: 시간과 생산성 추적 도구 2026: Toggl·Clockify·Wakatime·RescueTime·Rize 심층 비교 — 내 시간은 어디로 가는가

Time and Productivity Tracking Tools 2026: Toggl, Clockify, Wakatime, RescueTime, Rize Deep Dive — Where Did Your Hours Actually Go?

"You cannot improve what you do not measure. And not everything you measure matters."

Prologue — You worked 8 hours, so why does it feel like 4?

It's 7pm. You're about to close the laptop and a strange feeling sets in. You were at the desk since 9am, but you cannot point at a single thing you "made today" with any confidence. Slack reply, meeting, PR review, quick Twitter, back to a PR, back to Slack, and somehow it is dark outside.

This is still the default 2026 picture. Two monitors instead of one, an AI assistant writing half your code, and yet the felt amount of real work keeps dropping.

There are two answers. One, write the time down by hand. Two, let the computer write it for you. The first is the world of Toggl and Clockify. The second is the world of Wakatime, RescueTime, Rize, and Timing. And half of this post is an argument about which one is more honest.

Tools covered in this post:

Chapters:

1 · The eternal manual vs automatic debate

The biggest fork in the time-tracking world is this. Will you press start/stop by hand, or let the computer log on your behalf?

The virtue of manual tracking is consciousness. The moment you press the timer, your brain grabs a context. From this minute, for the next 30, I am doing this. That promise pins you to the chair. And when the timer ends you find yourself asking, "Wait, did I actually do that for 30 minutes?" In other words, the act of tracking is itself a focus device. That is why Toggl shows pop-ups like "Are you still working?".

The virtue of automatic tracking is honesty. When you write things down by hand you are kind to yourself. You enter a meeting, drift to Twitter, drift back to the meeting, and the report still reads "Meeting 60 min". Automatic tracking writes down every one of those context switches without mercy. The first week is a shock. "Did I really look at Slack that much?"

People who do this well usually use both. Manual goes to billing and deep-work retrospectives. Automatic goes to "where did this whole week even disappear to?". The workflow chapter below walks through the combinations.

There is a third option. Semi-automatic. Toggl Desktop's autotrack and Timing's rule-based classification show candidates and ask you to label. Auto for the lazy half, manual for the honest half.

              Honesty up
                 |
       Auto  ────|──── Rize.io / RescueTime
                 |
                 |   Wakatime (code only)
                 |
                 |
       Semi  ────|──── Timing / Toggl Autotrack
                 |
                 |
       Manual────|──── Toggl Track / Clockify / Hourglass
                 |
            Awareness ←  →  Convenience

A common misunderstanding. Automatic tracking is not the better tool by itself. It just collects more data. What you do with that data is the real value. That is why the good auto trackers ship great reports and coaching.

2 · Toggl Track — the manual classic

Toggl Track started in Estonia in 2006. In the time-tracking market, it occupies the "Google" spot — the default recommendation for any newcomer.

Why it is a classic:

• The start/stop button is everywhere — web, desktop (Mac, Windows, Linux), mobile (iOS, Android), browser extensions.
• Entries can carry projects, clients, tags, and a billable flag.
• The reports look genuinely good — donut charts, bar charts, weekly calendar views. They are presentable to clients.
• The desktop app includes autotrack and idle detection. If you stepped away while the timer ran, it asks, "Do you want to remove this idle time?"

Pricing (as of 2026):

• Free: up to 5 users, basic tracking and reports. Plenty for any single user forever.
• Starter: around 10 USD per user per month. Billing, project templates, sorted reports.
• Premium: around 20 USD per user per month. Billable rates, priority support, audit logs.
• Enterprise: contact sales. SSO, custom terms.

Where Toggl shines:

• Freelance hourly billing — the PDF reports you send to clients are clean.
• Solo consultants — the 5-user free tier runs forever for free.
• Small team usage analysis — instantly see who spent what on which project.

Where it falls short:

• "Where am I leaking hours?" — Toggl's auto features are bolted on; RescueTime or Rize are far ahead.
• Per-language, per-project automatic developer stats — that is Wakatime territory.
• HR-style employee evaluation — Toggl actively rejects this use case, which is a virtue but not the tool for you if that is what you want.

Verdict: the most trustworthy default in the manual-tracking category. When in doubt, start here.

3 · Clockify — the serious free alternative

Clockify is built by Serbia-based CAKE.com, and its market slogan is "free forever". Early on it had a reputation as "the Toggl clone", but by the mid-2020s it earned its own identity as a real competitor.

Clockify's differentiators:

• Unlimited users on the free tier. Toggl gives you 5; Clockify happily runs a 100-person team for free. Agencies love this.
• Aggressive surveillance features: automatic screenshots, idle detection, forced start/stop. Whether this is virtuous or villainous depends on your culture.
• Built-in simple billing and quoting modules.
• One of the few majors offering a self-hosted option (Enterprise only).

Pricing (as of 2026):

• Free: unlimited users, basic tracking.
• Basic: around 4 USD per user per month. Billable hours, project templates.
• Standard: around 6 USD per user per month. Invoicing, time approval.
• Pro: around 9 USD per user per month. Screenshots, activity tracking, auto-lock.
• Enterprise: around 15 USD per user per month. SSO, audit, self-hosting.

Where Clockify wins:

• 30 to 100-person agencies. Toggl would cost hundreds of dollars a month; Clockify is free or very cheap.
• Hourly billing businesses that must map employee hours precisely onto invoices.
• Security-sensitive organizations needing self-hosting.

Where it falls short:

• Depth of automatic tracking — simpler than RescueTime or Rize.
• Design — Toggl is generally considered prettier.

Verdict: if Toggl is expensive, Clockify is the answer. The fact that a 100-person team can run for free forgives many minor shortcomings.

4 · Wakatime — automatic tracking for developers

Wakatime was started in 2013 by Alan Hamlett as a one-person project. It is now the de facto standard, with tens of thousands of developers shipping daily data.

How it works:

• You install an IDE plugin (VS Code, JetBrains, Vim, Emacs, Neovim, Sublime, Xcode, Android Studio — over 60 supported editors).
• The plugin detects keystroke activity, files, languages, and projects, and ships that to the Wakatime backend.
• The dashboard automatically rolls it up: "Today: 8 hours coding, of which Python 4h, TypeScript 3h, meeting markdown 1h."

Why developers love it:

• It really does write things down for free. Forget about it for a month and the data is patiently waiting.
• Per-project, per-language, per-hour stats come for free.
• You can pin a widget on your GitHub README. "487 hours in Rust this year" makes for a great brag.
• Team features show who works on which codebase how much — but do not use this for performance reviews (see the privacy chapter).

Pricing (as of 2026):

• Free: last 14 days of stats.
• Basic: around 9 USD per month. Full history.
• Premium: around 14 USD per month. Deeper analytics, integrations.
• Free for students.

Where Wakatime wins:

• Developers who want an objective measure of their own coding time.
• Year-in-review retrospectives — "what language did I touch most?"
• Open-source maintainers — showing sponsors the unpaid labor that goes in.

Where it falls short:

• Non-coding time. Meetings, design, research are not captured.
• Context awareness. Hours of real work in the same IDE look identical to hours of "Twitter open in another window while the file stays open".

Open-data culture: one of Wakatime's biggest charms is that many developers publish their numbers. README widgets, "this week's coding time" tweets, blog sidebars showing live stats. It works as peer pressure and accountability in equal measure.

Verdict: if you are a developer, just install it. You can turn off the data it sends, so install first, collect for a month, then judge whether to keep it.

5 · Codetime, Pulse for VS Code — Wakatime rivals

The success of Wakatime spawned several similar approaches.

Codetime (Software.com)

• Started VS Code-first, expanded to JetBrains, Atom, and others.
• Music integration — pair Spotify with your coding sessions and see "what you listened to while making what".
• Free, no ads. The business model question keeps coming up.

Pulse for VS Code

• A lightweight, VS Code-only local tracker.
• Optional local-only data — privacy first.
• GitHub-style daily heatmap.

Wakatime vs Codetime vs Pulse — picking criteria:

The safest default remains Wakatime. The exception: "I want 100% control over where my data lives" — pick Pulse.

6 · RescueTime and Rize.io — auto-tracking for everything

When you want to see non-coding time too, this is the category. Background agents log "which app, which window are you in right now?".

6.1 RescueTime — the elder

Released in 2008. This tool has been doing this job since the PC era.

• Categories: software development, communication and scheduling, entertainment, etc. — auto-classified.
• A productivity score from -2 (very unproductive) to +2 (very productive) is assigned per category. User-adjustable.
• "FocusTime" — a concentration mode that blocks unproductive sites.
• Pricing: Lite free, Premium around 12 USD per month.

Pro: the longest history means the database of apps and sites is enormous. Most things you use are already classified. Con: the UI smells of 2014. Reports look dated.

6.2 Rize.io — the newcomer

Emerged around 2021 and grew rapidly in 2023-2025. Often described as the spiritual successor to RescueTime.

• A cleaner macOS-native UI.
• Focused on deep-work measurement — emphasizes contiguous time blocks in the same app.
• Counts context switches — if you switched apps 200 times today, it shows.
• "Notifications" coaching — nudges like "long meeting day, want a break?".
• Pricing: around 10-15 USD per month.

Pro: design is great. It makes you want to look at the data. The deep-work emphasis is a real differentiator. Con: relatively new, so the category database is not as mature as RescueTime's. macOS-first, so not the answer for Windows or Linux users.

6.3 RescueTime vs Rize.io

Verdict: Windows or Linux, lean RescueTime. macOS, try Rize or Timing first.

7 · Timing — Mac users' rule-based automation

Timing is built by a one-person developer in Germany (Daniel Alm) and is a macOS-only automatic tracker. The headline feature is that everything stays local — no cloud round-trip.

How it works:

• Automatically records apps, documents, and URLs.
• You write rules — "this domain is work", "this app is design", "files in this folder belong to client A's project".
• Once you set the rules, future data is automatically categorized.

Why it is good:

• Data does not leave the machine. Usable under NDA or client-confidentiality regimes.
• The rule language is expressive — URL match, regex, folder path. Endlessly deep for the serious tracker.
• It can compare against your iCal — "time you booked for the meeting" vs "time you actually stayed in the meeting".

Pricing (as of 2026):

• Both one-time purchase and subscription tiers.
• Productivity tier — around 9 USD per month or 70 USD per year.
• Professional tier — around 12 USD per month or 100 USD per year.
• 30-day free trial that is unusually generous.

Where Timing wins:

• Single users who do all their work on one Mac.
• Privacy-sensitive contexts — lawyers, medical, government, consulting.
• Precision trackers willing to invest time in rules.

Limits:

• Mac only. No Windows, Linux, or mobile.
• If you do not write rules, you get half the value.

Verdict: if you are a Mac user and care about privacy, top pick. A safe haven for people who do not want their data going to the cloud.

8 · TickTick, Things 3, Hourglass — tasks plus time

There is also a category that fuses to-dos and time, rather than tracking time alone.

TickTick

• To-do app + pomodoro timer + calendar integration.
• A clock icon next to each task — tap to start a 25-minute timer. When it ends, time logs to that task automatically.
• Pricing: free / Premium around 3 to 4 USD per month.

Things 3

• An elegant macOS / iOS-only to-do app.
• Weak on time tracking itself, but pairs well with other trackers.
• One-time purchase — about 50 USD for Mac, 10 USD for iOS, 20 USD for iPad. No subscription.

Hourglass

• A single-purpose tool. Press start, the timer runs; press stop and it ends.
• No reports or billing.
• Free or very cheap.
• For the minimalist who wants nothing but a timer.

Combination patterns:

• Things 3 for task management + Toggl Track for billable time.
• TickTick for both (with weak billing and reports).
• Hourglass + a paper notebook — the lowest-budget combo.

9 · Cosmos and the AI-era "Granola for time"

One interesting newcomer from 2024-2025 is Cosmos. It is often described as Granola (the auto meeting-summary tool) but for time tracking.

Cosmos's concept:

• Records activity automatically (similar to RescueTime / Rize).
• On top of that, an AI summarizes your day every evening — "Morning: 3 hours code review. Afternoon: 4 meetings and work on 2 PRs. After 6pm: 47 minutes on Twitter."
• Natural-language search. "How much did I spend on project ABC last Tuesday?" is a question you can ask.
• Calendar integration — booked meeting blocks vs actual attended time appear side by side.

Why it is interesting:

• Gathering the data is a solved problem since the RescueTime era.
• The hard part is turning that data into "so what?", and LLMs are starting to make that natural.

Things to watch:

• A young tool, so company longevity and the stability of the privacy policy remain unknown.
• AI summaries hallucinate. A "5 hours on ABC" summary could mean 3 hours in reality — always verify against the source data.
• The market moves fast. In a year Cosmos's spot might be taken by another name, or Rize and RescueTime might have absorbed the AI layer.

Verdict: worth trying for early adopters. Keep your main tracker as RescueTime or Rize, and run Cosmos as a secondary tool for a quarter or so.

10 · Privacy reality check

Automatic tracking is fundamentally a surveillance tool. 99% of the time you are surveilling yourself, but the 1% — companies surveilling employees — follows like a shadow.

Personal-use checklist:

1. What data does it collect? Keystrokes? Active windows? Mouse position? Screenshots? It varies tool by tool.
2. Where does the data go? Local disk? Vendor cloud? US, EU, elsewhere?
3. Who sees it? Only you? Your manager? Your teammates?
4. Can you delete it? You should be able to wipe a wrongly-tracked period from a month ago.

Typical answers per tool:

When your employer pushes:

• Tools that force screenshots and keystrokes are increasingly contentious from a labor-rights perspective. In several countries and US states, advance disclosure and consent are mandatory.
• On your personal laptop, an employer cannot install a tracker without consent.
• On a company laptop, company policy typically wins, but monitoring scope should be explicit in your employment agreement and internal policy.

Especially important for developers:

• Wakatime ships filenames and project names to the cloud by default. That can violate client NDAs. Turn tracking off for specific projects, self-host, or enable anonymization.

11 · Real workflows — freelance, deep work, ADHD

Tools are only tools. The real value lives in the workflow. Three representative scenarios.

11.1 Freelance: time to invoice

Stack: Toggl Track plus calendar.

Workflow:

1. New client arrives — create a Toggl client and project.
2. Press the timer before starting work. Add a one-line description like "PR review — auth module".
3. Step away — stop. Toggl Desktop's idle detection often helps.
4. End of month — export Toggl's report as CSV / PDF. Filter for billable hours automatically.
5. Paste into your invoicing tool (Hopper, Bonsai, or a Google Sheet) and send to the client.

Easily missed:

• Reply emails and quote-drafting may be billable. Do not skip them.
• Whether meeting prep is billable should be explicit in the contract.
• When juggling multiple clients, the cost of context switching should be allocated to someone.

11.2 Deep work measurement: how many hours did you really focus?

Stack: Rize.io (or RescueTime) plus a manual note.

Workflow:

1. Every morning, write "today's three deep tasks" on paper.
2. Rize / RescueTime logs all activity in the background.
3. At lunch and again in the evening, check Rize for "how many minutes of deep-work blocks did I get this morning?"
4. Weekly retrospective — "this week's deep-work total: 12 hours. Last week: 18 hours. What was different?"

Realistic expectations:

• 2 to 4 hours of deep work a day is a good day for a typical developer. 8 hours is nearly impossible.
• With 4 or 5 meetings, deep work approaches zero.
• Be deliberate about who sees these numbers. They are for your retrospective, not for your manager.

11.3 ADHD-coping: surface the context switches

For an ADHD developer, the biggest value of time tracking is not billing but self-awareness.

Stack: Wakatime + Rize + a manual journal.

Why this helps:

• Wakatime captures coding time, Rize captures all time.
• The context-switch count is an objective proxy for "how scattered was my brain today?".
• "I switched 47 times today, only 23 yesterday — what was different?" becomes a real question.
• After a month you can see correlations between meds, sleep, caffeine, meeting density, and switch count.

Tips:

• Do not use this as self-punishment. An ADHD brain reads "47 switches" as "I am hopeless". The data is a system-debug tool, not a verdict on your character.
• Do not over-analyze. A weekly 30-minute review is enough. If analysis crowds out the work, you have the means-and-ends backwards.

12 · Cost summary and decision framework

A one-line cost summary as of 2026:

Decision flow:

1. Who are you?

   • Freelancer / consultant — billable hours matter most — Toggl or Clockify.
   • Full-time developer — self-reflection matters most — Wakatime, plus optionally Rize / RescueTime.
   • Team lead — team productivity metrics — Clockify (cheap) or Toggl (premium).
   • Designer / general office worker — Rize.io or RescueTime.

2. Manual or automatic?

   • Conscious tracking needed — manual (Toggl, Clockify, Hourglass).
   • Honest data needed — automatic (Wakatime, RescueTime, Rize, Timing).
   • Both — combine.

3. Privacy sensitivity?

   • Very sensitive — Timing (local) or self-hosted Clockify / Wakatime.
   • Normal — any cloud tool is fine.
   • Employer-mandated — review the contract first.

4. Which OS?

   • Mac only — Timing or Rize.
   • Windows / Linux / mixed — RescueTime, Wakatime, Toggl, Clockify.
   • Mobile included — Toggl or Clockify.

Epilogue — decide what to measure before you measure

Time tracking is, in the end, a conversation with yourself.
The tool does not give you answers.
The tool gives you data to ask better questions.

Of today's 8 hours, how many minutes were real work?
Was that meeting really needed?
Who forced the context switch?
When was deep work even possible?

The point is not that an answer appears.
It is that the questions become sharper.
That is good tracking.

Starting checklist

• Start with one tool and use it daily for at least two weeks.
• Do not analyze in week one. Just collect.
• After two weeks, do the first review. Find the part most different from your expectation.
• After a month, swap the tool without regret if it does not fit you.
• Do not spend more than 30 minutes a day on time tracking itself — that is means becoming ends.

Common anti-patterns

• Obsessing over "perfect categorization" — 80% right is enough.
• Leaving the timer running and waking up to 8 hours of "work" logged.
• Using the data as a self-flagellation tool.
• Forcing teammates to share their numbers.
• Switching tools three times a week.

Next post

The next post is about using the results of tracking. A weekly retro template, a 30-minute PPP (Progress, Plans, Problems) format, calendar-negotiation tactics that cut meeting time by 50% — what you can do once the data exists.

References

• Toggl Track official site: https://toggl.com/track/
• Clockify official site: https://clockify.me/
• Wakatime official site: https://wakatime.com/
• RescueTime official site: https://www.rescuetime.com/
• Rize.io official site: https://rize.io/
• Timing (macOS) official site: https://timingapp.com/
• TickTick official site: https://ticktick.com/
• Things 3 official site: https://culturedcode.com/things/
• Codetime by Software.com: https://www.software.com/
• Pulse for VS Code: search "Pulse time tracking" on the VS Code Marketplace.
• Cal Newport, "Deep Work" — the original deep-work text.
• Anders Ericsson, "Peak" — the science of deliberate practice and measurement.
• "How to Track Your Time as a Developer" — collected developer-time-tracking workflow guides.