kando.menu

No. According to Kando's official website, Kando is privacy-first: it has no telemetry, no tracking, and no cloud. Your data stays on your machine. This applies to the core application as described on kando.menu — it does not send your usage data to the developers or any third party.

What "No Telemetry, No Tracking, No Cloud" Means

Kando's site states three specific commitments:

• No telemetry — Kando does not automatically report usage statistics, feature interactions, or performance data back to its developers.
• No tracking — there is no analytics or behavioral tracking built into the app.
• No cloud — Kando does not upload your menus, configuration, or files to a remote server. Your setup lives locally.

The stated design principle is that your data stays on your machine. For a tool that launches apps, runs macros, and opens files, this matters: the menu configuration itself can reveal what you work with, so keeping it local avoids exposing that to a vendor.

Where Your Data Actually Lives

Because Kando is a local, cross-platform desktop app (Windows, macOS, and Linux), the data it works with is on your own system:

Kando is also open source, so the claim is independently verifiable — you or anyone else can inspect the code rather than taking the statement on trust. That is a stronger position than a closed-source app making the same promise.

Practical Caveats to Keep in Mind

The privacy statement covers Kando itself. A few things sit outside that scope:

• Your OS and other software may still log activity independently of Kando.
• If you download Kando from GitHub, the download and any update checks involve GitHub's own infrastructure, which has its own privacy terms — separate from Kando's in-app behavior.
• Links on the site (for example, the YouTube video) are third-party services with their own tracking.
• "No cloud" describes Kando's design, not a guarantee about every file you choose to open — if a file itself lives in a synced folder, your sync provider handles it.

Bottom Line

If your concern is whether Kando phones home with your usage data, the official answer is no: no telemetry, no tracking, no cloud, data stays local. The open-source nature means you can confirm this rather than rely on the claim alone. The main things to watch are the surrounding services — your OS, GitHub, and any third-party links — which fall outside Kando's own privacy design.

An open-source UI element library is a collection of individual, ready-made interface pieces—buttons, cards, inputs, toggles, loaders—that you copy into your own project and adapt. A UI framework, by contrast, is a structured system of components, conventions, and often a theming layer that governs how your whole interface is built. The practical difference: an element library gives you a snippet; a framework gives you a way of working. If you need a polished button in ten minutes, reach for the element library. If you're building a 40-screen product with a team, you probably want the framework.

What "open-source UI element library" actually means

The term gets used loosely, so it helps to separate the parts:

• Open-source: the code is publicly available, and the license tells you what you may do with it—copy, modify, redistribute, or use commercially.
• UI element: a single, self-contained piece of interface, usually small enough to read in one sitting. A button with hover states, a pricing card, a search field.
• Library: a browsable, searchable collection of those elements, typically contributed by many different people.

On a site like Uiverse, elements are shared by a community and written in plain CSS or Tailwind. You find one you like, copy the markup and styles, paste them into your project, and adjust colors, spacing, and text to fit. There's no package to install and no build step required—which is exactly the appeal, and also the source of most of the confusion.

Element library vs. UI framework: the core differences

The table isn't a verdict. It's a map of trade-offs. Element libraries win on speed and freedom; frameworks win on consistency and maintenance.

Licensing and attribution: what to check before you paste

This is where people get into trouble, and it's worth slowing down for.

1. Find the license. Every element or collection should state one. Common open-source licenses include MIT, Apache-2.0, and BSD. Some projects use copyleft licenses like GPL, which can impose obligations if you redistribute your code.
2. Understand what the license permits. MIT and Apache-2.0 are permissive: you can typically use the code in commercial and closed-source projects. Copyleft licenses may require you to release derivative source under the same terms.
3. Check attribution requirements. Permissive licenses usually require you to keep the copyright notice and license text somewhere in your project. That's a real obligation, not a formality.
4. Look for per-element terms. On community sites, the site's overall terms and the individual contributor's stated wishes may differ. If a contributor asks for credit, honor it.
5. When in doubt, ask or avoid. If a snippet has no license at all, you don't have clear permission to reuse it. Treat "no license" as "not open source," even if the code is publicly visible.

This article is general information, not legal advice. For commercial products with real exposure, have someone qualified review the licenses you're relying on.

How to use a community element in your project: a practical workflow

Here's a repeatable process that avoids most of the usual mess.

1. Start from a real need, not a browsing session

Decide what you need first—"a compact primary button with a loading state"—then search. Browsing aimlessly produces a pile of pretty snippets that don't fit together.

