First off, apologies for the bad first impression, the team is pushing super hard to make sure it is easy to access these models.
- On permission issue, not sure I follow the flow that got you there, pls email me more details if you are able too and happy to debug: Lkilpatrick@google.com
- On overall friction for billing: we are working on a new billing experience built right into AI Studio that will make it super easy to add a CC and go build. This will also come along with things like hard billing caps and such. The expected ETA for global rollout is January!
> I get the feeling GCP is not good for individuals like I.
Google isn't good for individuals at all. Unless you've got a few million followers or get lucky on HN, support is literally non-existent. Anyone that builds a business on Google is nuts.
I'd like to state the AWS, in contrast, has been great to me as an individual. The two times that I needed to speak to a human, I had one on the phone resolving my issue. And both issues were due to me making mistakes - on my small personal account.
Yes, it’s extremely complicated. I gave up on fire base for one project because I could not figure out how to get the right permissions set up and my support request resulted in someone copying and pasting a snippet from the instructions that I obviously had not understood in the first place.
It’s also extremely cumbersome to sign up for Google AI. The other day I tried to get deep seek working via Google’s hosted offering and gave up after about an hour. The form just would not complete without error and there was not a useful message to work with.
It would seem that in today’s modern world of AI assistance, Google could set up one that would help users do the simplest things. Why not just let the agent direct the user to the correct forms and let the user press submit?
Oh man, I've been playing with GCP's vertex AI endpoints, and this is so representative of my experience. It's actually bananas how difficult it is, even compared to other GCP endpoints
I was interested. I does look like he just needs to update that. His personal blog says google, and ex-openAI. But I do feel like I have my tin foil on every time I come to HN now.
Its not a new problem though, and its not just billing. The UI across Gemini just generally sucks (across AI Studio and the chat interfaces) and there's lots of annoying failure cases where Gemini will just timeout and stop working entirely midrequest.
Been like this for quite a while, well before Gemini 3.
So far I continue to put up with it because I find the model to be the best commercial option for my usage, but its amazing how bad modern Google is at just basic web app UX and infrastructure when they were the gold standard for such for like, arguably decades prior.
We are talking here about the most basic things- nothing AI related. Basic billing. The fact that it is not working says a lot about the future of the product and company culture in general (obviously they are not product-oriented)
Given how many paid offerings Google has, and the complexity and nuance to some of those offering (e.g. AdSense) I am pretty surprised that Google don't have a functioning drop in solution for billing across the company.
If they do, it's failing here. The idea of a penny pinching megacorp like Google failing technically even in the penny pinching arena is a surprise to me.
Even though my post complaining about google's billing and incoherent mess got so many upvotes, I'll be the first to say that there is nothing basic about "give me money".
Apart from the fact that what happens to the money when it gets to google (putting it in the right accounts, in the right business, categorizing it, etc), it changes depending on who you're ASKING for money.
1. Getting money from an individual is easy. Here's a credit card page.
2. Getting money from a small business is slightly more complicated. You may already have an existing subscription (google workspaces), just attach to it.
3. As your customers get bigger, it gets more squishy. Then you have enterprise agreements, where it becomes a whole big mess. There are special prices, volume discounts, all that stuff. And then invoice billing.
The point is that yes, we all agree that getting someone to plop down a credit card is easy. Which is why Anthropic and OpenAI (who didn't have 20 years of enterprise billing bloat) were able to start with the simplest use case and work their way slowly up.
But I AM sensitive to how hard this is for companies as large and varied as Google or MS. Remember the famous Bill Gates email where even he couldn't figure out how to download something from Microsoft's website.
It's just that they are also LARGE companies, they have the resources to solve these problems, just don't seem to have the strong leadership to bop everyone on the head until they make the billing simple.
And my guess is also that consumers are such a small part of how they're making money (you best believe that these models are probably beautifully integrated into the cloud accounts so you can start paying them from day one).
My first thought was this is the whole thing about managers at Google trying to get employees under other managers fired and their own reports promoted -- but it feels too similar to how fucked up all the account and billing stuff is at Microsoft. This is what happens when you try to "fix" something by layering on more complexity and exceptions.
From past experience, the advertising side of the business was very clear with accounts and billing. GCP was a whole other story. The entire thing was poorly designed, very confusing, a total mess. You really needed some justification to be using it over almost everything else (like some Google service which had to go through GCP.) It's kind of like an anti-sales team where you buy one thing because you have to and know you never want to touch anything from the brand ever again.
We made the bet 2 years ago to build AI Studio on top of the Google Cloud infra. One of the real challenges is that Google is extremely global, we support devs in hundreds of countries with dozens of different billing methods and the like. I wish the problem space was simple but on the first day I joined Google we kicked off the efforts to make sure we could bring billing into AI Studio, so January cannot come soon enough : )
No one should even notice the payment flow. This isn't Stripe where the polish on the payment experience is a selling point for the service. At Google, paying for something should be a boring but quick process that works and then gets out of the way.
It doesn't need to be good. It just need to be not broken.
That’s a pretty uncharitable take. Given the scale of their recent launches and amount of compute to make them work, it seems incredibly smooth. Edge cases always arise, and all the company/teams can really do is be responsive - which is exactly why I see happening.
A company with a literal embedded payment processor, including subscription services for half of all mobile users can't manage to take payments for their own public facing services seems like a huge fucking failure to me.
Especially for software developer and tech influencer focused markets.
Considering the product itself seems to be excessively limited without actually getting paid for it, and the paid tier itself having so many onboarding issues, as a critical usage path, it's pretty bad.
This is in a $3.6 Trillion company, for a product they're spending billions a quarter to develop, with specialized employees making mid 6-figure to 7-figure salaries and bonuses... you'd think somebody has the right connections into the departments that typically handle the payment systems.
My expectations shoot up dramatically for organizations that have all the funding they need to create something "insanely great" in terms of user experience the further they fall short... I don't know who the head of this group/project/department/product is... but someone failed at their job, and got payed excessively for this poor execution.
When we first started using Gemini for a new product a few months ago you banned our entire GCP account from using at all Gemini in the middle of a demo to our board. Doesn't seem like things have improved all that much on the on boarding front.
The new releases this week baited me into business ultra subscription. Sadly it’s totally useless for gemini 3 cli and now also nano banana does not work. Just wow.
I bought a Pro subscription (or the lowest tier paid plan, whatever it's called), and the fact that I had to fill out a Google Form in order to request access to get Gemini 3 CLI is an absolute joke. I'm not even a developer, I'm a UX guy who just likes playing around with seeing how models deal with importing Figma screens and turn them into a working website. Their customer experience is shockingly awful, worse than OpenAI and Anthropic.
Oh man, there is so, so much pain here. Random example - if GOOGLE_GENAI_USE_VERTEXAI=true in your environment, woe betide you if you're trying to use gemini cli with an API key. Error messages don't match up with actual problems, you'll be told to log in using the cli auth for google, then you'll be told your API keys have no access.. It's just a huge mess. I still don't really know if I'm using a vertex API key or a non-vertex one, and I don't want to touch anything since I somehow got things running..
Anyway vai com dios, I know that there's a fundamental level of complexity deploying at google, and deploying globally, but it's just really hard compared to some competitors. Sadly, because the gemini series is excellent!
Thank you for your service. Also, one of the main issues from the outside seems to me to be the impedance mismatch between google's entire cloud business and the direct-to-dev type API access oAI and Anthropic have pioneered. So, there's always going to be some pain here. It would be realllyy nice if that pain were incurred internally at the mothership, both for Dev UX and for sales. But so far, it looks to me like it's being spread out internally and externally.
Lol. Since the GirlsGoneWild people pioneered the concept of automatically-recurring subscriptions, unexpected charges and difficult-to-cancel billing is the game. The best customer is always the one that pays but never uses the service ... and ideally has forgotten or lost access to the email address they used when signing up.
Hi, is your team planning on adding a spending cap? Last I tried, there was no reasonable way to do this. It keeps me away from your platform because runaway inference is a real risk for any app that calls LLMs programatically.
The fact that your team is worrying about billing is...worrying. You guys should just be focused on the product (which I love, thanks!)
Google has serious fragmentation problems, and really it seems like someone else with high rank should be enforcing (and have a team dedicated to) a centralized frictionless billing system for customers to use.
We use Google Cloud's billing service, but given the super global nature of our customer base, there is a lot of complexity in moving this into AI Studio. Though we are making great progress!
Since 3 days I am trying to get a login to Antigravity and first there was trouble with an api now all I get is 'Your current account is not eligible for Antigravity. Try signing in with another personal Google account'. Even though it is verified and in a supported region...
This is nice that you know about the issue and are working on it. I really appreciate all the new "Get api key" buttons across google ai products that already makes it much easier than setting up a cloud project and getting credentials json files.
But I do think it's a general problem with Google products that the solution is always to build a new one. There are already like 8 ways to use and pay for Google AI and that adds to the complexity of getting set up, so adding a new simpler better option might make that all worse instead of better
Maybe if the sign up process encouraged people to send videos (screen-side and user-side could be useful also), of their sign-up and usage experience, the teams responsible for user experience could make some real progress.
I guess the question is, who cares, or who is responsible in the organization?
The permission thing happens to me too, but very intermittently, usually a couple of hard refreshes of the tab clears it up, sometimes I need to delete the conversation I'd just tried to start and start a new conversation. I can't remember the exact message, sometime like you don't have permission or permission denied. If I had to guess it happens 1 in 5 sessions I load. The API key stuff would be a lot easier if it landed you on the correct page in the GCP portal when it directs you out of AI studio, I think that is the most confusing part of the experience, you end up on what seems like a random GCP billing page with no clear indication as to what it has to do with API keys.
Pls email me if you can on the latter, we can update whatever pointers we have to the cloud console and make them more contextual. We are also pushing on the north star of the P99 user experience not needing to leave AI Studio. We have landed a lot of stuff to make this possible already!
Just make it a VSCode plugin, I don't want to install a new IDE (which is just VSCode anyway) to use your product. It might be better than claude and chatgpt5.1 but not better enough to justify me re-doing all my IDE configs.
Any chance that this reflected to our company account instead of AI Studio?
We want to switch to Gemini from Claude (for agentic coding, chat UI, and any other employee-triggered scenarios) but the pricing model is a complete barrier: How do we pay for a monthly subscription with a capped price?
You launched Antigravity, which looks like an amazing product that could replace Claude Code, but do I know I will be able to pay for it in the same way I pay Claude, which is a simple pay per month subscription?
I had the same reaction as them many months ago, the Google Cloud and Vertex AI stuff namespacing is a too messy. The different paths people might take to learning and trying to use the good new models needs properly mapping out and fixing so that the UX makes sense and actually works as they expect.
Hopefully the mobile version of AI Studio gets some improvement. There are some pretty awful UI bugs that make it really difficult to use in a mobile first manner.
Though I still managed to vibe code an app using nanobanana. Now I just need to sort API billing with it so I can actually use my app.
Dude. Let me give you my money. This isn’t rocket science. I don’t want anything to do with Google Cloud or Google Workspace or w/e it’s called now. Let me just subscribe to Gemini or Nano straight up.
Can we get free Nano Banana in AI studio at least in super low resolution? For app building and testing purposes it will be fine and cheap enough for you to make it possible?
- On permission issue, not sure I follow the flow that got you there, pls email me more details if you are able too and happy to debug: Lkilpatrick@google.com
- On overall friction for billing: we are working on a new billing experience built right into AI Studio that will make it super easy to add a CC and go build. This will also come along with things like hard billing caps and such. The expected ETA for global rollout is January!