# Deploy within your operating boundary.

Evaluate desktop, Linux, Docker and mobile deployment roles for Rangoon. Define identity, data routes, adapter support and recovery before rollout.

Canonical: https://rangoon.ai/software/self-hosted-deployment/

Launch specification. Application source, downloads and versioned compatibility evidence publish with releases.

Audience: Infrastructure & platform teams

Choose where capabilities run and which services they can reach. Separate desktop authoring, team services and mobile participation, then review credentials, data routes and recovery for each environment.

Evaluation outcome: A deployment plan tied to package versions, operating roles, credential scope, approved provider routes and a tested recovery procedure.

## Operating workflow

### Choose the runtime role

Map authoring and review to desktop workspaces; map persistent operations to team services. Docker and Compose provide repeatable service packaging. Mobile roles remain separately bounded.

[Review the specification](https://rangoon.ai/downloads/)

### Review the connection boundary

Check the adapter version, supported operations, identity and credential scope. Record where data is processed; self-hosting a control plane does not make every provider local.

[Review the specification](https://rangoon.ai/compatibility/)

### Prepare rollout and recovery

Keep configuration, secrets, state and release artifacts distinct. Define health checks, rollback conditions, receipt retention and reconciliation ownership before deployment.

[Review the specification](https://rangoon.ai/product/deployments/)

## Evaluation checklist

### Desktop or persistent service?

Use the operating role to select a deployment form. A desktop authoring workflow and a shared service have different uptime, identity and state requirements. Release documentation identifies supported packages and lifecycle requirements.

### What remains inside the boundary?

List model endpoints, connector destinations, secret stores and operational records. Document approved egress and processing locations. Local infrastructure can still send data to a remote provider if the workflow permits it.

### What changes on mobile?

iOS, iPadOS and Android participate through companion workflows, policy SDKs and explicitly bounded edge work. Review platform lifecycle, background execution and permission limits separately from desktop and server capabilities.

## Continue the evaluation

- [Review systems and release availability](https://rangoon.ai/downloads/)
- [Read deployment architecture](https://rangoon.ai/product/deployments/)
- [Downloads and systems](https://rangoon.ai/downloads/)
- [Compatibility](https://rangoon.ai/compatibility/)
- [Connector contracts](https://rangoon.ai/developers/connectors/)
- [Open-source model](https://rangoon.ai/open-source/)
- [Agent development](https://rangoon.ai/software/agent-development/)
- [Execution governance](https://rangoon.ai/software/execution-governance/)


## More information

- [Documentation index](https://rangoon.ai/llms.txt)
- [AI access and policies](https://rangoon.ai/ai/)
- [Source repository](https://github.com/hypler-dev/rangoon)