←
Gul Saeed Khattak2,411 posts
Gul Saeed Khattak avatar

Gul Saeed Khattak

@Ldataengineer

Lead Data Engineer at the University of Glasgow, exploring the future of data and AI through autonomous agents, and agentic workflows

◷ Joined June 2023▧ 378 Photos and videos
Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·Nov 16

𝗜 𝗧𝗿𝗶𝗲𝗱 𝗪𝗲𝗶𝗴𝗵𝘁-𝗦𝗽𝗮𝗰𝗲 𝗣𝗿𝗼𝗴𝗿𝗮𝗺𝗺𝗶𝗻𝗴 𝗼𝗻 𝗠𝘆 𝗗𝗚𝗫 𝗦𝗽𝗮𝗿𝗸 𝗪𝗶𝘁𝗵 𝗖𝗹𝗮𝘂𝗱𝗲 𝗙𝗮𝗯𝗹𝗲 𝟱.𝟮 𝗮𝘀 𝘁𝗵𝗲 𝗪𝗿𝗶𝘁𝗲𝗿, 𝗮𝗻𝗱 𝗔𝗰𝗰𝘂𝗿𝗮𝗰𝘆 𝗪𝗲𝗻𝘁 𝗙𝗿𝗼𝗺 𝟱𝟯% 𝘁𝗼 𝟳𝟭% Spent the weekend on weight-space programming. The idea: one LLM reads another network's weights and edits them directly. No gradients, no fine-tuning. I used dspy-wsp from cmpnd-ai, which builds on "Sparks of Weight-Space Programming" by Takehi, Teoh, Zhang and Khattab. The Two Models: The model being fixed is LiquidAI d1-omni-600M, a small open model (about 587M weights) running on the Spark's GPU. It reads a business record, say an invoice or a security alert, and answers 5 questions about it. The model doing the fixing is called the writer. It gets a locked Python sandbox with the small model inside and 25 runs over the data. 𝗙𝗶𝗿𝘀𝘁 𝗧𝗿𝘆: 𝗠𝘆 𝗟𝗼𝗰𝗮𝗹 𝗤𝘄𝗲𝗻𝟯.𝟴-𝟮𝟳𝗕: I tried my local Qwen3.8-27B first because it's free. Went to bed and let it work. 𝟲.𝟵 𝗵𝗼𝘂𝗿𝘀 𝗹𝗮𝘁𝗲𝗿 𝗶𝘁 𝗵𝗮𝗱𝗻'𝘁 𝘀𝗮𝘃𝗲𝗱 𝗮 𝘀𝗶𝗻𝗴𝗹𝗲 𝗲𝗱𝗶𝘁. +0.0. (To be fair, I gave it 90 code runs instead of the default 300, and 36 of them crashed.) 𝗦𝗲𝗰𝗼𝗻𝗱 𝗧𝗿𝘆: 𝗖𝗹𝗮𝘂𝗱𝗲 𝗙𝗮𝗯𝗹𝗲 𝟱.𝟮 𝗧𝗵𝗿𝗼𝘂𝗴𝗵 𝗢𝗽𝗲𝗻𝗥𝗼𝘂𝘁𝗲𝗿: Then I made Claude Fable 5.2 the writer, through OpenRouter. It took 𝟴𝟴 𝗺𝗶𝗻𝘂𝘁𝗲𝘀. It started by testing the small model and found it right about half the time. Then it spent 95 Python runs looking inside. What it found: the facts needed for the right answers were already in the model. The last layer, the scorer (it turns what the model read into a score for each option), just wasn't using them. The original model called all 100 test invoices "Routine", overdue or not. So it 𝗱𝗶𝗱𝗻'𝘁 𝘁𝗲𝗮𝗰𝗵 𝘁𝗵𝗲 𝗺𝗼𝗱𝗲𝗹 𝗮𝗻𝘆𝘁𝗵𝗶𝗻𝗴 𝗻𝗲𝘄. It rewired 144 of the scorer's 1,024 units, 𝟭𝟰𝟳,𝟳𝟰𝟰 𝘄𝗲𝗶𝗴𝗵𝘁𝘀, 𝗮𝗯𝗼𝘂𝘁 𝟭 𝗶𝗻 𝟰,𝟬𝟬𝟬, using one direct calculation on 900 practice cases. It checked the result on 300 cases it hadn't used, improved it twice, kept the best version and saved it as a small patch. The original model is untouched. On 400 test cases it never saw (2,000 answers), accuracy went from 𝟱𝟯.𝟯𝟱% 𝘁𝗼 𝟳𝟬.𝟵𝟱% (+17.6, ±1.2). 257 cases got better and 𝟱𝟭 𝗴𝗼𝘁 𝘄𝗼𝗿𝘀𝗲. The dspy-wsp team's own run with gpt-6-astra got 68.3% on the same test. The picture I keep coming back to is a student who read the whole book, then ticks the same box on every question. More lessons won't help. You fix the answer sheet. That also tells you the ceiling. Fable estimated this kind of last-layer fix tops out around 74 to 75%, because two cues never reach that layer at all. Cost: The whole thing cost $𝟭𝟳: about $14 for the main run and $3 for test runs. Prompt caching did a lot of the work. 95% of the input came from cache, which costs 1/40 of the normal price, so without it I'd guess around $50 for the main run. One gotcha: DSPy's default cache setting sent nothing through OpenRouter. It only kicked in once each call marked its newest message. I would not call it a clean win: I wouldn't call it a clean win over astra, though. Each writer ran once and astra's number is the team's published run, so Fable is 𝘀𝗹𝗶𝗴𝗵𝘁𝗹𝘆 𝗮𝗵𝗲𝗮𝗱 𝗮𝘁 𝗯𝗲𝘀𝘁. Astra was cheaper too, at $7.63. And 70.95% counts the option the model rates most likely. The answer the program actually returns only reaches 𝟳𝟬.𝟳% after DSPy's ReAnchor refits its cut points. Without that it's 𝟲𝟬.𝟮%. What stuck with me is the gap between writers. A local 27B model got nothing out of the same job that Fable turned into +17.6. The README points the same way: on this model gpt-6.1-sol gained 5.8 points and gpt-6-astra 16.1 (on returned answers). I think the writer is most of the game. Claude Code did the setup and runs, and built the live demo of both models side by side you see in the video. I'll put the code, demo and notes in a repo. 𝘚𝘢𝘮𝘦 𝘵𝘰𝘰𝘭, 𝘴𝘢𝘮𝘦 𝘮𝘰𝘥𝘦𝘭, 𝘴𝘢𝘮𝘦 𝘥𝘢𝘵𝘢. 𝘖𝘯𝘭𝘺 𝘵𝘩𝘦 𝘸𝘳𝘪𝘵𝘦𝘳 𝘤𝘩𝘢𝘯𝘨𝘦𝘥, 𝘢𝘯𝘥 𝘪𝘵 𝘸𝘦𝘯𝘵 𝘧𝘳𝘰𝘮 +0.0 𝘵𝘰 +17.6. Links in reply 👇

