The free tape stops at the sign up page. Paying keeps it running.
A free scan checks that your app loads. It never fills in a form, so it can't tell you if anyone can sign up or pay. Here's the whole tape I recorded for brewnyc.app on its audit, with the free part marked off.
Two ways to pay. The difference is how often the tape runs.
Same tape either way. Both prices are for one app, iPhone and desktop.
I record the whole tape once, like the one above. You get the report with every frame, the video, console and network, and a fix prompt for each issue. When you've fixed things, I record it again once, any time in the next 14 days.
A new tape every night at 02:00, and another after every deploy. I put tonight's next to last night's and only email you when something changes: a new failure, or something that's started working again. Re-tests are unlimited.
Bought the audit first? I take the £249 off your monthly bill if you switch within 30 days. Not sure which flows matter? Describe them and I'll reply within a day.
What's on each tape
| Free scan | Audit, £249 | Nightly, £149 a month | |
|---|---|---|---|
| Pages load, links, console errors, mobile layout, speed | Yes | Yes | Yes |
| Sign up, onboarding, paywall and the main thing your app does | No, stops at sign up | Once | Every night and after every deploy |
| Video, console and network for each frame | One frame of evidence | Yes | Yes |
| Your own tests, written in English | No | 3 | 15 |
| Re-test after you've fixed things | Run a new scan | 1, within 14 days | Unlimited |
| Tonight next to last night, and an email when it changes | No | No | Yes |
| Pages crawled | 10 | 50 | 50 |
Questions people ask me
Do you create real accounts on my app?
Yes, on paid tapes. Each run signs up with a fresh address at inbox.didibreak.dev, so the accounts are easy to find and delete. If you've got a staging site, point me at that instead. There's a cleanup webhook if you'd rather they disappeared on their own.
Will you charge a real card?
No. On staging I use Stripe test mode and go all the way through. On production I stop on the last screen before the charge and check the button is there and works up to that point.
How does the after-deploy run work?
You add one webhook in Vercel, Netlify, Railway or GitHub Actions. When a deploy finishes I record a new tape against it, usually within two minutes. If a deploy breaks sign up or payment I email you straight away, I don't wait for the night.
Am I going to get an email every night?
No. Only when something changes. If a check fails once and passes when I retry it, I mark it unconfirmed and don't email you unless it fails again the next night. Most weeks you'll hear from me once, in the Monday summary.
My app has a CAPTCHA or two-factor login. Does that work?
Give me a bypass header or a test token for the test accounts and it's fine. If I get blocked anyway, the report marks it as blocked, so you don't go looking for a bug that isn't there.
Do I have to write tests?
No. On the first run I find sign up, log in, the paywall and checkout myself and ask you to confirm them. If you want something specific checked, like saving a cafe, you write it in plain English and I turn it into steps. You get 3 of those on the audit and 15 on nightly.
Why pounds?
I'm in London. Stripe converts for you. UK businesses pay VAT on top.
Can I stop?
Yes, from billing, any time. Your tapes stay readable for 30 days after you cancel.