What Is Ikuna? A Focus Intelligence and Context Manager for macOS

Part of the Ikuna series: a five-piece brand story:

What Is Ikuna· Why I Built It · Updates in 2026 · More Than a Window Manager · The Science Behind It

Ikuna is a focus intelligence and context manager for macOS. That's the one-sentence answer.

Here's why that sentence isn't enough on its own. If you've heard the name mentioned somewhere and landed here looking for a straight definition, you're probably trying to figure out whether this is a window manager, a task manager, a Focus Mode wrapper, or something else entirely. The short answer is: none of those, though it touches all of them. The longer answer is that Ikuna does something specific that doesn't fit neatly into existing categories, and the three-part phrase "focus intelligence and context manager for macOS" is the most honest way I've found to describe what it actually does. This article unpacks that phrase, walks through what the product does mechanically, what it doesn't do, who it's for, and how it fits into a working day.

The one sentence, unpacked

Focus intelligence and context manager for macOS. Three phrases, in that order, for a reason.

Focus intelligence is the product. It's the part that matters most and the part that took the longest to build. Ikuna shows you the shape of your own attention: how long you stay in a context before switching, when in the day your deep blocks happen, how often a context is interrupted before it reaches twenty minutes. Most knowledge workers have never seen this data. I hadn't, until we built it. The dashboard is quiet, not gamified, and it tells you things about your own behaviour that are hard to see from the inside. That's the intelligence layer, and it's what separates Ikuna from tools that stop at the mechanism.

Context manager is the mechanism. A context, in Ikuna's terms, is a named project state: the apps that should be open, the exact browser tabs in each window, the window positions, the monitor layout. You save a context once. After that, you can rebuild it in under three seconds, leave it for three days, and come back to exactly where you were. The mechanism is save and restore. The reason the mechanism matters is that it makes switching between projects cheap enough that you actually do it, which means each project gets its own cognitive environment, which is what the brain needs to focus without leaking attention residue from the previous task.

For macOS is the platform. Ikuna runs on macOS 13 and later, native on Apple Silicon and Intel. It uses the Accessibility API to detect and position windows, which means it requires permission but keeps all data on-device. No telemetry, no cloud sync, EU-hosted when you do use the web (for checkout and account management). The macOS constraint is deliberate. The product is built around what macOS allows and what Mac professionals actually need, not a cross-platform abstraction.

Put the three together and you get the definition: a tool that helps you see and improve how you focus, by giving each project its own rebuildable environment, on the platform where most knowledge work happens.

What Ikuna actually does

This is the mechanical walkthrough. Five named features, one paragraph each.

Save & restore contexts. You name a context ("Client A," "Deep Writing," "Research"), open the apps and tabs and windows you need for that project, arrange them how you want, and save. After that, switching to that context rebuilds the full state in under three seconds: apps launch, browser tabs reopen in the right windows, windows move to the right positions, external monitors reconnect to the right layout. You're not reconstructing. You're resuming. The speed matters because it makes the boundary between projects cheap enough that you use it multiple times a day, which is what actually reduces context-switching cost.

Focus Intelligence. The dashboard shows you how you actually focus. How long you stay in each context before switching. When in the day your deep blocks happen. How many times a context is interrupted before it reaches the twenty-minute threshold that the research says matters. The data is on-device, not sent anywhere, and it's not gamified. No streaks, no points, no social comparison. Just a quiet external view of your own attention, which turns out to be the thing most people have never had and the thing that makes the biggest difference once you do.

Focus Shield. This is Ikuna's own attention-guarding layer, not a wrapper around macOS Focus Modes (the API doesn't allow it). You set per-context distraction rules: which apps and sites to block, which to allow. When you're in a shielded context and try to open a blocked app or site, Ikuna shows a gentle nudge first, then escalates to a full-screen block if you try again. The escalation matters. A nudge respects agency. A hard block respects the decision you made when you weren't in the moment. The two together work better than either alone.

Rituals & triggers. Each context can have its own wallpaper, opening video, and playlist. When you enter the context, the ritual fires automatically. The content doesn't matter as much as the repetition. After about a week, the ritual becomes a reliable trigger for the cognitive state you associate with that context. This is the same mechanism athletes use to enter performance mode, and it's the same mechanism the office commute used to provide accidentally. Ikuna makes it deliberate and repeatable.

