Bob's CLI
A local-first AI coding CLI that adapts to you
Start new thread

BobVault for BobCLI - CLI based Zero-Knowledge Architecture for code repositories

by
•
VaultBob brings true user sovereignty to your dev workflow. We teamed up with Amazon Web Services (AWS) to build a NEW end-to-end Zero-Knowledge Architecture for code repositories.  Unlike GitHub or other platforms that hold your keys, VaultBob encrypts your source code, configuration files, and deep local AI context directly on your machine before upload. Your encryption key never leaves your device. Secure, versioned snapshots with zero third-party risk. #PowerToTheUser 🌲

Add a comment

Replies

Best
Maker
📌
Today marks a major milestone in our push toward absolute user sovereignty! We are thrilled to launch the VaultBob update for BobCLI. 🚀 Unlike traditional development platforms that hold the keys to your code, we believe your intellectual property should never be accessible to a third party. To make this a reality, as a part of our new partnership we teamed up with Amazon Web Services (AWS) infrastructure to power a new, end-to-end Zero-Knowledge Architecture for your development workflows. With VaultBob, BobCLI users can now run manual or scheduled backups that protect three critical layers: your source code, your configurations, and your deep project AI context. The core of VaultBob's security is simple: encryption is never outsourced to a server. Local Processing: VaultBob bundles and compresses your files directly on your local drive. Local Encryption: The bundle is encrypted on your machine using your own local system resources. Zero-Knowledge Storage: By the time data leaves your network card, it is already secure ciphertext. Your private encryption key never leaves your device. It is never sent to Seedling.io, nor is it stored on AWS. Because the cloud storage layer only holds unreadable ciphertext, it is physically impossible for AWS, Seedling, or an outside attacker to decrypt your code or AI conversation history. VaultBob’s math eliminates third-party risk entirely. At Seedling, we believe our users the builders, developers, and creators are the real superheroes. Today, VaultBob gives you a powerful new tool on your belt to protect your work and own your data. More secure than ever. Let’s build. 🌲 #LetsGrowTogether #PowerToTheUser #AwsActivate #ZeroKnowledge #BobCLI

local first w ur own key makes sense to me. but what if the laptop dies? if the key never leaves the device are the backups just gone or is there a recovery phrase somewhere

Maker

 BobCLI was built within our Bob's Workshop ecosystem. There's a mobile and web version. So although it's Local first, it's not local only. User's can use BobCLI in Hybrid mode enabling actions to continue and be operated from their other devices. (Including emulator support to run project builds, project directory, and terminal access...). For ultimate security and control, If the local key is lost, we do have alternative backup methods in place on our web app for users to set up in order to ensure there's always an option for access.

Hey PH!

We built VaultBob because losing local LLM context every time you switch machines or clear a workspace is a nightmare. Now you have all the keys. Literally.

Complete sovereignty at its finest, that's what Seedling is all about.

Would love your feedback on the workflow, especially if you're managing local AI workflows. What’s your biggest friction point with context persistence right now? Let's keep growing together!🌱