#Feature Request: Flexible Compute Allocation / Feature Opt-Outs (Pro Tier & Above)

2 messages · Page 1 of 1 (latest)

tardy compass
#

The Concept:
Provide an option for users starting at the Pro tier to intentionally deselect specific generative features—such as Veo (Video generation) or Lyria (Music generation)—in exchange for a higher allocation of AI credits or rate limits on core productivity tools.

Target Audience:
This would be a massive value-add for non-corporate developers, hobbyists, and independent professionals. These users heavily utilize tools like Google Antigravity, Gemini Code Assist, or extended Pro model chat context for coding and agentic workflow orchestration, but might not have the budget to upgrade to the Ultra tier. Currently, their multimodal generation quotas often sit completely untouched.

Why this is a Win for Google:

  • Optimized Hardware Allocation: Multimodal rendering (high-fidelity video and audio) requires significantly heavier compute resources compared to text-based LLM queries or agentic IDE orchestration. Letting users explicitly opt-out gives Google highly predictable data for monthly hardware, TPU, and server allocation planning.

  • Creating Organic Evangelists: Enthusiasts and hobbyists are ultimately Google’s best grassroots salespeople. By giving them the flexibility to maximize the dev and orchestration tools they actually use, they can push the limits of platforms like Antigravity. When they demonstrate the incredible, tangible value they get out of their subscription, it serves as the best possible marketing to drive broader enterprise and peer adoption.

kindred hawk
#

Hey @tardy compass, thanks for sharing this very detailed suggestion on flexible compute allocation, this is very helpful! 🙂