Connectors

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.

​

How permissions work — every connector

Two boundaries govern what happens through a connector:

• The hard boundary is 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, and at the command level Auto-authorization 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

​

Source control

​

Observability

​

Project management

​

Compliance

​

Messaging