> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nuphos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Connect your cloud accounts, repositories, observability tools, and messaging so the agent can work with them.

Connectors are how you give Nuphos access to your world. Each one establishes a
**trust relationship** — never a stored long-lived key — that the agent uses to
inspect and operate that system on your behalf.

Every connector page in this section covers the same things: how to connect it,
what lights up in the Nuphos app once it's connected, what the agent can do for
you with it, and how permissions and authorization work along the way.

<Info>
  Connecting (binding) a connector requires the **Administrator** role on your
  team. Administrators can also restrict any connector to specific members with
  a [member allow-list](/security/access-control).
</Info>

## How permissions work — every connector

Two boundaries govern what happens through a connector:

* **The hard boundary** is [access control](/security/access-control): who may
  use the connector at all. Only Administrators can bind or remove one, a
  per-binding member allow-list decides which teammates can use it, and within a
  session the agent only holds the credentials you explicitly selected. These
  checks are enforced server-side on every credential request — they are not
  something the agent can talk its way around.
* **The soft boundary** is what the agent may *do* with the access it has. Reads
  are free-form, but changes are packaged as
  [plans that a human approves](/security/approvals), and at the command level
  [Auto-authorization](/security/auto-mode) decides which commands run on their
  own and which pause for your yes — with standing rules you control.

The outermost limit is always the credential itself: the agent can never exceed
the permissions of the role or token you created in the provider.

## Cloud providers

<CardGroup cols={2}>
  <Card title="AWS" icon="aws" href="/connectors/aws">
    Assume an IAM role via OIDC web-identity federation.
  </Card>

  <Card title="GCP" icon="google" href="/connectors/gcp">
    Impersonate a connector service account.
  </Card>

  <Card title="Cloudflare" icon="cloudflare" href="/connectors/cloudflare">
    Manage zones, DNS, and more with an API token.
  </Card>

  <Card title="Linode (Akamai)" icon="server" href="/connectors/linode">
    Manage Linodes and LKE clusters.
  </Card>

  <Card title="Hetzner" icon="server" href="/connectors/hetzner">
    Manage Hetzner Cloud servers and networks.
  </Card>

  <Card title="Tailscale" icon="network-wired" href="/connectors/tailscale">
    Access tailnet devices and policies.
  </Card>

  <Card title="Zeabur" icon="rocket" href="/connectors/zeabur">
    Connect Zeabur projects and servers.
  </Card>
</CardGroup>

## Source control

<CardGroup cols={2}>
  <Card title="GitHub" icon="github" href="/connectors/github">
    Browse pull requests, workflows, and repositories.
  </Card>

  <Card title="GitLab" icon="gitlab" href="/connectors/gitlab">
    Connect gitlab.com or a self-hosted instance.
  </Card>
</CardGroup>

## Observability

<CardGroup cols={2}>
  <Card title="Grafana" icon="chart-line" href="/connectors/grafana">
    Dashboards, alerts, and trace exploration.
  </Card>

  <Card title="Better Stack" icon="heart-pulse" href="/connectors/betterstack">
    Monitors, incidents, and telemetry.
  </Card>
</CardGroup>

## Project management

<CardGroup cols={2}>
  <Card title="Linear" icon="diagram-project" href="/connectors/linear">
    Open, track, and close Linear issues.
  </Card>

  <Card title="Jira" icon="diagram-project" href="/connectors/jira">
    Create, comment on, and transition Jira Cloud issues.
  </Card>
</CardGroup>

## Compliance

<CardGroup cols={2}>
  <Card title="Vanta" icon="shield-check" href="/connectors/vanta">
    Read failing compliance tests and remediate.
  </Card>

  <Card title="Secureframe" icon="shield-check" href="/connectors/secureframe">
    Read failing compliance tests and remediate.
  </Card>
</CardGroup>

## Messaging

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="/connectors/slack">
    Let the agent operate from Slack channels.
  </Card>

  <Card title="iMessage" icon="message" href="/connectors/imessage">
    Talk to the agent over iMessage.
  </Card>
</CardGroup>