Thanks for the link! Atuin is a powerful tool, especially with their focus on command management and execution.
From my perspective, the main difference is the UI footprint and the intended use case. Sklad is intentionally 'passive' and limited to the system tray. It’s not meant to be a full window or a command runner/executor. I built it as a simple warehouse for static data — like passwords, specific IPs, or boilerplate templates — that I need to grab quickly and paste anywhere, whether it’s a terminal, a browser, or a GUI prompt.
I also focused heavily on the recursive folder hierarchy within the native tray menu itself to help with mental mapping, whereas Atuin (and its UI) feels more search-centric and terminal-focused. I think there’s definitely room for both depending on whether you need to execute a command or just grab a piece of secure data.
This is an incredible suggestion. Transitioning Sklad into a "UI-client-as-a-bridge" for established password managers is a fantastic idea for a v2 or a plugin-based architecture.
The point about narrowing the "crypto surface area" is especially sharp. By leveraging the 1Password SDK or KeePassXC-proxy, Sklad could focus entirely on the navigation UX while delegating the heavy lifting of security, sync, and recovery to battle-tested giants.
For the initial launch, I opted for a standalone approach for a few reasons:
1. Zero Dependencies: I wanted a tool that works "out of the box" for developers who might not use a specific password manager or want to keep their CLI/DevOps snippets entirely isolated from their main vault.
2. The "Warehouse" Vibe: Keeping it local-only and standalone fits the "industrial warehouse" aesthetic—you own the file, you own the key, no external APIs involved.
3. Simplicity: As a first step, building a "sovereign" vault was easier to reason about architecturally before diving into complex SDK integrations.
However, I am now seriously considering a "Bridge Mode" where Sklad could act as a fast-access frontend for 1Password/KeePassXC. It would be the best of both worlds: industry-standard security with a "muscle memory" tray interface.
Thank you for this—it’s given me a very clear roadmap for where this could go next!
You hit the nail on the head regarding the separation of concerns. I specifically built this because polluting my "High Security" vault (KeePassXC) with temporary server IPs and bash one-liners felt wrong.
Regarding the stack (Tauri vs. Native):
That is a valid critique. I considered native (SwiftUI/GTK), but Linux support was a hard requirement for the DevOps use case. I couldn't justify maintaining three separate native codebases.
To mitigate the supply chain risk, I tried to keep the architecture as follows:
1. Dumb Frontend: The React side is purely for UI.
2. Rust Backend: All file I/O, encryption (AES-GCM), and key management happen in Rust. While crates.io isn't immune to supply chain attacks, I find the dependency tree generally easier to audit and lock down than a massive Electron+Node modules dependency graph.
But I agree—for "life-critical" secrets (banking, root CA keys), a battle-tested native app (or even an air-gapped machine) is always the superior choice. Sklad is for the operational layer where velocity matters more than absolute paranoia.
Great question. I'm a long-time user of KeePassXC myself, and I see Sklad as complementary to it, not a replacement.
The main difference is the workflow and friction.
1. Tray-First vs. Window-First: KeePassXC is primarily window-based. Even with the tray icon, retrieving a specific entry usually involves opening the window, searching (Cmd/Ctrl+F), and copying. Sklad exposes your entire folder hierarchy as a native recursive tray menu. You right-click the icon, hover through `Servers -> Client A -> SSH Key`, and click to copy. It allows for "muscle memory" access without ever switching focus or managing windows.
2. Snippets vs. Credentials: I use KeePassXC for high-security web logins and bank details. I built Sklad for "operational" data—SSH keys, complex CLI one-liners, specific IP addresses, and env vars that I need to grab 20 times a day.
3. Hierarchy Visualization: Sklad allows you to visualize the tree structure instantly via the menu, which feels faster for mental mapping of infrastructure than a flat search list.
In short: KeePassXC is a vault; Sklad is a quick-access utility belt.
From my perspective, the main difference is the UI footprint and the intended use case. Sklad is intentionally 'passive' and limited to the system tray. It’s not meant to be a full window or a command runner/executor. I built it as a simple warehouse for static data — like passwords, specific IPs, or boilerplate templates — that I need to grab quickly and paste anywhere, whether it’s a terminal, a browser, or a GUI prompt.
I also focused heavily on the recursive folder hierarchy within the native tray menu itself to help with mental mapping, whereas Atuin (and its UI) feels more search-centric and terminal-focused. I think there’s definitely room for both depending on whether you need to execute a command or just grab a piece of secure data.