Show HN: Sklad – Secure, offline-first snippet manager (Rust, Tauri v2)
Show HN (score: 10)Description
I built Sklad because, as a DevOps engineer, I was frustrated with how I handled operational data. I constantly need access to SSH passwords (where keys aren't an option), specific IP addresses, and complex CLI one-liners. I realized I was storing them in insecure text files or sticky notes because standard clipboard managers felt too bloated and password managers were too slow for my workflow.
I wanted a "warehouse" for this data—something that lives quietly in the system tray, supports deep hierarchy, works completely offline, and looks industrial.
The app is built with Rust and Tauri v2. The core technical challenge was mapping a local JSON tree structure directly to a recursive native OS tray menu. This allows you to navigate nested folders just by hovering, without opening a window.
For security, I implemented AES-256-GCM encryption with Argon2 for key derivation. When the vault locks, the sensitive data is wiped from memory, and the tray menu collapses to a locked state.
It was an interesting journey building this on the Tauri v2 Beta ecosystem. I’d love to hear your feedback on the implementation, especially regarding the Rust-side security logic.
More from Show
Show HN: Config manager for Claude Code (and others) – rules, MCPs, permissions
Show HN: Config manager for Claude Code (and others) – rules, MCPs, permissions I use Claude Code across multiple projects with different conventions and some shared repos just as it so happens to be the real world. Managing the config files (.claude/rules/, mcps.json, settings.json) by hand got tedious, so I built a local web UI for it.<p>This one started out as claude-config but migrated to coder-config as I'm adding others (Gemini, AG, Codex, etc).<p>Main features: - Visual editor for rules, permissions, and MCP servers - Project registry to switch between codebases - "Workstreams" to group related repos (frontend + API + shared libs) with shared context - Auto-load workstreams on cd to included folders - Also supports Gemini CLI and Codex CLI<p>Install: npm install -g coder-config coder-config ui # UI at http://localhost:3333 coder-config ui install # optionally, autostart on MacOS<p>It can also be installed as a PWA and live in your taskbar.<p>Open source, runs locally, no account needed. Feedback and contributions welcome!<p>Sorry, haven't had any chance to test on other OSes (linux/windows)
Show HN: React-like Declarative DSL for building synthetic LLM datasets
Show HN: React-like Declarative DSL for building synthetic LLM datasets
Show HN: UnisonDB – Log-native KV database that replicates like a message bus
Show HN: UnisonDB – Log-native KV database that replicates like a message bus Hi HN,<p>For the past few months, I’ve been building UnisonDB — a log-native database where the Write-Ahead Log (WAL) is the database, not just a recovery mechanism.<p>I started this because every time I needed data to flow — from core to edge, or between datacenters — I ended up gluing together a KV database + CDC + Kafka.<p>It worked, but it always felt like overkill: too many moving parts for even small workloads, and too little determinism.<p>What is it?<p>UnisonDB unifies storage and streaming into a single log-based core. Every write is: • Durable (appended to the WAL), • Ordered (globally sequenced for safety), • Streamable (available to any follower in real time).<p>It combines B+Tree storage (predictable reads, no LSM compaction storms) with WAL-based replication (sub-second fan-out to 100+ nodes).<p>Key Ideas<p>1. Storage + Streaming = One System — no CDC, no Kafka, no sidecar pipelines<p>2. B+Tree-Backed — predictable reads, zero compaction overhead<p>3. Multi-Model — KV, wide-column, and large objects (LOB) in one atomic transaction<p>4. Replication-Native — WAL streams via gRPC; followers tail in real time<p>5. Reactive by Design — every write emits a ZeroMQ notification<p>6. Edge-Friendly — replicas can go offline and resync instantly<p>Performance & Tradeoffs 1. Write throughput is lower than pure LSM stores (e.g. BadgerDB) — because writes are globally ordered for replication safety. Deliberate tradeoff: consistency > raw write speed.<p>2. Still ~2× faster than BoltDB with replication enabled.<p>Tech Details<p>Written in Go<p>FlatBuffers for zero-copy serialization<p>gRPC for streaming replication<p>GitHub: <a href="https://github.com/ankur-anand/unisondb" rel="nofollow">https://github.com/ankur-anand/unisondb</a>
Show HN: A context aware backend for AI coding agents
Show HN: A context aware backend for AI coding agents Hey HN, I’m Hang. Today I’m open-sourcing InsForge, a context aware backend for AI coding agents.<p>When using agents like Cursor or Claude to build applications, they often assume what the backend looks like instead of inspecting it. Without access to the actual backend state, they fall back on outdated information, which leads to concrete issues. For example:<p>1. Storage, edge functions, and database logic are closely connected. Without understanding how these parts interact, existing setups get overwritten and important flows break. 2. Database migrations conflict with foreign keys or miss functions because the agent never inspects the live schema. 3. Recreating tables or adding columns that already exist, which leads to conflicts and failed deploys.<p>These problems are not about the agent’s ability to code. They happen because there’s no structured way for the agent to inspect and understand the actual backend before acting.<p>To address this, I built InsForge, which exposes the backend in a structured way and gives the agent direct control:<p>1. Introspection endpoints for schema, relations, functions, triggers, policies, routes, storage, roles, documentation, logs and events 2. Control endpoints for operations usually done through CLI, dashboards or SQL editors<p>InsForge is a full backend platform that includes:<p>- Postgres - Authentication - Storage - Edge functions - Built in AI-model endpoints (via OpenRouter)<p>On top of this, it exposes structured backend metadata and control capabilities through an MCP server and tools, providing a structured, self-describing interface for agents to inspect schemas, policies, triggers, and docs, and interact with the backend.<p>It’s open source and can be self hosted (<a href="https://github.com/InsForge/InsForge" rel="nofollow">https://github.com/InsForge/InsForge</a>) or try our cloud service at (<a href="https://insforge.dev/" rel="nofollow">https://insforge.dev/</a>).<p>We love feedback!
No other tools from this source yet.