nowfound

Alternatives

Products that do what DotBGE does

Local-first file encryption for iOS, CLI, and agents

  1. 1
    hat.sh212

    Free, fast, secure and serverless file encryption

    2019

  2. 2

    Open-Source encryption fully integrated into the files app

    2021

  3. 3
    Port22239

    Claude Code, Codex & more on your phone

    Aug 2026 · tryport22.com

  4. 4
    CodeMote144

    Claude Code, Codex, any CLI agent. Driven from your iPhone

    Jul 2026 · codemote.caste.work

  5. 5

    Browse, search & track costs across Claude Code sessions

    Apr 2026

  6. 6

    End-to-end encrypted file sync & sharing for your team

    2016

  7. 7

    Private & Encrypted Files, Notes, Passwords, 2FAs app

    2020

  8. 8
    Cryptee155

    An encrypted home for your private photos, docs & notes.

    2018

  9. 9
    AroCrypt127

    Encrypt files, then make them vanish inside images

    2025

  10. 10

    Simple & secure password manager for teams & individuals

    2018

  11. 11AL
  12. 12

    Create portable encrypted documents on your Mac

    2019

  13. 13
    Finch79

    Encrypted file sharing and messaging for geeks

    2017

  14. 14ET

    So, you want to avoid mass surveillance and don't trust big tech companies either? But you're tied to your existing network of contacts like everyone else? Well now you can send encrypted messages to your contacts over the Twitter direct messaging channel. It's a serverless SPA called Seecret, a Twitter client hosted at https://www.seecret.io Seecret is open source and freely distributable. You can host it anywhere even from your own localhost server. The app is just plain html and javascript, with no server-side processing at all, no tracking, no logging. Steps: 1-Grant Seecret.io…

    2016

  15. 15SH

    I have written a passwords/secrets manager for my personal needs. Maybe it solves some of your problems too. It is written in Go and is a self-contained executable for a small web-app: https://github.com/jarmo/secrets-web There is also a CLI version if that is your taste: https://github.com/jarmo/secrets-cli To read about more technical details, look into the core repository at https://github.com/jarmo/secrets Any questions/comments/suggestions are welcome in here or via GitHub pull requests.

    2020

  16. 16CI
  17. 17IP

    Hey HN! I made a service to share passwords easy and secure but never promoted it. It's called instapass.io I noticed that people besides my friends and clients actually started to use, so maybe it will be helpful for you too! You share one-time self-destruct message using one time links and I won't even be able to see what you wrote. How does it work? When you generate a message the client-side makes a random password and use that to encrypt the message. The password is appended as an anchor tag which all modern browsers never send to the server. This way, I don't even know what you shared.…

    2019

  18. 18NQ

    Hey HN, We're building ncrypt, an open-source encrypted file manager that allows you to store, manage, and privately query your files using fully homomorphic encryption (FHE). This project originally started as a simple SFTP-like CLI for my personal S3 buckets which I used to send and retrieve encrypted files and have more granular control over key rotation. As the number of files that I was storing grew, file discovery started to become a problem, and I found myself frequently having to download and decrypt files to inspect their contents. Rather than leaving them unencrypted in S3 and…

    2025 · github.com

  19. 19HS

    Hi HN! I built hidetext.sh — a way to share text, code, and files through links the server can't read. How it works: your browser generates a random key and encrypts everything locally (NaCl secretbox, XSalsa20-Poly1305). Only ciphertext is uploaded. The key goes into the URL fragment — the part after # — which browsers never send to servers. The link carries the key, my server stores the locked box, and the two only meet in a browser. A design detail I'm fairly happy with: burn-after-read doesn't destroy the paste on the first HTTP request. The naive version means a Slack or iMessage link…

    Jul 2026 · hidetext.sh

  20. 20GE

    Hi! I've been frustrated with the secret sharing situation in serverside javascript land for a while; the common thing is to just toss .env files around on Slack to get someone's app working, or involves some kind of convoluted setup to get a blob from a storage and turn it into environment variables via commands I have to copy paste every time. But everyone uses secret storage providers, e.g. shared password vaults, cloud secrets, etc., so why not leverage those as URIs in a JSON file that can be checked in to source control? I want something simple that would just generate the darn .env…

    2025 · github.com

  21. 21A1

    I wrote a minimal iOS app called PocketServer (~1MB in download size) that creates persistent local HTTP/WebDAV servers which can actually run in the background. Functionalities: - Serve a folder via WebDAV — browse/add/delete files from others devices on the same network. - Host a static website or directory listing, accessible locally. - Share files cross-platform on the same network, no app needed on the receiving side. https://apps.apple.com/us/app/pocketserver-local-server/id67...

    2025

  22. 22AF
  23. 23CR

    Hi HN — I built Catnip, an open-source iOS app that lets you run Claude Code against a real development environment from your phone. Under the hood it spins up a GitHub Codespace, installs Claude Code, and connects the iOS client to it securely. You can use a full terminal when needed, or a lightweight native UI for monitoring and interaction. I built this because Claude Code is most useful when it has access to a persistent environment with plugins, tools, and real repos — and I wanted that flexibility away from my laptop. GitHub gives personal users 120 free Codespaces hours/month,…

    Jan 2026 · github.com

  24. 24BM

    Wrapper around Apple's macOS sandbox-exec tool, which usually sandboxes native apps. It is "allow-first" i.e. it will not overprotect everything, just crucial information and therefore allows most tools to run without issues. Limiting is done using a .gitignore like file schema. Further TOML config options available. I built it because Docker sandboxing requires config and planning. Build in sandboxing of AI tools instead is limited to the very tools themselves, instead I wanted to have a simple cage around Claude running inside VSCode. Also needed to protect files inside a folder like…

    Apr 2026 · github.com

Ranked by how close each launch is in meaning, then by votes. Refine with a description →