The number at the bar, adjusted for what you ate.

Most training apps are a filing cabinet. You put numbers in and they hand the same numbers back. Atlas reads them and tells you what to load next — and it reads your food and your strength as one thing, because your body does.

Get an invite How the rule works

Pre-release. Being used daily by the person who wrote it.

Legs · 1 of 4

Hack Squat

Last 150 kg × 6 · Sat, 4d ago

150 kg

× 7 reps

Inside 5–8 — same bar, one more rep.

Session 1 — inside the range

You got 6 reps last time and the range is 5–8. There is room left, so the bar does not move — Atlas asks for one more rep instead.

A simulation of the real rule, not a video.

Four sessions, one rule, nothing to decide.

That is the real progression rule running above. Add reps until you reach the top of your range, then the weight goes up and you start again at the bottom. You never work out what to load; you answer whether you got it.

It never invents a number. No history for a lift? It asks what you lifted rather than guessing a starting weight.
Deloads round down. Two sessions under the bottom of your range and the bar comes off — to a weight you can actually load.
Your plates, your jump. Microplates move you 1.25 kg. It never suggests a weight you cannot build.

Three things that read the log back to you.

Recording is the easy half. These are the parts that turn a log into an instruction — and they are why a neighbouring tracker cannot copy this by adding a screen.

Progression

Decides the next set from your own history, in your own units, down to the plates you actually own.

Strength trend

Fits a line through your estimated one-rep max per muscle group. Gap weeks are left out rather than counted as zero.

Coach

Reads calorie balance, weight rate, strength trend and logging consistency together, and returns one recommendation.

exercises, across 29 muscle groups

food databases, searched at once

accounts, servers, or trackers

Both halves, one app.

Food tracking is not a bolt-on. It is the input the coach reads when it tells you whether a stalled lift is your programming or your deficit.

The Atlas workout screen: Hack Squat, 150 kg, times 7 reps, with the reason 'Inside 5 to 8, same bar, one more rep', and three buttons: Hit it, Log actual, Skip it. — The guided session. One decision per screen.

The Atlas food diary: 1,134 kcal remaining against a 2,193 target, with protein, carbs and fat bars and logged meals. — The diary — searched across three food databases.

The Atlas dashboard: a coach card reading 'Cut is on track, hold current calories', and today's Legs session with four exercises and a Start workout button. — Today — what the log says, and one thing to do about it.

Screens are the real app running against seeded data, not mockups.

What you should know before it ships.

Your data stays on your phone. No accounts, no backend, no servers. Nothing to breach, and nothing for anyone to sell.
Food search leaves the device, and only that. A search term or a scanned barcode goes to Open Food Facts, USDA FoodData Central and fatsecret. Nothing else does.
No advertising, no analytics, no trackers. Not a policy we could quietly reverse — there is no pipe for it to travel down.
Apple Health is optional. Read-only, used on the device, never transmitted. The app works without it.
It is not finished. No App Store listing, no TestFlight yet, and a rest timer is still on the list.

Five accents. Change this page with one.

The app ships all five, each a light and a dark pair that clears the contrast floor. This page wears the same palette — pick one.

Accent

Built for one lifter first.

Atlas is used daily by the person who wrote it, which is the only reason it says no to as much as it does. TestFlight opens to a small group first. Ask, and you are on the list.

Goes straight to Mark. No list, no sequence, no newsletter — what happens to it.