Device Link. When you disconnect an external monitor and reconnect it later, Ikuna remembers which context was on which display and rebuilds the layout automatically. This sounds minor until you're a consultant switching between home and client offices three times a week, or a developer who docks and undocks twice a day. The mechanism is simple: Ikuna detects the display configuration, matches it to the context, and restores. The result is that your multi-monitor setup stops being a thing you have to think about.

What Ikuna is NOT

This is the disarming honesty section, and it matters because the surface of the product can mislead.

Ikuna is not a window manager. If it reads that way at first glance, that's fair. We deliberately put window snapping on the surface because it's the instant, obvious benefit. But the snapping is not the point. The point is the full context: apps, tabs, layouts, rituals, and the intelligence layer on top. Window managers stop at positioning. Ikuna starts there and goes several layers deeper.

Ikuna is not a task manager. It doesn't track todos, deadlines, or dependencies. It tracks cognitive state. The unit of organisation is the context, not the task. If you need to manage what to do, use a task manager. If you need to manage the environment in which you do it, that's what Ikuna is for.

Ikuna is not a Focus Mode wrapper. The macOS Focus Mode API doesn't allow third-party tools to trigger or extend Focus Modes. Focus Shield is Ikuna's own layer, built from scratch, with its own rules and its own escalation logic. It works alongside Focus Modes if you use them, but it's not dependent on them and doesn't try to be.

Ikuna is not a Spaces replacement. macOS Spaces are good at visually grouping windows. Ikuna swaps the app and tab and window set in place on the active space. The two can coexist, but they're solving different problems. Spaces give you multiple desktops. Ikuna gives you rebuildable project states within a desktop.

The reason I'm spelling this out is that the category confusion is real, and it leads people to compare Ikuna to tools it's not competing with. If you're looking for a window manager, there are simpler options. If you're looking for the intelligence layer, the ritual triggers, the per-context attention guard, and the ability to see the shape of your own focus, Ikuna is the only tool I know of that does all of that in one place.

Who it's for

About 1,000 Mac professionals are using Ikuna right now. The archetypes are consistent.

Consultants and freelancers juggling three to five clients. Each client is a context. Each context has its own Slack workspace, browser profile, project files, and CRM view. Switching between them used to mean ten minutes of tab archaeology. Now it's three seconds and a ritual that tells your brain which client you're in.

Developers switching between codebases. Each codebase is a context. Each context has its own IDE window, terminal sessions, documentation tabs, and Spotify playlist. The ability to leave a context mid-debug, work on something else for two days, and come back to the exact state you left is the difference between flow and frustration.

Founders wearing five hats. Product, sales, ops, finance, hiring. Each hat is a context. Each context has its own apps, tabs, and mental mode. The dashboard shows you which hat you're actually spending time in versus which one you think you are, and that gap is usually the first thing that needs fixing.

Researchers with multiple concurrent studies. Each study is a context. Each context has its own literature tabs, data files, analysis scripts, and writing doc. The ability to keep the states separate, and to see how much deep time each study is actually getting, turns out to matter more than any single productivity technique.

If you're a knowledge worker who does one thing, in one app, all day, Ikuna is probably overkill. If you're juggling multiple projects with different cognitive demands, and you've noticed that switching between them costs more than it should, that's exactly who this is for.

How it fits into a day

Here's what it looks like in practice, using my own day as the example.

Morning. I open the laptop, trigger the "Deep Writing" context. The ritual fires: wallpaper shifts to a specific dark gradient, a specific piece of music plays for thirty seconds, the writing doc and research tabs rebuild in the positions I saved. Three seconds, total. By the time the music fades I'm already in the mode. I stay in that context until 10:30, which the dashboard will later tell me was 90 minutes of uninterrupted deep time.

Mid-morning. I close "Deep Writing" and switch to "Customer Calls." The CRM opens, the notes doc opens, the browser switches to the customer-facing profile, the Slack window moves to the second monitor. Focus Shield activates: personal email is blocked, Twitter is blocked, Hacker News is blocked. The ritual plays a different piece of music. I'm in a different mode now, and the environment reflects it.

