Random Llama
  • Work
  • Blog
  • About
  • Contact
Start a project

Random Llama Software, LLC

Custom software for businesses with a problem no off-the-shelf tool fits. Built and maintained in Richmond, Texas.

Richmond, TX · Est. 2025

Work

  • Full index
  • Custom development
  • Site maintenance
  • Changelog
  • Blog

Company

  • About
  • FAQ
  • Contact

Weekly, on Thursdays

What shipped this week

Every Thursday: changelog entries from the week, any build notes we published, and a rotating spotlight on one shipped tool. Unsubscribe from any issue.

© 2026 Random Llama Software, LLC

Privacy policyTerms of serviceCookie policy
GitHub / orgGitHub / personal

Blog

May 2, 2026

ai-tools · industry-news · model-releases

All posts

GPT-5.5 and Gemini 3.1 Drop. OpenAI Leaves Microsoft Exclusive.

Robert Hattala · May 2, 2026


01 · Article

Two flagship models landed this week and one of the most consequential business moves in AI happened quietly in the fine print. Let's get into it.

GPT-5.5 and Gemini 3.1 Ultra Are Both Out

OpenAI released GPT-5.5 with meaningful upgrades to coding, computer use, and agentic task performance. The framing from OpenAI is less "smarter" and more "more capable of taking action." It's positioned as the model you reach for when you need something to actually do work, not just answer questions.

Google's Gemini 3.1 Ultra landed with a 2-million token context window and was built from the ground up to handle text, image, audio, and video natively, not bolted on after the fact. That multimodal-from-training design is worth taking seriously. Most long-context benchmarks favor Gemini right now, and 2 million tokens changes what's architecturally possible for enterprise workflows.

Both models are genuinely good. The benchmark wars are getting tedious. What matters is which one integrates cleanly into your stack and does the actual work you need. Run your own evals. Don't outsource your opinion to a leaderboard.

OpenAI Is Breaking Up With Microsoft Exclusivity

This one didn't get the headlines it deserved. OpenAI loosened the exclusivity structure it had with Microsoft that previously limited where it could distribute its models. The result: OpenAI models are coming to Amazon Web Services, with room for Google Cloud too.

Microsoft's competitive moat around Azure as the primary distribution channel for OpenAI has been a real and meaningful differentiator. That's changing now. AWS and Google Cloud customers are going to get first-party access to OpenAI models, which means the model layer is becoming less of a platform advantage and more of a commodity available everywhere.

For anyone building on OpenAI through Azure: nothing breaks immediately. But the strategic picture looks different when your vendor's flagship partner is also distributing through your competitors. Keep an eye on where the pricing and SLA differences land when this plays out.

Also: Google's TurboQuant Paper Is Worth 20 Minutes of Your Time

Google presented TurboQuant at ICLR 2026, an algorithm that significantly cuts the memory overhead from KV cache, the part of a model that holds context during inference. It sounds like a research paper, and it is, but it directly affects the economics of running massive context windows at scale.

Cheaper inference on large context models means more of what was only possible at the frontier starts being viable for mid-size deployments. When this hits production, it's going to change the math for a lot of teams currently priced out of the long-context use cases.


Related

Related posts

  • AI Models Hacked Hugging Face Just to Cheat on a TestJuly 30, 2026
  • Nvidia Bets $250B on OpenAI While an AI Model Breaks FreeJuly 27, 2026
  • AI News: Claude Sonnet 5 Ships, Copilot Goes Open SourceJuly 25, 2026
Related posts
PostPublished
AI Models Hacked Hugging Face Just to Cheat on a TestJuly 30, 2026
Nvidia Bets $250B on OpenAI While an AI Model Breaks FreeJuly 27, 2026
AI News: Claude Sonnet 5 Ships, Copilot Goes Open SourceJuly 25, 2026

02 · Contact

Building something similar? Describe the workflow you want replaced.

Start a projectWork index