Autify is another login. agent-qa is QA memory living inside your repo.

Yes, and the reason is structural rather than a feature count. Autify is a no-code AI test automation platform where scenarios are created and run inside the vendor's product, which means the asset you are building lives on their side of the line. agent-qa is a source-available QA agent with no paid tier, governed by FSL-1.1-ALv2: tests are plain-English YAML in your repository, runs execute on your laptop, in your CI, or from your coding agent, and every run writes back into memory committed beside the tests. The suite gets better at your app whether or not you renew anything.

Autify is priced on plan tiers shaped around scenarios and platform usage, so the bill tracks how much you test. agent-qa has no paid tier, no seats and no platform fee; FSL-1.1-ALv2 governs permitted use. You pay for the model tokens and infrastructure you already control, on the provider you choose, and the validated action cache takes roughly 60% of the tokens off a matched rerun. Adding coverage does not add a line item.

You are re-describing intent, not porting code, which is why this is far smaller than a normal test migration. Autify scenarios are recorded user journeys; write each journey's intent as an agent-qa YAML test and you gain code review, memory, and LLM choice in the same move. Run npx agent-qa init, write each critical flow as a plain-English YAML test, and let the runtime work out the selectors and the recovery. Most teams move a smoke suite in an afternoon, and there is nothing to un-pick later because the output is files in your own repository.

Yes, and from the same file. agent-qa runs end-to-end tests on web, Android and iOS with one natural-language format, one memory store and one evidence model, so a flow written once survives being pointed at another surface. Autify offers a mobile product line; agent-qa handles web and mobile in one harness with one authoring format and one memory store.

You write plain English in a YAML file, closer to a checklist than to code. If your team can write an Autify scenario description, it can write an agent-qa test; the difference is the file lands in git where reviews, agents, and history already work.