1:12
Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·5m

OpenAI asked 101 researchers what they’d give up to keep frontier coding agents for three months. The median answer? 40% of team headcount. Hypothetical, of course. But when people start valuing AI in terms of colleagues rather than tokens, something fundamental is shifting.

Post attachment
Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·53m

I don’t need another AI news feed. I want to connect with people who build, break, test and question things. If that’s you, let’s #connect.

0:09
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·5h

6 self-hosted alternatives to Zapier, IFTTT and Airflow Zapier's pricing goes up with every automation you add. At first it's a few dollars to send a Slack message when a form comes in. A year later you're running 40 automations and paying more than for your actual software. GitHub list of free software you can run yourself, has a whole section of automation tools you can host for free: ⚡ Activepieces: no-code automation like Zapier. Connect apps, set a trigger, done 🤖 Huginn: build agents that watch the web and act for you, years before "AI agents" was a buzzword 👀 changedetection.io: get alerted when any web page changes, like a price, a job listing or a "back in stock" notice 🏷️ Discount Bandit: tracks prices and stock across Amazon, eBay, Walmart and more 🕐 Cronicle: schedule and run tasks from a web dashboard 🪁 Apache Airflow and Kestra: heavy-duty workflow tools for data teams For non-technical people: These are little robots that do repetitive computer chores for you while you sleep, without a monthly bill. For technical people: Activepieces is the closest drop-in for Zapier. changedetection.io is the hidden gem: point it at any page and it emails you the moment something changes. The honest catch: when an automation breaks at 3am, there's no support team. It's you. But if you're already paying for automation by the task, you'll want to see this. Links in reply 👇

