PANONDA
Últimas
← News
Ferramentas·3 min read

Google Cloud now sells both OpenAI and Anthropic models. Price the same job three ways before you commit

Google Cloud added OpenAI models in private preview on Oct. 21 and Anthropic's Claude Platform on Oct. 22. One invoice, two rival vendors. What nobody has published yet is the price.

By PANONDA Newsroom

Foto: Google DeepMind · Pexels

What happened

On October 21, 2026, Google Cloud put three OpenAI models — GPT-6 Astra, GPT-6.1 Sol and GPT-6 Luna — into its Model Garden in private preview for selected enterprise customers. The next day, Anthropic made its full Claude Platform generally available on Google Cloud as an Anthropic-managed service.

Claude customers on that setup can use Google Cloud IAM for access control, Cloud Audit Logging for records, and pay through their existing Google Cloud bill. The OpenAI models are billed through Google Cloud Marketplace.

So one cloud account now reaches two competing frontier labs. That is the whole news. No new model capability was announced.

What it means for a publishing shop

If you run anything beyond a chat window — archive search, transcript cleanup, headline variants, internal tooling, batch classification of a back catalog — you have probably been opening separate accounts, separate API keys and separate card charges for each vendor. This collapses some of that.

The real shift is in how you design the workflow. The question stopped being "which model do I build on" and became "do I build on a model at all, or on a layer that lets the model change."

The second answer is better when prices move every quarter, and they have been. You route long-context archive work to one model, code maintenance to another, high-volume tagging to whatever is cheapest that month, and you don't rewrite your internal tools each time a vendor ships a new API.

What this is not

It is not a price cut. Google Cloud's final rates for the OpenAI models have not been published. Whether Google adds a markup over buying direct from OpenAI or Anthropic is not confirmed. A single invoice simplifies procurement and can still cost you more per token than two invoices did.

It is not generally available for everyone. The OpenAI models are in private preview for selected enterprise customers. If you are a four-person newsletter, you are not in that cohort this week.

It is not portability. Your prompts, tool definitions, safety settings and output quality do not travel cleanly between vendors just because the billing does. A prompt tuned for Claude does not produce the same copy on GPT-6. You still have to re-test everything.

It is not a data-handling answer. Retention terms and training terms for each offering on Google Cloud were not disclosed in the announcements. If you are uploading an archive, that is the clause that matters, not the invoice.

And it is not evidence that lock-in got weaker. Centralized logging and IAM are genuinely useful for governance. They also deepen your dependence on one cloud. Both things are true.

The pattern underneath

The model race is turning into a distribution race. The lab with the best benchmark score may not win the money. The platform that makes swapping models cheapest and safest might. For anyone buying AI tools rather than building them, that is the better trend to track — it predicts your costs for the next two years more reliably than any model launch does.

What to do about it

  1. Pick one representative workload you actually run weekly. Not a demo. Something with real volume.
  2. Price that exact workload three ways: direct with OpenAI, direct with Anthropic, and through Google Cloud. Compare the invoices, not the rate cards.
  3. Measure cost per finished output, not cost per token. A cheaper model that needs three passes is not cheaper.
  4. Put your prompts and evaluation tests in version control, tagged by model. When you switch, you re-run the tests instead of guessing.
  5. Get written terms on whether prompts, uploaded archives and outputs are used for training. Ask for it in email. Do not accept a sales call summary.
  6. Keep sensitive archives out of experimental workflows until retention and access terms are in writing.
  7. Build a fallback route to a second model before you need it. Test it once a quarter.
  8. Do not sign an annual commitment this month. The preview pricing is not public yet, and committed-use discounts are the easiest place to overpay.

Sources

Everything above was checked against these pages. Open them and see for yourself — that is why they are here.

  1. 1promptea.me
  2. 2sharedsapience.com
  3. 3dailyaibrief.blog

Get the stories by email

What changes in AI for people who publish — sourced, and to the point.

No spam. Unsubscribe anytime.