# Connect systems.

> Plan explicit operations for external systems so access, credentials, permissions, policy authorization, and execution never collapse into one assumption.

Canonical: https://rangoon.ai/product/connectors/

Status: In active development. Product screenshots are design previews with illustrative data. No general availability is implied.

## Operations, not ambient access

Connector contracts are intended to describe supported operations, inputs, outputs, side effects, idempotency needs, and policy-relevant metadata.

### System families

Potential adapters span source control, cloud, databases, CRM, ticketing, communications, observability, and security tools.

## Separate every boundary

Installing a connector, enabling it, assigning credentials, granting permission, and authorizing a request are distinct stages.

### Clear review surface

Operators should be able to inspect the intended resource and expected side effect before approval.

## Governed execution path

LNSAT provides the proposed authorization and evidence foundation; connector coverage and contracts are still being developed.

### No implied integration

This page does not claim any connector is currently shipped or configured.


## 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)