Post attachment
Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·5h

🏠 Home Assistant: github.com/home-assistant/co… 🔌 Tasmota: github.com/arendst/Tasmota 🧩 Node-RED: github.com/node-red/node-red 🚗 evcc: github.com/evcc-io/evcc ☀️ SOLECTRUS: github.com/solectrus/solectr…

Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·5h

Take your smart home back from the cloud Your smart lights stop working when the internet goes down. Think about that. The bulb is in your house. The switch is in your house. But the decision to turn it on happens on a server in another country. And when the company shuts down that server, your "smart" home becomes a dumb one overnight. awesome-selfhosted, the GitHub list of free software you can run yourself, has a fix: 🏠 Home Assistant: one app to control lights, heating, locks and sensors from almost any brand, running locally 🔌 Tasmota: free firmware that cuts cheap smart plugs off the cloud and gives you full local control 🧩 Node-RED: drag-and-drop flows to wire devices and services together 🚗 evcc: charges your electric car when your solar panels are producing the most ☀️ SOLECTRUS: a solar dashboard showing what you produce, use and save For non-technical people: It's a smart home that keeps working when the internet doesn't, and doesn't tell anyone when you got home. For technical people: Home Assistant is the centre of the self-hosted smart home world. Tasmota on ESP-based plugs, plus MQTT, is the classic way to get devices off the cloud. The honest catch: setup takes an afternoon, and some brands make local control deliberately hard. But once it's running, your house answers to you, not to a server. Links in Repo 👇👇

0:09
Gul Saeed Khattak avatar
Gul Saeed Khattak@Ldataengineer·5h

⚡ Activepieces: github.com/activepieces/acti… 🤖 Huginn: github.com/huginn/huginn 👀 changedetection.io: github.com/dgtlmoon/changede… 🏷️ Discount Bandit: github.com/Cybrarist/Discoun… 🕐 Cronicle: github.com/jhuckaby/Cronicle 🪁 Kestra: github.com/kestra-io/kestra

Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·7h

A Dead Man’s Switch You Run Yourself Think about what lives only in your head. The password to the family photos. Where the insurance papers are. The thing you never quite said to your sister. If you were gone tomorrow, 𝘄𝗵𝗼 𝘄𝗼𝘂𝗹𝗱 𝗸𝗻𝗼𝘄 𝗮𝗻𝘆 𝗼𝗳 𝗶𝘁? LastSignal is a small open-source app built for that question. The README calls it a self-hosted, email-first "𝘥𝘦𝘢𝘥 𝘮𝘢𝘯'𝘴 𝘴𝘸𝘪𝘵𝘤𝘩." You write messages for the people you care about. Every 𝟯𝟬 𝗱𝗮𝘆𝘀 it emails you a check-in, and you click to say you're fine. Miss one and it sends 𝟯 𝗿𝗲𝗺𝗶𝗻𝗱𝗲𝗿𝘀, 𝗮 𝘄𝗲𝗲𝗸 𝗮𝗽𝗮𝗿𝘁. With the last one, it can ask a trusted contact whether you're really unreachable. If they say you're OK, delivery pauses. If nobody answers, your messages go out. Every timing is yours to change. You can even make one person wait extra days before they can open theirs. 𝗣𝗿𝗶𝘃𝗮𝗰𝘆 𝗶𝘀 𝘄𝗵𝗲𝗿𝗲 𝗶𝘁 𝗴𝗲𝘁𝘀 𝘀𝗲𝗿𝗶𝗼𝘂𝘀. Messages are encrypted before they leave your browser, so the server only ever stores scrambled text. Per the README, even the person running it can't read them. And it's yours. 𝗡𝗼 𝗵𝗼𝘀𝘁𝗲𝗱 𝘃𝗲𝗿𝘀𝗶𝗼𝗻, 𝗻𝗼 𝘀𝘂𝗯𝘀𝗰𝗿𝗶𝗽𝘁𝗶𝗼𝗻. The authors say plainly that anyone selling LastSignal as a service isn't them. You run it with Docker on your own server, even a Raspberry Pi 4 or 5. It's MIT licensed, built with Rails 8 and SQLite. Google has had something similar for years (Inactive Account Manager), but that hands over your Google data, held by Google. LastSignal sends words you wrote, from a machine you control. Two honest caveats: The README warns that if someone steals the database, they can try to guess your recipients' passphrases offline with no limit, so 𝘄𝗲𝗮𝗸 𝗽𝗮𝘀𝘀𝗽𝗵𝗿𝗮𝘀𝗲𝘀 𝗮𝗿𝗲 𝘁𝗵𝗲 𝗿𝗲𝗮𝗹 𝗿𝗶𝘀𝗸. And it only works if your server and email provider are still running when the day comes. 𝘔𝘰𝘴𝘵 𝘰𝘧 𝘶𝘴 𝘱𝘭𝘢𝘯 𝘧𝘰𝘳 𝘰𝘶𝘳 𝘮𝘰𝘯𝘦𝘺. 𝘝𝘦𝘳𝘺 𝘧𝘦𝘸 𝘱𝘭𝘢𝘯 𝘧𝘰𝘳 𝘵𝘩𝘦 𝘭𝘢𝘴𝘵 𝘵𝘩𝘪𝘯𝘨 𝘸𝘦 𝘸𝘢𝘯𝘵 𝘵𝘰 𝘴𝘢𝘺. Links to repo: github.com/giovantenne/lasts…

