Run compatible mixture-of-experts models whose complete weights would not normally fit in your device’s memory—without sending inference to a cloud API.
Live execution pathLocal storage → unified memory → Metal
Local storage
Expert payloads
verified · checksummed
Unified memory
Expert bank
E03E11E24E—
device-sized · reusable
Apple Silicon
Metal inference
routed · local
Why MoE is different
Hundreds of experts. Only a few active.
A mixture-of-experts model may contain hundreds of experts, but each token activates only a small subset. Traditional inference still loads every expert into memory.
Overfit keeps shared layers and non-expert weights resident, while routed experts stay in a verified package on local storage. The complete parameter count becomes less tied to memory capacity; active parameters, storage speed, reuse, context, and bank size shape performance instead.
Allshared layers resident+Fewexperts active per token
How Overfit works
Storage becomes a managed backing store for expertise.
01
Package
Reorganize the model. Preserve the weights.
On Mac, Noema converts a compatible MoE GGUF into a .noema-paged package. Conversion does not retrain, prune, or replace the model’s weights—it changes how they are stored and loaded.
A smaller resident GGUF with the model’s always-needed weights.
Separate expert payloads optimized for paged access.
A strict manifest covering every expert, tensor, offset, size, and checksum.
02
Size
Build an expert bank for this device.
At launch, Noema sizes the bank from available memory. A larger bank retains more experts and reduces storage reads; a smaller bank leaves room for context, compute buffers, and the rest of the app.
The bank is calculated for the current device and memory state.
Models that fit normally keep the original resident GGUF path.
03
Route
Stream only the experts the router selects.
Bank hits proceed immediately. Missing experts are read asynchronously from local storage, verified, and made visible to inference only after validation succeeds.
Related reads can be combined to reduce I/O overhead.
Prefetching and hot-expert protection improve reuse without unbounded memory growth.
04
Execute
Run through the Apple Silicon engine.
Overfit extends Noema’s llama.cpp and Metal runtime with paged MoE scheduling, fused routed reductions, and expert-major prompt processing.
Long prompts process experts in bounded waves.
Token generation reuses experts already in the bank whenever possible.
Measured on your device
Launch is not the benchmark.
The Canary Test measures the exact package, Apple device, storage volume, available memory, native runtime, and app build. When any of them changes, the result expires.
Observed signals
01Storage bandwidth
02Time to first token
03Generation speed
04Latency percentiles
05Long stalls
06Bank hit rate
07Page misses
08Peak memory
Honest outcome
Paged — interactive
Paged — slow
Too slow on this device
Relay recommended
Not supported
Faster follow-up conversations
Resume the prefix. Process only what changed.
Cold prompt processing can sweep broadly through the expert package. After a successful conversation, Noema can save a local prompt-state checkpoint and restore an unchanged system prompt and conversation prefix on a matching future launch.
Checkpoints are tied to the exact model and configuration. A cache failure never blocks the model; Noema falls back to a cold prompt.
Private by design
The model, conversation, and inference stay on your device.
Weights remain on local storage.
Prompts and responses remain on device.
No cloud inference service is required.
Expert payloads are excluded from device backups.
Saved prompt states remain local and configuration-bound.
Relay may be recommended for an unsuitable model, but using it remains a separate choice.
Designed to fail safely
Corrupt or incomplete expert data fails closed.
01Strict package geometry and bounds validation
02File fingerprints and per-expert checksums
03Independent native validation at launch
04Bounded I/O queues and staging memory
05Automatic prefetch reduction under pressure
06Thermal and memory-pressure monitoring
07Early termination before an unsafe memory condition
08Preservation of any partial answer already generated
The honest tradeoff
Storage is not RAM.
A smaller model that fits completely in memory will usually start faster, generate faster, and use less energy. Overfit is for cases where access to a larger model’s capabilities matters more than minimum latency.
01Storage throughput02Available memory03Model architecture04Quantization05Experts per token06Prompt length07Bank hit rate08Thermal state09Speculative decoding
Current availability
Deliberately restricted.
The current runtime supports paged packages for Qwen 3 MoE, Qwen 3.5 MoE, Qwen 3.6 MoE, and Gemma 4 MoE. It is not a generic mechanism for dense models or arbitrary GGUF architectures.
Package creation is currently available on macOS. Conservative context limits and some auxiliary or multimodal workflows may continue to use the normal resident runtime.