Answers to the questions we get the most.
What VigilOps does today, what is on the roadmap, how billing and seats work, and how your code is handled. Updated as the product and pricing change.
FAQ
Everything in one place.
What does VigilOps actually do?
VigilOps is an autonomous agent that runs your maintenance loop on GitHub — bug fixes, PR summaries, deprecated-API cleanup, regression-test generation, and failing-check fixes — so your engineers stay focused on product work. See /features for the full capability list.
Which version-control platforms are supported today?
GitHub is the live integration today. Onboarding installs a single GitHub App scoped to your organization and pulls findings on every push and pull-request open.
Do you support Jira, GitLab, or Bitbucket?
Jira is on our near-term roadmap — webhook plumbing already exists on the platform side and the issue sync is the next integration we are shipping. GitLab and Bitbucket are planned further out. The integration tier is already included in /pricing, whether you turn it on today or later.
How does billing work?
Checkout goes through a fresh Stripe session — there is no signup before payment, no card on file, and no manual invoice flow unless you are on Enterprise. Free is $0 forever; Team is $99 per developer per month, monthly or yearly. See /pricing for the full breakdown.
Which repositories does VigilOps work on?
Any GitHub repository the installed GitHub App is granted access to — public or private. There is no language lock-in: the scanner handles JavaScript, TypeScript, Python, and Java today, and the grammar support expands with each release (see /changelog).
How is my source code handled?
The agent runs against a tokenized GitHub App scoped to a single organization. Code only flows in for the lifetime of the pull request that produced a fix — the agent does not persist your code beyond that lifecycle. Findings from one customer never train, leak, or cross into another tenant.
What is the data retention policy?
Enterprise plans negotiate custom data retention and sign a DPA — full details on the Enterprise tier at /pricing. For Team, scan findings and PR summaries stay available as long as your subscription is active; if you cancel, the rules are spelled out on /pricing. Free plan retention matches the Team baseline.
How are seats counted?
One seat = one developer who pushes code and receives agent fixes. Team leads, managers, and stakeholders who only read reports do not require a seat. Add or remove seats any time; changes prorate to the day. Full terms are on /pricing.
Can I cancel or switch plans?
Yes, from your account settings any time. Mid-cycle cancellations keep access through the end of the current billing period — bug-fix runs and PR summaries shut off there and your data stays put, so re-activation is one click. Switching between monthly and yearly is also self-serve; credits and cutovers are detailed on /pricing.
Do you offer refunds?
The Team and Enterprise plans spell out the cancellation and refund terms on /pricing — there are no surprise clauses, and the same terms apply whether you came in through the self-serve flow or a sales-assisted setup.
Is there a free trial of the Team plan?
The Free plan is the hands-on trial — you connect one GitHub repository, run the bug-fix agent on demand, and read the codebase health dashboard at no cost. Team starts at $99 per developer per month with the cancellation terms spelled out on /pricing.
Where can I get in touch for a sales conversation?
For volume, security review, SSO, or self-hosted deployment, send a note via /contact. The Team and Enterprise tiers route through a one-business-day sales reply.
Question we did not cover?
Send a note and we will get back within one business day. No form to fill, no gating — just a real reply.
Get in touch