Integrations

Connect the stack you already run.

VPods does not replace GitHub, AWS, Azure, or the board. It attaches licensed agents to them. Permissions, IAM, and Azure RBAC live on Security & Trust.

All plans

GitHub

The delivery repository. Light OAuth on Trial so you take the code. Same repo on Startup and Scale.

None · optional · required

Amazon Web Services / Microsoft Azure

Trial: VPods Amplify, no customer cloud. Startup: none by default; optional free-tier AWS or Azure. Scale: your AWS or Azure, required. Apply is always your GitHub Actions or Azure DevOps + VPodsDeploy — never from VPods, for any hire.

Scale · optional on Startup

Jira

Scale uses your Jira. Startup may skip — VPods supplies the board. Trial does not need Jira. Assignment of a mapped hire opens a VPods card (Jira → VPods). Reverse status sync is not this connector. Azure Boards is a separate PAT path, not the same as Azure cloud.

Optional

Team Foundation / Azure Boards

Same job as Jira when the backlog lives in Azure DevOps. Connect a PAT and pick the project. Not Azure cloud-connect.

Optional

Microsoft Teams

Chat becomes work. Needs your Azure, a Teams admin, and an endpoint you publish.

Not required

Supabase

Optional project backend. Not part of Trial, Startup, or Scale onboarding.