Skip to content

Product1 publisher3 min readPublished

Promevo's Insights keeps Gemini Enterprise seat and agent records past Google's 28-day window

Promevo launched Insights to join Gemini Enterprise license and agent data that, it says, Google's consoles split apart and keep for only 28 days. It is aimed at admins who have to name idle seats and audit the agents staff build themselves.

The Product Desk · Product desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

What happened

  • Insights separates activated Gemini Enterprise seats that are in use from idle ones, and puts an estimate on the share of idle-seat spending a customer could recover.
  • Insights also lists the agents employees have built, along with what each one can access.
  • Where agents touch Google Cloud, Promevo says customers can follow a license to the agent that uses it, and from that agent to the cloud resources it relies on.
  • Insights is available now for Google Workspace and Gemini Enterprise customers, with more of the platform rolling out over the coming weeks.

Compiled by The Product DeskSomething wrong?How this is made

Why it matters

  • cost A seat that looks idle over 28 days may belong to someone who uses it once a quarter, so cuts made from the native view alone can remove seats people actually work in.
  • constraint Once any employee can build an agent in a no-code workbench, a hand-kept list of agents and their access falls behind as fast as staff build.
  • exposure Buying Insights to close the gap means giving an outside vendor identity and access data gathered across projects, which is an access decision in its own right.

Say finance sends the Workspace admin one email with two questions: which Gemini Enterprise seats can be dropped, and which of the agents staff have built can open the shared finance drive [2]. According to Promevo, the admin has to answer from two places. Google's Cloud and Workspace consoles keep license data and agent data in separate systems, each with a rolling 28 days of history [3].

Gemini Enterprise launched a year ago [2], so a 28-day console window covers about 8 percent of the product's life [15]. Insights flags a seat as "in use" when it has been activated and used [5]. That is activity in a period. A seat decision depends on whether people keep coming back month after month and how much of their work runs through the tool. Both need more than four weeks of records.

A rollout plan that budgets for a few dozen experimental agents is preparing for a smaller job than the one Promevo's chief executive describes [11]. Karthik Kripapuri said the company is "already seeing customer organizations with thousands of agents" and expects that kind of scale to become common [11]. He said one of the biggest questions enterprises have is whether agents are staying "within proper boundaries" [10]. That count comes from the vendor selling the inventory.

Promevo's pitch is a "visibility gap" [14]. What the product actually does is pull two sets of Google data into one place and keep them longer [4]. It also gathers identity and access data across projects and flags users with more permissions than they need [8]. Promevo said it does this without reading or storing the content of prompts and responses [7]. The estimate of reclaimable spend comes from a company that also sells a structured Gemini Enterprise adoption program [12].

The decision comes down to two things: how far back your seat review looks, and how many agents employees have built.

- Review within four weeks, dozens of agents: the native consoles are enough. - Review further back, dozens of agents: the missing piece is history, and someone writing down the console numbers every four weeks covers most of it. - Review within four weeks, thousands of agents: the missing piece is the agent inventory and what each agent can reach, which is the part Insights is built around [6]. - Review further back, thousands of agents: both pieces are missing, and this is the customer Kripapuri describes [11].

In the first two cases I'd use the consoles and a calendar reminder before paying anyone. The tradeoff is staff time, plus a log that holds only what someone remembered to record, set against a vendor bill. Promevo did not publish a price for Insights or say how far back its record runs [4][13].

What to watch

  • Google lengthening the 28-day window or joining license and agent data in its own consoles, removing the gap partners like Promevo sell into.
  • Agent-per-organization counts from someone other than Promevo, to test Kripapuri's thousands-of-agents figure.
  • Promevo naming customers who cut idle seats on its estimate, and the amount they actually recovered.
Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories