Enterprise AI Coding Rollout

Four controls decide whether security will sign off: who has access, what the policy allows, how data moves and whether anyone measures adoption. Settle them before the pilot starts, because they apply whichever tool you pick.

The owner column matters as much as the controls. A control with no named owner goes unchecked until someone has to answer for it. If nobody owns identity, for example, nobody checks that people who leave lose access.

Security does not own all four. Identity is IT's system of record, and policy is engineering leadership's call about what the team may ship. Adoption belongs to whoever owns developer experience. Security owns the data-flow question and the audit path, and it will ask about both.

Data flow is the question that stalls approvals, so answer it before the review meeting. Write down what the tool can read, what it can change, what leaves your network and where any of it is retained. Most of the answers come from the vendor's documentation and your own configuration. Ask the vendor for anything the documentation leaves out, and note where each answer came from.

The stack below breaks a rollout into layers. Policy comes first because the other layers carry it out. Identity controls who gets access, workflow moves code from prompt to merge, and measurement shows whether the rollout is working.

Start narrow, and expand only when the pilot earns it.

1. 1Week 1: pick one team, one repo and three realistic tasks.
2. 2Week 2: write the workflow standard from the pilot.
3. 3Week 3: train champions and add policy guardrails.
4. 4Week 4: expand only after quality, cost and review load are visible.

Treat the four weeks as an order, not a deadline. The first two weeks mostly show you what your standard should say. A pilot too broad to watch closely can't teach you that, so it starts with one team and a few real tasks. Pick the team that will tell you when something breaks, even if another team would produce a better-looking result. Put policy and training in place before the rollout grows, because both are harder to add once people have formed their own habits.

Expansion is the step to slow down. After a good pilot, the pressure to widen access can arrive before the evidence does. Before you add teams, answer three questions with numbers: did review load go up or down, what does a developer cost per month, and did quality hold.

Record the same numbers before the pilot starts, so you have a baseline to compare against. Two more weeks of the same pilot cost less than a rollout you have to walk back, so run them if any answer is still a guess.

Cursor ships often, so advice about it can go out of date. The table summarizes Cursor's recent releases, so you can check this page against the current product. For each release's date and sources, see What's new in Cursor 2026.

Measure it from your git host. Cursor's admin analytics dashboard reports adoption: AI share of committed code, Agent and Tab edits, messages by mode and model, active users per surface, daily usage, a usage leaderboard and repository insights. It also counts Cloud Agent work (agents created, PRs opened and merged, and lines merged), and on Enterprise it adds the Conversation InsightsA Cursor analytics view that passively categorises what agents are doing (new features, bug fixes, refactors) so leaders can see where engineering time goes. Press Enter for the full definition. classifier. Reviewer comments and rework passes come from pull request data instead, and someone has to collect them.

Know how the adoption number is built before you quote it in a steering meeting. AI share of committed code comes from signatures Cursor logs on the device for AI-suggested lines. Cursor matches them against later commits by the same author on the same machine. Automated formatters can invalidate those signatures, and CLI commits have to be scored on the machine where the code was written.

Older guides say the tracking skips Background Agents and the Cursor CLICursor's command line: the full agent, all modes and models, in the terminal and pipeable into scripts and CI. Press Enter for the full definition.. That changed: Cursor's docs now say it covers the CLI and Cloud AgentsAgents that run in a Cursor-managed virtual machine, check out the repo, do the work and open a pull request, then shut down, with no load on your laptop. Press Enter for the full definition.. If a chart still shows a drop that doesn't match what your team sees, check for formatter runs and commits made on other machines first. Cursor asks you to report missing metrics for a workflow as a bug.

Pair one number from each side, and keep both simple: one from the dashboard for adoption and one from the git host for review cost, both filtered to the pilot repo.

The plumbing supports that. Analytics need client 1.5 or later, the user, group and date filters cover up to 90 days, and every chart exports to CSV. On Enterprise, the Admin API is there for the day this becomes a scheduled report.

No. A spend alert sends an email when spending crosses a threshold. A spend limit is the control that caps cost.

Where you set alerts depends on the plan. On a legacy Teams plan, add them in the team dashboard at team or member level, and choose whether member-level alerts go to admins, the member or both. On The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition., Teams admins set them on the Alerts page under Billing, and additional usage has to be turned on first.

The trigger decides when you hear anything. Alerts count only additional usage: on-demand spend on legacy plans, or prepaid-credit usage on The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition.. Included usage never counts, so the first email arrives after the included allowance is gone, too late to serve as an early warning. Enterprise accounts with pooled usage can set member-level alerts against total spend instead.

