Source: https://docs.any.org/understanding/preview.html

# Preview status and license

`any` is a **developer preview**. The data model, the HTTP API and the on-disk format can still change between releases, and a breaking wire change is absorbed by bumping the `/v1/` prefix rather than by a migration. Use a separate account and data root for experiments.

## License

`any`, `anyrt` and the SDKs they build on ([any-sync](https://github.com/anyproto/any-sync), [any-store](https://github.com/anyproto/any-store), [any-sync-sdk](https://github.com/anyproto/any-sync-sdk)) are released under the **MIT** license.

## What runs on your device

The `any` binary is the server and the CLI: `any run` owns the any-store database, the search index and the sync engine; every other `any <cmd>` is an HTTP client of it. The companion `anyrt` runtime executes programs, agent sessions and triggers in a wasm cage against that server. Standalone, they are two processes; a host app can embed both ([Install](https://docs.any.org/quickstart/install.md.txt), [anyrt](https://docs.any.org/quickstart/anyrt.md.txt), [Embedding anyrt](https://docs.any.org/agents/embedding-anyrt.md.txt)).

The server binds to loopback. Its API serves the account loaded into that process and currently has no per-caller authentication — with the plan to ship proper auth and access capabilities support. It is designed to be used by software on the same device. [Security model →](https://docs.any.org/operations/security-model.md.txt)

## Offline behavior

Database operations work against local state. Sync needs a reachable peer. Fetching an uncached file needs a source that holds its bytes. Calling an external model or connector needs that service to be available. Scheduled programs need a device with the `anyrt` runtime running. [Local-first →](https://docs.any.org/understanding/local-first.md.txt)