Tools
Software you install and run.
The core Logos software, Basecamp and the node, has its own pages under Logos. See Basecamp and Run a node.
Tools
Tools built on the Logos stack, grouped by the part of the stack they use most. Almost all are community projects. Each page quotes what the project's own README says about whether it is official.
Messaging
- Booth: broadcast a live stream from Basecamp over Logos Messaging, with no server or account. Prototype.
- Receiver: find and listen to Booth stations over Logos Messaging, played over Tor. Prototype.
- Forumer: a private, serverless forum for Basecamp, with pictures in Logos Storage. Prototype.
- KYM: a household envelope budget synced between the household's own devices. Almost done.
- Perun: a run tracker that sends runs from an Android phone to a Basecamp module. Full Release.
- Shrooms: a mesh VPN that finds peers over Logos Messaging and carries traffic over WireGuard. Prototype.
- WhisperBox: forms and surveys with each answer encrypted to the form's key. Prototype.
Storage
- Reelcut: cut a long video into short captioned reels and keep them in Logos Storage. Prototype.
- Backpack: an Android app store whose repositories live in Logos Storage. Prototype.
- Whistleblower: publish documents to Logos Storage and anchor them on chain so they survive takedowns. Prototype.
Logos Execution Zone
- Medusa: a self-custody privacy wallet for the Logos Execution Zone, run as a Basecamp module. Prototype.
- Evice Wallet SDK: a wallet engine, dApp SDK and command-line wallet. Prototype.
- LNS: a private-by-default name service, with an app to post, message and get paid under a name. Prototype.
- LEZ Atomic Swaps: swap native Bitcoin and LEZ with no custodian or bridge. Prototype.
- Private Token Balance Attestation: prove an account holds at least a set amount without showing the balance. Prototype.
- Private M-of-N Multisig: a multisig where members approve without showing who voted. Prototype.
- DistributionX: pay out to an allowlist without publishing the recipients. Prototype.
- Forum-protocol: an anonymous forum with joint moderation and on-chain revocation. Prototype.
- Logos Autonomous Agent: an AI agent with its own shielded wallet, storage, messaging and an owner spending limit. Prototype.
Logos Blockchain
- Logos-blockchain-ui (xAlisher): run, watch and fund a testnet node from Basecamp in one click. Prototype.
- Node Remote: watch and control a node from an Android phone over Tor. Prototype.
- SoliCamp: write, deploy and test Solidity in Basecamp, then publish to the chain. Prototype.
Basecamp only
- Keycard (xAlisher): give other Basecamp modules keys from a Keycard smartcard. Prototype.
- Docs (xAlisher): search the Logos docs and blog on the device. Prototype.
- Can it run DOOM?: the DOOM engine as a Basecamp module. Prototype.
Each tool page has a stage: Design, Planning, Prototype, Almost done or Full Release. The page says which line from the project's own sources set the stage.
Tools Logos did not build
Tools from outside Logos that Circles use, for chat and calls, working together, fundraising, browsing, passwords and more, are listed on Resources for activists, which keeps its own listing rule. The criteria below apply to the tools on this page.
Criteria for listing a tool
The format of these criteria comes from Privacy Guides and its VPN criteria, which split each test into a minimum and a best case. A tool must meet every minimum to be listed here. The best case is what we hope to see.
Open source licence
Minimum to qualify:
- Released under a licence approved by the Open Source Initiative or the Free Software Foundation.
- The licence is named in the repository.
Best case:
- A copyleft or permissive licence that matches the rest of the Logos stack.
- Every dependency it ships is also open source.
Published code
Minimum to qualify:
- All source code is public in a repository anyone can read.
- A reader can build it from that source.
Best case:
- Versioned releases with notes on what changed.
- Signed releases, and builds that can be reproduced.
- Dependencies pinned to exact versions.
Documentation
Minimum to qualify:
- Install and use instructions a newcomer can follow.
- Build instructions.
Best case:
- A step-by-step guide from zero to working.
- A plain statement of known limits and the threat model: what it protects against and what it does not.
Privacy
Minimum to qualify:
- No analytics, telemetry or tracking.
- No account or personal information needed to use it.
Best case:
- Works over Tor or another anonymity network.
- Keeps no logs or records of its users.
- Keys and secrets stay on the user's own device.
Who maintains it
Minimum to qualify:
- A named maintainer or team, or a public handle with a history of commits.
- Some way to report bugs, such as an issue tracker.
Best case:
- More than one active maintainer.
- A security policy, a way to disclose bugs in private and an independent audit.
- Says clearly whether it is an official Logos product or a community project.