ADO Pilot is a cloud service. You can run it against any Azure DevOps Services organization that is reachable over HTTPS from the public internet, with a modern browser for the management portal and a Stripe-supported payment method for paid plans.

## Azure DevOps platform

| Platform                      | Supported in v1 |
| ----------------------------- | --------------- |
| Azure DevOps Services (cloud) | Yes             |
| Azure DevOps Server (on-prem) | No              |

On-premises Azure DevOps Server is not supported in v1 and is not on the near-term roadmap. The webhook architecture relies on your organization's service hooks reaching `adopilot.dev` over HTTPS, which an air-gapped Server install cannot do.

## Network and security

- All ingress and egress is over HTTPS. Azure DevOps service hooks reject `http://` and `localhost` targets, and ADO Pilot only exposes HTTPS endpoints.
- If your organization restricts outbound traffic, allow HTTPS to `adopilot.dev` (the docs and marketing site) and `app.adopilot.dev` (the management portal), plus the Stripe hosts that render billing: `js.stripe.com` and `*.js.stripe.com`, `api.stripe.com`, `hooks.stripe.com`, `link.com` and `*.link.com` (Stripe Link, an on-by-default saved-card accelerator), and the hosted billing portal at `billing.stripe.com`. Stripe maintains the authoritative allowlist in its [integration security guide](https://docs.stripe.com/security/guide#csp) — a partial allowlist can silently break Stripe Link for returning customers.
- Azure DevOps service hooks do not support HMAC signing. Webhook authorization to ADO Pilot's ingress is enforced with a per-tenant credential that the wizard provisions automatically.

## Browser support

The management portal at `app.adopilot.dev` is tested against the latest two versions of Chrome and Edge. Firefox and Safari work but are not part of the regression suite. The portal is responsive on mobile, but the in-Azure-DevOps settings hub from the Marketplace extension is desktop-only.

## Billing and payments

- Paid plans are charged through Stripe. Entering or updating a payment method loads Stripe's client-side components — including Stripe Link, which may offer to save your card for faster checkout next time — so your browser needs access to `js.stripe.com`, `*.js.stripe.com`, `api.stripe.com`, `hooks.stripe.com`, `link.com`, and `*.link.com`; managing your subscription through the billing portal also reaches Stripe's hosted `billing.stripe.com` pages.
- Stripe accepts Visa, Mastercard, American Express, and Discover. The set of supported countries is whatever Stripe supports for the merchant of record. See the [Stripe documentation](https://docs.stripe.com/) for the current list.
- The free trial is offered without a payment method. You only enter card details when you select a paid plan.

{% callout type="info" title="Identity re-confirmation required" %}
Before you can open the Stripe billing portal, add a payment method, change the overage cap, or convert or end a paid plan, an org admin must recently re-confirm their identity (a "step-up" check): a fresh authenticator code if two-factor authentication is enrolled in **Settings → Security**, their account password if they sign in with a password, or a one-time code we email to their current address if they sign in without a password (a magic link, an email code, or **Sign in with Microsoft**) — two-factor authentication is not required. Selecting your initial plan during onboarding does not require this check. Viewing or downloading an invoice requires neither. Continuing on free-trial credits requires neither either. See [Step-up re-authentication](../trust/account-security.md#step-up-re-authentication) for details.
{% /callout %}

## Azure DevOps organization access

To complete onboarding you need:

- A user account in the target Azure DevOps Services organization that can create a personal access token (PAT) with the scopes listed in [Creating a personal access token](../connecting-ado/creating-a-pat.md).
- Permission to add service hook subscriptions to the projects you want reviewed. The wizard creates one `git.pullrequest.created` and one `git.pullrequest.updated` subscription per selected project.
- Optionally, organization-admin permission to install the Marketplace extension. The extension is not required — see [Installing the extension](installing-the-extension.md).