Post attachment
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·Nov 16

Most people keep their files, photos and media on someone else’s servers. You pay every month, and your data lives on a machine you don’t control. There is a better way: self-hosting. You run the apps yourself on a small box at home, like a Raspberry Pi or an old mini PC. But there is a catch. Self-hosting usually means the Linux command line, Docker (a tool that runs each app in its own isolated box), config files and ports. Most people give up there. An open-source project from IceWhale Technologies solves this with CasaOS. The idea is simple: a home server with an app-store feel. Take a machine running Debian, Ubuntu Server or Raspberry Pi OS. Run one install command. Open the dashboard in your browser. Click to install the apps you want. You pick the apps. The system handles the Docker part by itself. How it works: → It is not a full operating system. It sits on top of your existing Linux as a layer. → Every app is a Docker container, so apps stay separate and are easy to remove. → A built-in app store gives one-click install for selected apps like Nextcloud, Home Assistant, AdGuard and Jellyfin. → The dashboard also handles files and drives, and widgets show resource usage and app status. It started as the pre-installed system for ZimaBoard, a crowdfunded single-board server. Now it is community-driven. The project in numbers: • ~37.6k GitHub stars • 100,000+ Docker apps you can install, they say • 3 hardware types: x86-64, arm64, armv7 • Apache-2.0 license What I find interesting as someone working with self-hosted tools: Docker was already there. The missing piece was a simple screen on top of it that someone who is not an engineer can use. Links in the reply 👇

0:17
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·Nov 17

I work from home, so X is the closest thing I have to an office. My feed still has too few people who ship things. I want to change that. If you're building with AI, say hi: It's too quiet in here. • Data Engineers • Inovators • AI Engineers • Vibe coders • Founders Tell me what you're building 👋

Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·12h

JUST IN -MASSIVE CYBERATTACK: 178 organisations, including the BBC, CNN, HSBC and Zoom, were hit by a supply-chain attack via Optimizely. The malicious code ran on their websites, in visitors’ browsers. One vendor flaw, 178 victims. Third-party scripts are now a front-line risk. #InfoSec newsweek.com/cyber-attack-we…

Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·17h

