Pricing

What it costs.

Free today. Prices for when paid care begins.

Atrytone is free, by invitation, right now.

During early access, an invited app gets everything in Care, free. No card is asked for and nothing is charged while we prove this works end to end on real apps. The prices below are only so you know what is coming — never a quiet switch.

Open to everyone from this Sunday, 1 November 2026.

Free check

Free

One app, read for free — the nightly check only, no fix.

  • Checked after every change, and every night: keys in the code, open tables, parts with a known flaw
  • Press “Check now” any time
  • No AI key needed: the check runs no AI
  • No fix opens, and nothing merges
Request early access
Recommended

Care

$29app / month

One app cared for: checked every night, fixed on your yes.

  • Checked after every change, and every night
  • Every fix needs your yes: one at a time, or a standing yes you set
  • A record of every act, kept: each receipt downloads any time, the whole record on request
Request early access

Agency

$19app / month

from 10 apps

Looking after a handful of apps, or more.

  • Everything Care does, for every app
  • This price for every app, once you look after 10 or more
  • One workspace for all of them
Request early access

Per app, in USD.

Your AI key pays the model.

Every model call runs on your own key, billed straight to you. We never see that bill, never touch it, and never add a markup. The prices above are for Atrytone only.

Merged, not deployed.

Atrytone merges the fix into your GitHub repository on your yes. It does not deploy: if your host publishes from GitHub, the merge goes live there.

Uploaded code: the fix goes into Atrytone's copy of your code; press Download the code on the app's page to take it.

What works today

As of 29 October 2026.

  • Checks, every night and whenever you press Check now

    keys left in your code; database tables your code lets strangers read, worked out from your Supabase migrations or Firestore rules; and parts with a published flaw, in JavaScript apps (npm, pnpm, yarn, bun) and Python apps (requirements.txt). Poetry, uv, Pipenv, Rust, Go, PHP and Ruby lockfiles are not read yet — the check says so when it meets one. Those three are the first; the map on our front page names every area the check reads from your code today.

  • Fixes

    made on a copy, tested with your app's own tests, and offered to you on GitHub. On 29 October 2026, 8 fix jobs had been asked for from the check's results, all in our own workspace and none in a customer's. An app with no tests can be fixed in two ways. You can say you check each change yourself, and its receipt then says no tests ran. Or, for a JavaScript app, the fix writes the app's first test: one that fails before the fix and passes after. Neither way has run on a customer's app yet. Other apps with no tests cannot be fixed yet.

  • Build and Look

    Own apps only: 56 build jobs asked for in words, 13 finished, and 3 look jobs asked for, none delivered. Read on 29 October 2026: every one in our own workspace and none in a customer's.

  • Your code

    Connect your app from GitHub, or upload its code.

  • Your AI

    Claude (Anthropic) keys run the fix jobs, on your own key. On 4 October 2026, our first two fix jobs, on our own test app, cost $3.41 and $3.43, plan included: two jobs, not an average. Neither fixed its flaw: one stopped on a failed check and was cancelled, the other merged a change that left the flaw standing. Every fix job so far has run on Claude. OpenAI and Gemini keys connect today; no fix job has run on them yet.

  • How far we are

    Our own bar before we call fix jobs reliable: five in a row, on apps we did not hand-pick, each reaching its goal with nobody stepping in. On 29 October 2026 we were at 0 of 5.

  • Who it is not for

    apps whose main job is payroll, payments or health, and any other app where one wrong change could seriously hurt someone; that is our choice of where to start while we prove this works, not a legal claim. It is about fixing, not reading: for an app that takes payments through Stripe, Lemon Squeezy or Paddle, the check reads the payment code and the Payments area of our map shows what it found, and a reading is not a promise that your payments are safe.

Questions

Why not charge per fix?

Because then you'd think twice before saying yes — and the point of the standing yes, which lets part updates go ahead on their own (each app's Money and rules page), is that you stop having to think about small, safe fixes at all. One price covers the app, however many fixes it needs.

Can I export everything?

Each job’s receipt downloads from its own line on the Record page, any time, and checks itself. For your whole workspace — every row and every file — write to us in Settings, and a person sends it to you by hand.

Do I need to connect a GitHub repository?

Connect your app from GitHub, or upload its code. What the App can and cannot touch is on our Security page.

Have an invitation, or want one?

Request early accessHave an invitation? Sign in