Afternoon. I switch to "Product Work." The Figma file, the GitHub issues, the Slack engineering channel, all rebuild in the layout I saved. I stay in that context for two hours, interrupted three times by messages. The dashboard will show me those interruptions later, and I'll see that the third one cost me the rest of the block.

Evening. I close "Product Work" and don't open another context. The laptop is still on, but I'm not in work mode anymore. The boundary is clear because the environment changed.

That's the day. Four contexts, three switches, each switch taking under five seconds including the ritual. The dashboard shows me that I got 90 minutes of deep writing, two hours of product work with three interruptions, and 45 minutes of customer calls. The data is honest. The environment did the work of holding the boundaries. I didn't have to spend willpower on the question of what mode I was in.

Where it runs, what it costs

Ikuna runs on macOS 13 and later, native on Apple Silicon and Intel. It requires Accessibility API permissions to detect and position windows. All data stays on-device. No telemetry, no cloud sync.

There's a free plan at brnsft.com/ikuna. Up to four contexts, multi-monitor support, basic dashboard. No card required.

Pro is €9 per month if you pay monthly, or €6 per month if you pay yearly (€72 per year, saves 33%). Unlimited contexts, full Focus Intelligence dashboard, Focus Shield, Rituals & triggers, Device Link. 14-day money-back guarantee. Checkout is via Paddle, EU VAT handled automatically. You can get Pro at ikuna.app.

The free plan is real. It's not a trial. If four contexts is enough for you, you can use Ikuna indefinitely without paying. The Pro tier is for people who need more contexts or who want the full intelligence and ritual layers.

FAQ

Is Ikuna a window manager? No, though I understand why it looks that way. Window snapping is on the surface because it's the instant, obvious benefit. The actual product is the intelligence layer (the dashboard that shows you how you focus), the ritual triggers (wallpaper, music, video on context entry), the attention guard (Focus Shield), and the ability to save and restore full project states (apps, tabs, layouts). Window managers stop at positioning. Ikuna starts there and goes several layers deeper. If you only need snapping, there are simpler tools. If you need the full stack, that's what Ikuna is for.

How is Ikuna different from BetterStage / Workspaces by Apptorium / Spencer? BetterStage and Workspaces are workspace switchers. They launch apps per workspace. Ikuna restores the exact browser tabs, window positions, and monitor layouts, not just the apps. Spencer saves window layout snapshots. Ikuna saves the full context including apps and tabs, plus the intelligence dashboard and Focus Shield on top. The wedge is the intelligence layer. Competitors stop at the mechanism. Ikuna adds the analytics and the behavioral guard.

Does Ikuna work with macOS Focus Modes? Ikuna's Focus Shield is its own layer, not a wrapper around macOS Focus Modes. The macOS Focus Mode API doesn't allow third-party tools to trigger or extend Focus Modes. Focus Shield is built from scratch, with its own per-context distraction rules and its own nudge-then-block escalation logic. If you use macOS Focus Modes, Ikuna works alongside them, but it's not dependent on them.

Is my data sent anywhere? No. All context data, window positions, app lists, browser tabs, and Focus Intelligence metrics stay on-device. Ikuna doesn't phone home, doesn't sync to a cloud, and doesn't send telemetry. The only network requests are for account management (if you're on Pro) and checkout (via Paddle, EU-hosted). The Accessibility API permission is required to detect and position windows, but the data never leaves your Mac.

What's the difference between the free plan and Pro? The free plan gives you up to four contexts, multi-monitor support, and a basic dashboard. Pro gives you unlimited contexts, the full Focus Intelligence dashboard with per-context deep-work metrics and switching patterns, Focus Shield with per-context distraction blocking, Rituals & triggers (wallpaper, music, video on entry), and Device Link for automatic multi-monitor layout restoration. If four contexts is enough and you don't need the intelligence or ritual layers, the free plan is a real, indefinite option. If you need more contexts or the full stack, that's Pro.

Ikuna is the focus intelligence and context manager for macOS. It rebuilds full project contexts, apps, tabs, windows, monitor layouts, in under three seconds, fires per-context rituals on entry, and shows you the shape of your own attention through Focus Intelligence. Free plan at brnsft.com/ikuna. Pro at ikuna.app.