A design skill for Claude Code, Codex, Cursor and OpenCode that Removes AI Slop in Web Design. You’ve seen this website a thousand times. A small label in capitals above every heading. A purple gradient. Three feature cards with icons. “Trusted by teams everywhere.” An email sign-up box at the bottom. You know it was made by AI before you finish scrolling. That’s the problem @nutlope set out to fix with Hallmark. It’s an open-source design skill for Claude Code, Codex, Cursor and OpenCode, and its tagline is that it “refuses to look AI-generated.” It’s already at 32k stars on GitHub. Here’s how it works. For non-technical people: Think of it as a strict art director sitting next to your AI. Before anything ships, it checks the page against a list of things that make a site look AI-made, and sends the work back if it fails. For technical people: • Quality gates in three tiers. “Floor” is never broken: contrast, keyboard focus, reduced motion, mobile layout, and no invented facts. “Reflex” is defaults you can override with a reason. “Finish” is craft details. • 48 “materials” (themes), each a single file under 8 KB, or a custom mode built from your prompt • It builds and reviews the hero section first, renders the page at eight screen widths with a lint script, then has a fresh subagent review it • 755 openly licensed photos, credited on the page and deliberately not from Unsplash or Pexels • /hallmark audit and /hallmark redesign for pages you already have • Output is plain, self-contained HTML and CSS My favourite detail: one of the things it checks for is a contact form that says “thanks!” without actually sending anything. If you’ve shipped AI-built sites, you know exactly why that’s on the list. The bigger lesson isn’t about design. AI defaults to the average of everything it has seen. That’s why so many AI-built sites look the same. A skill like Hallmark doesn’t make the model smarter. It gives it taste, written down as rules. Same model. Better instructions. Very different result. Install: npx skills add nutlope/hallmark -g Free and MIT licensed. Repo: github.com/Nutlope/hallmark

0:17
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·11h

𝗥𝘂𝘀𝘁 𝗜𝘀 𝗙𝗮𝘀𝘁𝗲𝗿 𝗮𝗻𝗱 𝗦𝗮𝗳𝗲𝗿. 𝗦𝗼 𝗪𝗵𝘆 𝗔𝗿𝗲 𝗧𝗲𝗮𝗺𝘀 𝗦𝗰𝗮𝗿𝗲𝗱 𝘁𝗼 𝗦𝘄𝗶𝘁𝗰𝗵? rust-anything 𝗠𝗮𝗸𝗲𝘀 𝗜𝘁 𝗮 𝗣𝗶𝗲𝗰𝗲 𝗼𝗳 𝗖𝗮𝗸𝗲 Every team has that one slow function. The search box that lags on each keystroke. The script that should take a second and takes a minute. Someone says "just rewrite it in Rust" and 𝘁𝗵𝗲 𝗿𝗼𝗼𝗺 𝗴𝗼𝗲𝘀 𝗾𝘂𝗶𝗲𝘁. The upside is real, though. Rust compiles to machine code with no garbage collector, and it checks memory use before the code ever runs. Google says memory-safety bugs fell 𝗯𝗲𝗹𝗼𝘄 𝟮𝟬% 𝗼𝗳 𝗔𝗻𝗱𝗿𝗼𝗶𝗱'𝘀 𝘃𝘂𝗹𝗻𝗲𝗿𝗮𝗯𝗶𝗹𝗶𝘁𝗶𝗲𝘀 in 2025 as more new code went into Rust. Its medium and large Rust changes also get rolled back about 𝟰𝘅 𝗹𝗲𝘀𝘀 𝗼𝗳𝘁𝗲𝗻 than C++. The fear comes from the old code. It's full of small decisions nobody wrote down. How it treats an emoji, a negative zero, an empty file. 𝗔 𝗿𝗲𝘄𝗿𝗶𝘁𝗲 𝗾𝘂𝗶𝗲𝘁𝗹𝘆 𝗴𝗲𝘁𝘀 𝗼𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲𝗺 𝘄𝗿𝗼𝗻𝗴. rust-anything, a new open-source tool by Erkam Yaman, is built for exactly that worry. It doesn't write the Rust. Your coding agent or you do. It runs your original app on thousands of edge cases, saves every answer, then replays them all against the Rust. 𝗡𝗼𝘁𝗵𝗶𝗻𝗴 𝗰𝗼𝘂𝗻𝘁𝘀 𝗮𝘀 𝗱𝗼𝗻𝗲 𝘂𝗻𝘁𝗶𝗹 𝗲𝘃𝗲𝗿𝘆 𝗰𝗮𝘀𝗲 𝗺𝗮𝘁𝗰𝗵𝗲𝘀. Your callers keep the same API, so you can move one hot loop or, step by step, the whole app. The README has a good example. A first port passed simple tests but failed 2 of 200 recorded cases, because JavaScript counts an emoji as two positions and Rust counted one. That's the kind of bug that usually reaches production. The speedups in the repo are big: a search over 50,000 keys went from 𝟭𝟬 𝗺𝘀 𝘁𝗼 𝗮𝗯𝗼𝘂𝘁 𝟬.𝟱 𝗺𝘀, and a Python 𝚜𝚕𝚞𝚐𝚒𝚏𝚢 got 𝟭𝟳𝘅 𝗳𝗮𝘀𝘁𝗲𝗿. Those are the project's own numbers, on 4 cores. And Rust isn't magic. When the author ported 29 small functions one by one, 𝘁𝗵𝗲𝘆 𝗰𝗮𝗺𝗲 𝗼𝘂𝘁 𝘀𝗹𝗼𝘄𝗲𝗿 𝘁𝗵𝗮𝗻 𝘁𝗵𝗲 𝗧𝘆𝗽𝗲𝗦𝗰𝗿𝗶𝗽𝘁, because crossing into Rust costs more than the work. The gains come from moving whole loops, and the tool benchmarks both before you ship. It covers TypeScript, Python, C, Go, Ruby and Java. It's MIT licensed, runs locally, and came out this week. 𝘛𝘩𝘦 𝘩𝘢𝘳𝘥 𝘱𝘢𝘳𝘵 𝘰𝘧 𝘢 𝘳𝘦𝘴𝘳𝘪𝘵𝘦 𝘸𝘢𝘴 𝘯𝘦𝘷𝘦𝘳 𝘵𝘩𝘦 𝘯𝘦𝘸 𝘭𝘢𝘯𝘨𝘶𝘢𝘨𝘦. 𝘐𝘵 𝘸𝘢𝘴 𝘱𝘳𝘰𝘷𝘪𝘯𝘨 𝘵𝘩𝘦 𝘯𝘦𝘸 𝘤𝘰𝘥𝘦 𝘥𝘰𝘦𝘴 𝘸𝘩𝘢𝘵 𝘵𝘩𝘦 𝘰𝘭𝘥 𝘤𝘰𝘥𝘦 𝘥𝘪𝘥. Links to Repo: github.com/erkamyaman/rust-a….

