Apple’s Gemini-backed AI is still its own thing

Apple rebuilt Google-derived Gemini models into Apple Intelligence with its own data and guardrails.

Apple’s WWDC26 AI update is messy in exactly the way real infrastructure is messy: part on-device, part cloud, and one model still running on Google Cloud. The key detail is that Apple says the system is no longer a simple Google skin, even though it started from Google code.

That matters because Apple is trying to sell a very specific story about privacy, performance, and control. The company now says its third generation of Apple Foundation Models includes five models, with two running locally and three in the cloud, including one tied to Google’s servers.

Apple’s AI stack is split across device and cloud

Apple’s new setup is built around the idea that different AI jobs need different hardware. The lighter tasks stay on the device, which helps with latency and privacy. The heavier tasks move to the cloud, where Apple can use more compute without asking every iPhone to pretend it is a data center.

The article from Macworld points to five models in total. Two are local models: AFM 3 Core and AFM 3 Core Advanced. Three are cloud models: AFM 3 Cloud, ADM 3 Cloud, and AFM 3 Cloud Pro.

• AFM 3 Core handles Siri improvements on-device.
• AFM 3 Core Advanced adds more expressive voices and stronger dictation.
• AFM 3 Cloud Pro is the only model running on Google’s servers.
• Apple says the models were rebuilt for Apple Silicon and Apple’s device sizes.

That split is the real story. Apple is not shipping a single giant model and calling it a day. It is slicing the work into layers, then placing each layer where Apple thinks it makes the most sense technically and commercially.

Jason Cross of Macworld says Apple started with Gemini’s foundation models, then optimized and rebuilt them for Apple Silicon, retrained them with Apple data, weights, and guardrails. That is a much more specific claim than “Apple uses Gemini,” and it changes how you should read the whole thing.

Apple says it rebuilt the models, not just renamed them

The distinction between “derived from Google code” and “Google’s AI in Apple clothing” is doing a lot of work here. Apple wants credit for the parts that matter to users: the training data, the weights, the guardrails, and the way the models behave on its hardware.

“It seems like Apple started with Gemini’s foundation models, optimized and rebuilt them for Apple Silicon and the model sizes it needs, and retrained them with its own data, weights, and guardrails.” — Jason Cross, Macworld

That quote gets to the heart of the issue. In AI, the starting point matters less than the final tuning. A model can begin life in one lab and end up behaving very differently after retraining, safety filtering, and hardware-specific changes.

Apple’s approach also fits its broader strategy. The company has spent years making the case that it can control the full stack better than rivals can. Here, that means keeping some intelligence on-device, pushing more demanding tasks to the cloud, and limiting how much of the plumbing depends on outside infrastructure.

The numbers show how hybrid this system really is

The technical details make Apple’s position less tidy than the marketing might suggest. But they also make the system more interesting, because Apple is clearly choosing pragmatism over purity.

• 5 total Apple Foundation Models in the third generation.
• 2 models run locally on Apple devices.
• 3 models run in the cloud.
• 1 model runs on Google’s servers.
• WWDC26 was the moment Apple disclosed the setup.

That last point matters because the confusion before WWDC26 was not accidental. If Apple had been clearer earlier, the debate would have been simpler. Instead, the company let people assume the worst or the laziest explanation: that Apple Intelligence was just Google AI with a fresh coat of paint.

It is more complicated than that. Apple appears to have taken Google-originated model work, then reshaped it for its own devices, its own constraints, and its own product goals. That does not erase Google from the story, but it does make the relationship less direct than the headlines imply.

What this means for Apple Intelligence users

For users, the practical question is whether the AI feels fast, private, and useful. If AFM 3 Core and AFM 3 Core Advanced do what Apple claims, the on-device pieces should keep common tasks responsive. The cloud models can handle the heavier lifting without forcing every request through the same path.

The bigger issue is trust. Apple is asking people to believe that a model lineage matters less than the final implementation. That is a fair argument if the outputs are good and the privacy story holds up. It is a harder sell if users keep hearing that one of the models is still living on Google’s infrastructure.

There is also a cultural problem here. “AI” has become a catch-all label for code completion, image generation, data analysis, and synthetic slop. That fuzziness helps companies bundle good tools with bad ones and sell the whole package as inevitable progress. Apple’s version is cleaner than most, but it still sits inside that same overloaded label.

The real test is simple: does Apple Intelligence feel like Apple software, or does it feel like a borrowed model wearing an Apple badge? If Apple keeps the on-device pieces fast and the cloud pieces useful, most people will stop caring where the first version of the model came from. If not, the Google connection will keep leaking into the conversation every time Apple talks about AI.

My bet is that Apple will keep tightening the split between local and cloud models, because that is the only way this story stays believable. The next question is whether Apple can make that architecture invisible to users, or whether the Google origin of one model keeps surfacing every time Apple explains how its AI works.