Other Connectors
Additional real, currently-supported connectors.
- Netlify, Railway — hosting connectors alongside Vercel.
- Docker, kubectl, Terraform, and major cloud CLIs (AWS, GCP, Azure) — driven through the same allowlisted command mechanism described in Coding → Commands & Terminal, using your own already-authenticated local CLI, not a separate PawOS credential.
Note
This list reflects connectors confirmed real in the current implementation — it is not exhaustive of every provider PawOS has ever experimented with.
How it works
What you see
- Connection setup, connected/disconnected status, permission screens from each service, and approval questions for actions.
- Each connector page lists exactly what that connection can do.
What PawOS does
- PawOS uses your connected account only for the actions that connector supports.
- Sign-in is handled securely, and PawOS asks for extra access only when a feature needs it.
- Connectors that need a higher plan stay locked until your plan includes them.
Permissions
- Connecting an account does not approve future actions — comments, deploys, rollbacks and other changes still ask first.
- If a connection is missing, expired or lacks access, PawOS tells you instead of continuing.
Records
- Connector actions record the service, the result, and any error the service returned.
Good to know
- Service settings and permissions vary, so the same request can behave differently for different accounts.