# rbox

> rbox is passive sync for developer workstations. It keeps code, Git state, and uncommitted work synchronized across a developer's machines while skipping dependencies and build output.

rbox is built for active working directories rather than general-purpose file storage. It moves branches, the Git index, stashes, uncommitted changes, and ordinary project files together. If another machine has conflicting local work, rbox waits instead of overwriting it. Files are encrypted on the user's device before upload, and rbox cannot read their contents.

## When to use rbox

Use rbox when a person or coding agent needs the same active development workspace on multiple macOS or Linux machines, including uncommitted files and Git checkout state. Use the CLI when an ephemeral coding agent, CI runner, devcontainer, or long-lived workstation needs to pull a current workspace without copying archives or exposing plaintext code to the service.

Do not use rbox as a general document-sharing service, a replacement for a Git remote, or a dependency/build-output cache. For headless setup, install the CLI, provide an `RBOX_KEY`, and run `rbox setup --workspace=<name-or-id> --dir .`; add `--daemon --pull-only` for a shared read-only agent fleet. See the Agents & CI section of the documentation for key creation and rotation.

## Product

- [rbox homepage](https://rbox.to/): Product overview, workflow, supported platforms, pricing, and installation.
- [Documentation](https://rbox.to/docs/): Installation, setup, CLI commands, sync behavior, and `.rboxignore` reference.
- [Developer resources](https://rbox.to/developers/): Agent setup, the supported automation surface, public API metadata, and authentication guidance.
- [OpenAPI specification](https://rbox.to/openapi.json): Machine-readable description of rbox's stable public release and health endpoints.
- [Contact](https://rbox.to/contact/): Support, security, privacy, billing, and business inquiries.
- [About](https://rbox.to/about/): The story behind rbox, who builds and operates it, current production use, and infrastructure location.
- [Changelog](https://rbox.to/changelog/): Release-by-release changes to the rbox CLI.
- [Security](https://rbox.to/security/): End-to-end encryption, key handling, server visibility, and security-model limitations.

## Guides

- [Git backup](https://rbox.to/guides/git-backup/): Why remote Git repositories do not protect uncommitted work, the index, or stashes, and how rbox handles them.
- [Using Git with Dropbox](https://rbox.to/guides/git-dropbox/): Risks of syncing live Git repositories with general-purpose file sync and safer alternatives.
- [Ignoring files and folders in Dropbox](https://rbox.to/guides/dropbox-ignore-folder/): Dropbox ignore approaches for dependencies and build output, compared with rbox defaults.

## Comparisons

- [rbox vs Dropbox](https://rbox.to/vs/dropbox/): Developer-workspace sync compared with general-purpose cloud storage.
- [rbox vs Syncthing](https://rbox.to/vs/syncthing/): Hosted, Git-aware sync compared with self-hosted peer-to-peer sync.
- [rbox vs Resilio Sync](https://rbox.to/vs/resilio-sync/): Developer-focused encrypted sync compared with general-purpose peer-to-peer sync.
- [rbox vs FreeFileSync](https://rbox.to/vs/freefilesync/): Continuous developer-workspace sync compared with manual folder synchronization.

## Optional

- [Privacy policy](https://rbox.to/privacy/): Data collection, encryption, service providers, and privacy rights.
- [Terms of service](https://rbox.to/terms/): Account, billing, acceptable-use, and service terms.