From the team Field notes № 01

The frontier of intelligence, hardware, and the way forward.

A woman pushes a towering pile of reports, bills, notes, and a dog photo toward a tiny phone. A curious man crouches beside it, inspecting the silver mercury bubbles connecting the phone to a laptop, workstation, and distant servers.
Can it deal with this? Let’s find out.

Device capability unavailable. All local device levels are disabled.

SLIDA meter

First, AI can be frustrating. And a lot of fun. Try squeezing it onto a phone, and the Terminator scenarios quickly give way to a more immediate concern: can we get this thing to finish a sentence? It takes a surprising number of tricks to make a small model work reliably on an everyday device. There’s still a big gap between that experience and what frontier models can do with a data center behind them. Even measuring the gap is tricky.

While building SLIDA, I ran into a wonderfully awkward design problem. I love simple interfaces with a little magic: everything you need up front, easter eggs tucked away, and more to discover when you go looking. But I couldn’t find a simple way to answer a basic question: how capable is this software, right now, on the device in my hand?

With AI, the same app can feel like a very different machine depending on the hardware and models available to it. A familiar interface doesn’t tell you whether there’s a small local model or a roomful of computers doing the thinking.

That’s where the SLIDA meter comes in. By testing the tasks our software actually needs to do, we can give users a simple guide to where their current setup sits: from basic functionality to frontier capability. And we can keep updating that guide as hardware improves and we find ways to fit more intelligence into smaller, more everyday devices.

01 / KNOW YOUR REACH

Introducing SLIDA meter

The meter runs from small local setups to hosted frontier models. Hover or tap a stop to see example devices and approximate hardware specs. Local modes run on your device; Frontier uses an external provider you configure. The example below is interactive.

Color and shape can also help make the cost and risk of each option easier to see.

A little map of what’s possible

SLIDA meter

Interactive concept
Expanded overview

Studio

Space for more demanding work.

Approximate hardware · Studio

65W–300W draw, up to 128GB RAM

⌂ On-device · local processing
Desktop
Laptop
Mini PC

Illustrative device families · benchmark placement pending.

SLIDA meter
This level represents processing on your device.

The same meter is intended to describe expected capability within the attached platform.

Hardware approximation guide

Hardware approximation guide

ClassPower & memory envelope
Pocket5W–15W draw, 8GB–16GB mobile RAM
Everyday15W–65W draw, 16GB–32GB system RAM
Studio · selected65W–300W draw, up to 128GB RAM
Power300W–1500W draw, up to 192GB VRAM
FrontierMegawatt scale, petabytes of cluster memory

Approximate hardware envelopes, not capability thresholds. Frontier describes cluster scale.