2. Copy the smallest version that works

Take the markup and the styles. Strip anything you don't need: demo wrappers, extra animations, decorative layers. Less code means fewer surprises.

3. Convert it to your conventions

If your project uses design tokens or CSS variables, replace hard-coded values:

/* Before: hard-coded */
.button { background: #4f46e5; border-radius: 8px; }

/* After: token-based */
.button { background: var(--color-primary); border-radius: var(--radius-md); }

This one step is what keeps a copied element from looking like a foreign object in your UI.

4. Check accessibility before you ship

Community elements vary widely here. Verify at minimum:

• Keyboard focus is visible and the element is reachable by Tab.
• Color contrast meets WCAG AA (4.5:1 for normal text).
• Interactive elements use semantic HTML (<button>, not a clickable <div>).
• Form inputs have associated labels.
• Motion respects prefers-reduced-motion.

5. Test in context

Paste it into a real page with real content. Long labels, small screens, and dark mode break more copied elements than anything else.

6. Note where it came from

Keep a short comment or an internal credits file: source, license, date. Future you—and your legal reviewer—will be grateful.

Where element libraries genuinely shine

• Prototypes and demos: you need something clickable today, not a design system.
• Landing pages and marketing sites: a handful of distinctive elements, each custom.
• Filling gaps: your framework lacks one specific component, and you don't want to build it from scratch.
• Learning: reading well-made CSS is one of the fastest ways to improve.
• Small projects: a personal site doesn't need a theming architecture.

Where they fall short

• Consistency at scale: ten elements from ten contributors rarely look like one product.
• Maintenance: you own every copy. When your design changes, you edit each one.
• Accessibility debt: you inherit whatever the contributor did or didn't do.
• No upstream fixes: a bug fixed in the original won't reach your copy.
• Integration friction: different naming conventions, different units, different assumptions about resets.

When to choose which

Choose an element library when the scope is small, the timeline is short, or you need a few distinctive pieces rather than a whole system.

Choose a framework or design system when multiple people build multiple screens over months, when consistency is a product requirement, or when accessibility and theming need to be guaranteed rather than checked.

A hybrid works well for many teams: adopt a framework for the structural components—forms, navigation, layout—and borrow individual elements for the places where you want personality. Just route every borrowed element through the same token and accessibility checks, so it lands as part of your system rather than beside it.

The short version: open-source UI element libraries are a fast, flexible way to get good-looking interface pieces into a project. They are not a substitute for a design system, and the license and accessibility details are the part worth reading carefully.

Kando runs on Windows, macOS, and Linux, and it accepts mouse, stylus, touch, and controller input. That combination means you can use the same pie menu concept whether you are on a desktop with a mouse, a tablet with a pen, a touchscreen laptop, or a setup with a game controller. The menu configuration itself is cross-platform, so a menu you build on one operating system can be used on another.

Supported operating systems

Kando is described as a cross-platform pie menu, with availability for:

• Windows
• macOS
• Linux

The project presents this as "one menu to rule them all," meaning the same menu setup is intended to work across these platforms rather than being locked to a single OS.

Supported input devices

Kando is designed to be used with any of the following:

The core idea is that you do not need to aim at small buttons. Your entire screen becomes a click target, so an approximate directional movement is enough to select an item, including items in nested submenus.

What this means in practice

Because Kando supports multiple input types and all three major desktop platforms, you can:

• Use one tool across devices — the same menu system works whether you are on a Windows desktop, a Mac, or a Linux machine.
• Switch input methods — if you normally use a mouse but sometimes work with a stylus, touch, or controller, Kando is built to handle that without a separate tool.
• Rely on muscle memory — selection is gesture-based, so the same directional movements apply regardless of which input device you are using.

Platform and device notes

• Cross-platform menus: Kando supports opening different menus depending on the current application or window, so you can have a dedicated menu per application. This behavior is part of the cross-platform design.
• No cloud dependency: Kando states it has no telemetry, no tracking, and no cloud, so your data stays on your machine. This applies across the supported platforms.
• Free and open source: Kando is described as completely free and open source, available on GitHub, with documentation available for setup.

If you want to confirm the exact current build for your specific OS version, the Kando documentation and GitHub releases are the authoritative sources, since platform support details can change between updates.

Yes. Kando is completely free and open source, and according to the project itself, it always will be. It is described as a passion project built for the community, with no paid tier mentioned anywhere on the site. You can get it by downloading it from GitHub, and the documentation is available separately for setup and usage guidance.

What "free and open source" means here

The Kando website states plainly that Kando "is and always will be completely free and open source." That covers two separate things worth distinguishing:

• Free: there is no price attached to using it. The site presents no pricing page, subscription, or payment option.
• Open source: the source code is publicly available, and the project is distributed through GitHub rather than a closed storefront.

Because it is community-oriented, development is framed as a passion project rather than a commercial product. The site also notes that Kando receives regular updates, with the most recent one having overhauled the menu action system so workflows can run multiple actions in sequence.

How to get Kando

1. Go to the Kando website (kando.menu).
2. Use the Download on GitHub link to reach the repository and download the application.
3. If you want to understand configuration before installing, use the Read the Docs link first.

The site does not specify system requirements, installer formats, or package-manager options, so check the GitHub repository and documentation for the current download details.

What you get for free

The free download includes the full feature set described on the site:

Privacy as part of the deal

Kando states it is privacy-first: no telemetry, no tracking, no cloud. Your data stays on your machine. That matters for a free tool, because it means the project is not monetizing usage data in place of a purchase price. The site does not describe any account creation or login requirement.

Things the site does not answer

A few practical questions are not covered by the available material, so treat them as open:

• Whether donations are accepted or how the project is funded.
• The exact license text (the site says open source but does not name a license).
• Minimum OS versions or hardware requirements.
• Whether prebuilt binaries exist for every platform or whether some require building from source.

For all of these, the GitHub repository is the authoritative place to look.

Bottom line

If your question is simply whether Kando costs money or is closed off, the answer is no on both counts. It is free, open source, cross-platform, and distributed via GitHub, with documentation available for setup. The main thing left to verify before installing is platform-specific download and requirement details, which live in the repository rather than on the landing page.

Kando is a free, open-source, cross-platform pie menu that replaces hunting through menus and remembering key combinations with directional gestures. You can use it to launch applications, run multi-step workflows or keyboard macros, open files and folders, and trigger actions that change depending on which app or window is active. It fits you if you work primarily with a mouse, stylus, touch, or controller and want your most frequent actions one gesture away; it is less useful if you prefer keyboard-only navigation or need actions to run on a remote or cloud machine, since Kando keeps your data local.

Launch apps with a single gesture

Instead of clicking through a dock, Start menu, or launcher, you open a Kando menu and throw your cursor roughly toward the app's slice. Kando treats your entire screen as the click target, so you do not have to land on a small button — approximate direction is enough. This is the most common starting point for new users and the easiest way to test whether gesture-based selection suits your muscle memory.

Execute multi-step workflows and keyboard macros

A single Kando selection can trigger a sequence of actions rather than one keystroke. The site notes that the latest update overhauled the menu action system, so you can now build workflows that execute multiple actions in sequence. Practical uses include:

• Pasting a saved snippet and then switching windows
• Running a chain of keyboard shortcuts you would otherwise have to remember
• Combining an app launch with a file open or a window arrangement

The trade-off is setup time: complex sequences take longer to configure than a simple app shortcut, so build them for tasks you repeat often.

Open files and folders quickly

Kando menus can point directly at frequently used files and folders, so you navigate to them in milliseconds rather than through a file manager. This works well for project directories, reference documents, or export folders you return to daily.

Select items through gesture and muscle memory

Kando supports nested menus, and its gesture recognition is designed to let you reach items in sub-sub-submenus without visually tracing each level. The intended effect is that after repetition you select items from muscle memory alone. The site frames this as a gradual path from beginner to expert, with achievements along the way for motivation.

Use different menus per application

Kando can open different menus depending on the current application or window. That means you can keep a dedicated menu for each of your favorite apps — for example, one set of actions while an editor is focused and another while a browser is focused — instead of one generic menu for everything.

Match your input device and platform

When Kando is a good fit — and when it is not

Kando suits you if you want to reduce pointer travel, if you repeat the same handful of actions across the day, or if you use a stylus, touch, or controller where precise clicking is awkward. It is a weaker fit if your workflow is already fast from the keyboard, if you only need one or two shortcuts, or if you want your automations to run somewhere other than your own machine.

Because Kando is open source and free, the main cost of trying it is the time you spend configuring your first menu. A reasonable approach is to start with one menu containing your five most-used apps, use it for a few days, and only then add nested menus or multi-action workflows.