Atlas

What should your team build?

Tell PA in plain words. A team of AI engineers designs, builds, tests and reviews it on your own Claude plan, and it goes live when you say so.

PA · in the Atlas app on your Mac
Copied. PA lives in the Atlas app. Download it, sign in with your email, and paste this to PA.Download for Mac

For Macs with Apple silicon · one project free · needs your own Claude Pro or Max plan

Every engineer, live.

The Network screen in Atlas: each engineer on its own piece of work, more hands where the work allows, and the programs on their own rail, with no AI.

Redrawn from the Network screen in the app, with an example project.

Watch it work.

What the team does after you press send.

Studio bookings
A booking page for my studio. Classes and private sessions, with an email reminder the day before.
PAI’ll get the team on it. One question first: who can book private sessions?
AnyoneMembers only
PAThe plan and the screens are approved, and the tests are written and failing, so building has started.
PAEvery case passes and the review says releasable. The backup is proven. It goes live when you say so.
  1. PAAsks what it needs towith buttons to answeranswered
  2. ArchitectureThe planwritten up, every diagram checkedapproved
  3. DesignThe screenssigned off before any buildingsigned off
  4. TestingTests written firstthey fail until the work existsfailing, as they should
  5. Back endBookings and remindersin its own copy of the codebuilt
  6. Front endThe booking screenswaited for the API they callbuilt
  7. TestingEvery case runeach with its screenshotspassed
  8. Code reviewThe build reviewedwith a security look at sign-inreleasable
  9. ReleaseReady to go livedata backed up, the backup proven by restoring itready
  10. YouGo live?never decided for youwaiting for youNot yetGo live
Your turn. Tell PA what you want built.Download for Mac

An example run, sped up. A real one takes as long as the work does.

The engine moves the car. Not the wipers.

A car doesn’t run its engine to move the wiper blades; a small motor does that. Atlas works the same way: Claude does the work that needs judgement, and programs do the jobs that repeat, with no AI, so they don’t burn your Claude plan.

Plan the architecture next job

Claude needs judgement

On the model and effort chosen for the kind of task.

  • Plan the architecturetop model
  • Design the booking screenstop model
  • Describe a test caseHaiku

Programs no AI · no tokens

Checks AI wrote once, run by themselves on every change.

  • Run the tests and land the worktest runner
  • Re-check a saved screenscreen checker
  • Scan what changed for committed keyssecurity scan
0 tokensfor a program run: no model call, so none of your Claude plan.
31k → 11ktokens, roughly, in a builder’s first turn, since each engineer loads only the tools its role uses.
3 timesthe same problem sent back in 14 days, and Atlas has a check written for it: from then on a program catches it, not the AI.

Start on your Mac. Carry on without it.

Build on your Mac for free. When the work should go on overnight or while you’re away, move the project in one click to a server in your own DigitalOcean account, and close the laptop. The team keeps working.

Your Mac

  • One project free, for ever
  • One window, one tab per project
  • Pause a project and the team is saved; resume it and the engineers who were working come back

Your own server

  • The team keeps working with the laptop closed
  • Sleeps after 30 quiet minutes, and stays awake while there is work it can move without you
  • Wakes from the app, or from a Start button in Slack
  • In your own DigitalOcean account: you choose how large and fast it is

Work goes on while you’re away

Overnight, on a flight, over the weekend: the engineers keep building and testing, and PA reports back when you’re here.

Reach it from anywhere

Talk to PA in Slack. A project that has gone to sleep wakes from a Start button there.

Your account, a flat fee

The server and its data are in your own account. On a server the Atlas licence is a flat $50 a month per project, whatever size of server you pick, with the first 30 days free for one; the software you build runs live at no charge.

What comes back to you.

Not just code: the proof that it works, and nothing live until you say so.

One project free on your Mac, for ever.

Each more project in development at the same time is $50 a month. You also need your own Claude Pro or Max plan, billed by Anthropic.