Everything you own, wired together.
Your computers, KVMs, files, terminals, and local sites in one place.
AllMyStuff is a desktop app for reaching the machines that are yours and the things other people have shared with you. Remote control a screen, open a real terminal, move files, map a folder into the native filesystem, reach a local web service, or work through a KVM when the operating system is not available.
The graph is the home screen. Your fleet stays together, while devices visible through a mesh or share remain separate and expose only the actions that relationship allows.
There is no cloud copy of your stuff and no VPN to configure. Connections use an end-to-end encrypted MyOwnMesh route. Peers connect directly when they can and use an authenticated relay when NAT or a firewall leaves no direct path.
AllMyStuff is free, open source, and runs on macOS, Linux, and Windows.
macOS and Linux
curl -fsSL https://allmystuff.works/install.sh | shWindows
irm https://allmystuff.works/install.ps1 | iexThe installer verifies the release, installs the desktop app and command-line
tools, and brings the pinned MyOwnMesh runtime with it. Prebuilt .dmg, .msi,
.deb, and .AppImage bundles, plus portable archives, are available on the
releases page.
Install AllMyStuff on each computer you want to own as a group. On the local network, choose Make claimable under that computer's This Device card, then select it from another AllMyStuff machine and choose Claim this device. Claiming adds it to your fleet and gives it the fleet relationship used for remote control, terminals, files, drives, sites, updates, and device management.
Once the machines are in your fleet, they do not need to remain on the same LAN. Open AllMyStuff and choose Remote, Files, Drives, or Settings on a device card. Normal mode keeps the graph and its common actions up front. Advanced mode exposes the fuller routing and device surfaces.
For task-by-task walkthroughs, see Using AllMyStuff. The documentation map separates user help from contributor, architecture, and maintainer material.
- Remote control. View and control every shared display, switch between screens, carry text, images, and files through the synchronized clipboard, and drop local files onto the remote desktop. Relative mouse capture supports games and other applications that consume raw movement. Pop any monitor into its own native window, then arrange several remote monitors across your local displays so the whole remote desk stays visible at once.
- Terminals. Open a real shell without configuring SSH, keys, or forwarded ports. Terminal sessions can be attached from more than one machine when you want to follow the same shell together.
- Files and native drives. Browse and transfer files in the app. Map an authorized folder or whole drive into the operating system: a drive letter in Windows, a mounted volume on macOS, or a mount point on Linux. It appears in native applications, not only inside AllMyStuff. A mapping is one-way, but both affected machines show the same source, destination, name, mount, and availability. Reverse mapping is a second explicit action.
- Sites. Publish only the local web services you mean to expose, then open them from another authorized machine even when the service itself listens on loopback.
- KVMs. Use NanoKVM and NanoKVM-Pro devices for video, keyboard, mouse, power control, Wi-Fi, updates, and BIOS access. Authorized ISO, IMG, and removable USB media can be presented to the attached computer for operating system installation or firmware work.
- Sharing. Share a capability with a person without adding their computer to your fleet. Screen, control, files, cameras, microphones, and sites keep their own permissions. A share from you does not silently create a share back to you.
- Rooms. Bring several people and machines into a temporary collaboration surface with chat, screens, control, cameras, microphones, and shared files.
- Always On. Run the node as a system service so a machine stays reachable before login and after reboot. The app also checks and repairs its pinned runtime components during updates.
The detailed native-drive and KVM media behavior is documented in Native drive mapping over the mesh.
These ideas are intentionally separate:
| Concept | What it means |
|---|---|
| Fleet | The devices you own together. Membership is signed and carries an owner, manager, or member role. |
| Mesh | A private reachability space. Being visible on a mesh does not grant access to a device. |
| Share | A one-way permission from one person to another for specific capabilities. |
| Room | A shared session where invited members can use only the capabilities offered to that room. |
That separation matters. Seeing a computer is not permission to control it, sharing your files does not expose theirs, and joining a room does not make its members part of your fleet.
amst comes with AllMyStuff and opens a mesh terminal from the command line:
amst # a shell on this machine
amst Tracy-Laptop # a new shell on another fleet machine
amst Tracy-Laptop --sessions # list its open terminal sessions
amst Tracy-Laptop --attach term-3On Windows, the installer also adds an AMSTerm launcher, shortcuts, and an
AMSTerm here folder menu. If this machine's node is not running, amst
starts the desktop app or the installed headless node as appropriate.
Run a server, build machine, or other computer without the desktop interface:
allmystuff serveKeep it available across logins and reboots:
allmystuff service installThe desktop app and allmystuff serve run the same node engine and speak the
same protocol.
AllMyStuff is written in Rust with a Tauri and Svelte desktop interface. Its node engine owns device inventory, authorization, sessions, media, input, terminals, files, drive mapping, sites, KVM integration, and the local control API. MyOwnMesh provides identity, discovery, encrypted transport, and relay fallback.
The graph model and protocol live in shared Rust crates. The desktop app and headless node use those same crates, while the UI mirrors the state it needs to stay responsive.
See ARCHITECTURE.md for the crate map, data flow, and persistent-state layout.
AllMyStuff is under active development and ships frequent releases. The desktop app and headless node are built and tested on macOS, Linux, and Windows. The mobile client has a runnable Tauri shell and shared core, but device validation and store releases are still in progress. See docs/MOBILE.md for its current state.
Please use GitHub Issues for reproducible bugs and feature requests.
Install just, then:
just setup # install development prerequisites
just dev # run the complete desktop app with hot reload
just check # run the library, node, and front-end checks
just gui-build # build the native desktop bundleSee CONTRIBUTING.md for platform requirements, CLI details, and the repository workflow.