So You Want to Use Pokki: What It Actually Is and What It Does
Pokki was a desktop widget and launcher platform. It lived in your system tray and gave you one-click access to games, apps, and utilities without opening a full browser. Think of it as a middle ground between a Start menu and a web browser. You could install it on Windows, put it on your home screen if you wanted, and it would just sit there waiting for a click. I ran Pokki on an old Acer netbook back in 2014. The setup took about five minutes. Download the installer, run it, sign in or skip it, and you get a small square panel that expands when you click it. Behind the scenes, it loads a lightweight Chromium-based renderer and streams content from Pokki's servers. That part is important because it means everything is web-based. If their servers go down, you lose access to anything you were relying on through the platform.
Downloading and Setting Up Pokki
The download used to live at pokki.com. As of my last check, the service has been discontinued and the site redirects to a landing page announcing the shutdown. That means new installs aren't really viable at this point unless you find an archived installer somewhere, which is honestly not something I'd recommend doing. If you're reading this and the site still works in your region, great. Install it like any normal Windows program. After installation, you can pin it to your taskbar, which is useful if your tray gets crowded. Here's where people usually hit a snag: the installer sometimes flags false positives in antivirus software. I had this happen once on a machine running a clean install of Windows 7. Windows Defender and a third-party AV both quarantined the Pokki setup file within seconds. The reason is that Pokki modifies shell entries and runs persistent background processes, which looks suspicious to signature-based scanners. My workaround was straightforward. I temporarily disabled real-time scanning, installed Pokki, then immediately re-enabled the scanner and added the installation folder to the exclusion list. The folder is usually C:\Program Files\Pokki or C:\Users\yourname\AppData\Local\Pokki, depending on whether you did a per-user or system-wide install. Once that was done, it ran fine for months without issues.
What Makes Pokki Different From Other Launchers
The most common comparison is to something like Rainmeter or a traditional start menu replacement. Those tools run locally. Pokki is fundamentally a web app wrapper. It pulls its content from Pokki's infrastructure. This distinction matters because it changes how you should think about performance, reliability, and privacy. For performance, it's actually lighter than most alternatives. The Chromium renderer is shared across all the widgets, so memory usage doesn't scale linearally with each additional app you add. I had it running alongside twelve different widgets and it hovered around 200 megabytes of RAM on a machine with 4 gigabytes total. That's reasonable. But the tradeoff is network dependency. If your internet goes out and you were using anything that required a live connection, Pokki stops working until you're back online. Local-only widgets, like the ones that just launch .exe files from your hard drive, don't have this problem. Everything else does. Privacy is another area worth noting. Since Pokki surfaces content from the web, it passes referrer headers and cookies to whatever services you interact with through it. I noticed this when I was using the streaming games section. The session tracking headers were intact, meaning the services could still fingerprint you the same way a normal browser would. If you're running Pokki on a machine where anonymity matters, this is something to keep in mind. It's not malware, but it's also not privacy-preserving by design.
Get the Full Details

The Shutdown and What That Means for Current Users
Pokki was discontinued. The company pivoted and the platform was retired. This isn't speculation. The developers announced it on their blog and in the app itself. For existing users, the widgets that relied on cloud-hosted content stopped loading within months of the announcement. Local shortcuts that pointed to installed applications still work because those are just saved paths on your disk. But the whole app discovery and download-through-Pokki model is dead. If you still have it installed and it's working for basic things, you can keep using it as a local widget launcher. Don't expect updates. Don't expect new content. Don't share it with people who will need the social features. And definitely don't download it from a random archive site and run it without checking the hash. Modified installers with injected adware are a real risk when you're sourcing software from unofficial channels.
Alternatives Worth Considering Instead
If you liked Pokki for the launcher aspect, Latte Dock on Linux or PowerToys Run on Windows covers most of what it offered and neither depends on a server staying online. For the widget side, Rainmeter still gets regular updates and runs entirely local. If you specifically wanted the Steam-like overlay experience, Steam's own built-in overlay does this natively now without needing a separate piece of software. Honestly, for most people the combination of PowerToys Run plus a taskbar pin solves the same problem Pokki was trying to address, with zero server dependency. One last thing that nobody tells you about Pokki: it doesn't integrate well with multiple monitors in a meaningful way. The widget panel is anchored to one screen. If you move it to another monitor, it sometimes loses its position data on restart and pops back to the primary display. I worked around this by disabling "remember window position" in the settings, restarting, and then dragging it manually to the monitor I wanted before closing it. On the next launch, it tends to remember that monitor, at least until Windows updates the display configuration. Just something to note if you run a dual-monitor setup, which a lot of people do. The bottom line is that Pokki was functional while it lasted. It did one thing decently and that thing was having a desktop interface that felt more immediate than a browser tab. The cloud dependency was always the weak point, and the shutdown proved it. If you find yourself nostalgic for that kind of thing, there are better options now that don't rely on someone else's infrastructure staying alive.