Routing sits underneath the alerts: on Teams and Enterprise, Cursor Router powers Auto, and Cursor's Router docs say only Cost mode keeps classic Auto pricing. Balance and Intelligence bill at the list price of the model that served each request, plus the Cursor Token Rate on eligible third-party models, and the docs say they use your limits faster. The help center's Router page says all Auto modes bill at the routed model's list price, so check real usage first.

The default differs by plan, so check it on day one. The router is on by default for Teams plans, so a Teams rollout can spend at routed rates without anyone touching the model picker. On Enterprise it stays off until an admin enables it, which leaves an unmade decision that looks like a working default.

Buy them for a small group, and buy them late. On The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition., each Teams seat is Premium at $30 per user per month, Super at $100 with 3.75 times Premium's weekly usage, or Ultra at $200 with 12.5 times. Upgrade only the heavy agent users.

Usage data tells you who those people are. Each paid seat has its own weekly pool for Cursor models (Grok 4.7Cursor and SpaceXAI's current lead Cursor model, in the weekly pool at $2 per million input tokens and $6 per million output, with a 256k context window and a 500k variant; above 256k input tokens it bills at 2x the standard rate. Press Enter for the full definition., Grok 4.6A Cursor and SpaceXAI model for complex coding and knowledge work, still in the Cursor model pool and succeeded by Grok 4.7; it is a selectable model and is separate from the Grok Bot product. Press Enter for the full definition., Grok 4.5 and Composer 2.5The current Composer release, better at long-running tasks and at judging when a job needs a light touch versus deep work. Press Enter for the full definition.), and seats don't share pools. Third-party models sit outside every pool and bill from the team's prepaid balance from the first request. Auto has no pool of its own: Cost mode draws on the seat's weekly pool, and a Balance or Intelligence request routed to a third-party model bills to the prepaid balance. A bigger seat only helps someone who runs out of the Cursor-model pool, and guessing early means paying for that headroom before anyone has changed how they work.

One month on Premium seats is usually enough to sort the team. Then upgrade the people who ran out of their weekly pool.

Teams created before The X SubscriptionThe subscription Cursor is sold through: one plan for Grok, Cursor and X, with Free, Plus, Premium, Super and Ultra tiers, per-seat Teams, a weekly included pool for Cursor models shared with Grok, and third-party models billed at API list price from prepaid credit. Press Enter for the full definition. keep their June 2026 seats until they switch. Standard costs $32 per seat per month billed annually, or $40 monthly. Premium costs $96 annually or $120 monthly, for five times Standard's usage at three times the price. Those seats split usage into two monthly pools, Cursor ModelsOn legacy Cursor plans, the monthly usage pool for Cursor's own models (Grok 4.7, Grok 4.6, Grok 4.5 and Composer 2.5), kept separate from the third-party Other Models pool. The X Subscription replaces it with one weekly pool. Press Enter for the full definition. and Other ModelsOn legacy Cursor plans, the monthly pool for supported third-party models from providers such as Anthropic, Google and OpenAI, separate from Cursor Models. On The X Subscription third-party models are billed from prepaid credit instead. Press Enter for the full definition.. The same advice holds there: start on Standard, then upgrade the people who run out.

The order stays the same, with less ceremony. A small team can run one shared workflow, a two-week pilot and a single review rule, with the four control owners collapsed onto two people. Write those two names down. At small scale, the usual failure is that nobody owns the data-flow answer when a customer's security questionnaire arrives. The startup rollout plan and the 10-developer pilot are sized for that.

Somewhere past about a hundred developers, the pilot itself needs structure. The exact point varies, so treat that number as a rough marker. Use cohorts instead of volunteers, champion teams, a support route for when something breaks, and measurement split by repo type, because a monolith and a set of services produce different review loads from the same tool. The 100-developer plan walks through that version.

Identity changes most with size. At twenty seats you can hand out access and fix it later. At two thousand you can't, so settle identity first, then map Organizations, teams and groups onto the org chart, then pilot inside that structure. Fitting cohorts onto people who already have broad access means taking access away from someone.

In one Cursor talk, Cursor's own finance team described a pattern that applies well beyond finance. It had no embedded engineers, and the one engineering partner it brought in at the start was security engineering, so the foundation was right before anyone built anything. That meant Okta permissions, GitHub structure, and credentials for the data and SaaS tools people would reach for.

Make the basics consistent across the org, then let people build on top of them. Otherwise every team invents its own access story, and security has to audit each one afterward.