Question 1

What is VPods?

Accepted Answer

VPods is the agentic delivery platform for software teams. VPods is the agentic delivery platform for software teams — AI teammates that join existing teams in days and help them deliver more. Add AI teammates to your delivery team. Virtual Pods. Virtual Agents. Real Teams. More Delivery.

Question 2

Does VPods replace software teams?

Accepted Answer

We’re not building AI to replace software teams. We’re building a new workforce layer that helps developers, architects, QA, DevOps and product teams carry more of the work and ship more of what matters. Your team keeps Approve, merge, and release.

Question 3

How is VPods different from Cursor, Copilot, or Codex?

Accepted Answer

Cursor, Copilot, and Codex typically start when a person opens a prompt or coding session. VPods starts when a structured backlog item is assigned to a specialized AI teammate — with requirements, role boundaries, repositories, and approvals attached. Keep your IDE; VPods is the delivery workforce layer on the backlog, not another autocomplete seat. Full landscape: /compare.

Question 4

How does VPods compare to software factories or autonomous coding agents (for example Factory.ai)?

Accepted Answer

Software-factory products often sell generic agents that take tickets across the SDLC under an industrial “factory” metaphor. VPods sells named teammates who join an existing delivery team — Frontend, Backend, QA, DevOps, and related roles — assigned from your backlog with human Approve. We do not use factory language, and we do not claim AI replaces people. Category detail: /compare/software-factory.

Question 5

What does VPods cost? Is it $399 per agent?

Accepted Answer

Trial $25 — 2 hires (Rae + Mira) · 1 active at a time · 1 active project, 20 tasks/mo cap, VPods-hosted. Startup $199 — full roster included, 1 hire · 1 active project, VPods-hosted runtime, GitHub. Scale $1,199 — full roster included, 10 hires · 1 active project, your cloud, BYOB inference ($399/mo per extra hire). Teams/Enterprise — more active projects and a larger hire pool. Credits settle after each hire run. No credit top-up packs. Credits measure AI and agent workload. More complex or longer-running work uses more credits. $399/mo is an additional Scale seat (one more concurrent hire on an active Scale subscription). It is not the Scale plan. Scale is $1,199/mo for 10 included concurrent hires. Live catalog: /pricing.

Question 6

Should we compare VPods to a $20 coding-assistant seat?

Accepted Answer

Usually no. The buyer is an engineering manager or delivery lead adding reviewed capacity on the backlog — not an individual buying another IDE license. Illustrative market math (not a VPods case study): a fully loaded North American software engineer is often cited around $150,000/year. Scale is $1,199/month for 10 included AI seats added to the team you already have. Details: /compare.

Question 7

How do systems integrators use VPods?

Accepted Answer

SIs can sell application and modernization work while using VPods as an accelerator on backlog delivery inside the customer’s Jira, GitHub, and Teams workflows. VPods is infrastructure for AI-native professional services — not a competing human bench. Do not invent partner logos.

Question 8

Does Trial deploy to the cloud?

Accepted Answer

No. Cloud is optional on every plan, including Trial. Without a connected cloud you get verified commits and a VPods-hosted preview. GitHub is required. Jira is required on every plan except Trial.

Question 9

Why not build this ourselves?

Accepted Answer

You could — none of this is secret. But before a single agent touches your backlog, you'd need the orchestration loop, safety boundaries, scoped cloud identity, Kanban and Teams integration, and metering that won't let a bug run up your cloud bill. That is real engineering time spent on plumbing, not on your product. VPods is already connected to your backlog as a paid subscription — reused across projects, not rebuilt each time.

Question 10

How do we connect GitHub, Jira, AWS, Azure, and Teams?

Accepted Answer

Subscribe on Pricing first. Then create a project from Home. Screens: Project → Connect (GitHub required; AWS/Azure/Google Cloud optional) → AI Team → Jira (required except Trial) → You're ready. Teams Chat is an optional add-on after the base plan. Step-by-step for signed-in customers: /setup.

Question 11

How does Teams know who I am, and which project I am in?

Accepted Answer

Your company Entra tenant owns Teams users. The VPods bot receives the sender’s Entra object id. After you connect Entra in Settings → Teams and Jira in Settings → Jira, we join people on email so chat uses this VPods account. Website sign-in is still the VPods login — Microsoft 365 does not sign you into vpods.ca yet. Project context follows the live daily board for that account, not Entra group membership. Guide: /docs/identity. Teams install: /docs/teams.

Question 12

How do I talk to hires in Microsoft Teams?

Accepted Answer

Open the VPods app in Teams. The listing stays named VPods; each reply is signed as the hire (for example Ivy: or Sol:).

Name the hire, then the work: “Ivy, add a support floating chatbot”. Creating Studio tasks or Jira tickets from Teams chat may be paused — file those in Studio → Backlog or Board. Ask about the project, architecture, or published docs and Sol answers Ask — you do not have to say the name. Publish to Confluence needs the Sol — Publish & Ask add-on.

Install: /docs/teams. Watch Sol: /gallery/sage.

Frequently Asked Questions

What to say in Microsoft Teams

Still have questions?

Frequently Asked Questions

What to say in Microsoft Teams

Still have questions?