0:10
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·10h

Looking alternative Open source SaaS apps you can run on your own server, not just in the cloud: 1. Slack alternative: Campfire (by 37signals) One Docker image, runs on a single machine, MIT licensed 2. DocuSign alternative: SignuDoc Runs anywhere Node.js and Postgres run, or 1-click to Vercel. MIT licensed 3. Google Analytics alternative: Umami Docker image, privacy-first, no cookies. MIT licensed, 40k+ stars Prefer one-click cloud chat? Ember deploys to your own Cloudflare account. Links in reply 👇

0:11
Gul Saeed Khattak avatar
⟳ Gul Saeed Khattak retweeted
Gul Saeed Khattak@Ldataengineer·16h

Every few months, another password manager company sends the email nobody wants to get: "We recently detected unusual activity..." And you realise every password you own lives on a server you've never seen. Some people chose a different path. They run their password manager on their own server. GitHub lists free software you can host yourself: 🔐 Vaultwarden: github.com/dani-garcia/vault… A lightweight server written in Rust that works with the official Bitwarden apps and browser extensions 🛡️ Bitwarden: github.com/bitwarden/server The official self-hosted server, with web app, browser extension and mobile apps 📧 AliasVault: github.com/aliasvault/aliasv… An end-to-end encrypted password manager that also generates email aliases, so every site gets a different address 👥 Passbolt: github.com/passbolt/passbolt… Built for teams sharing passwords For non-technical people: Instead of keeping your keys in a bank's safe, you keep them in a safe in your own house. You choose who has the key. For technical people: Vaultwarden is the favourite for home servers because it runs happily on a Raspberry Pi. It's an unofficial reimplementation of the Bitwarden server, so read up on what that means before you trust it with everything. The honest catch, and it's a big one: if your server dies and you have no backup, your passwords die with it. Self-hosting passwords means taking backups seriously. Get that right, and nobody can sell, leak or lose your vault except you.

Post attachment