Is the 30-day pilot really free? What's the catch?
Free, full-coverage, no credit card. The catch is honest and simple: we only run 10 founding-cohort pilots in 2026 because each one gets a dedicated engineer, and we expect a good share of pilots to convert because the morning report sells itself. If it doesn't for you, walk away and keep the tests.
What do you need from us to start?
Three things in the kickoff week: read access to your repo (via the GitHub/GitLab app), a staging environment with a couple of synthetic test accounts, and a Slack channel invite. Most teams spend under two hours total on onboarding.
Do I have to talk to anyone before starting?
No. Pricing is public, the pilot is self-serve, and the sample report is on the site. If you want to talk to an engineer (not sales), there's an optional 15-minute call — but nothing is gated behind it.
What does week 1 look like?
Day 1: kickoff and access setup. Days 2–4: we map your critical user journeys and generate the first suite. Day 5: suite goes live in CI. Day 6: your first 9am morning report lands in Slack. The full breakdown is on the How It Works page.
Will my price change mid-contract?
No. Flat monthly fee for tests under management. The only thing that changes your invoice is you: adding tests beyond your plan (₹150/test/month) or adding the Performance or Security add-ons. Everything costs what the page says.
Can I cancel anytime?
Yes — cancel anytime, effective at the end of the current billing month. No termination fees, no clawbacks. Annual plans can be cancelled with the unused months refunded pro-rata minus the 15% annual discount you received.
What happens to the tests if I leave?
Nothing — they're already yours. Every test is committed to your repo from day one and runs in your CI without any QAShift dependency. Leaving costs you the verification service, not the asset.
Why are Performance and Security add-ons instead of included?
To keep the base price honest for early-stage teams that don't need k6 load tests yet. Both add-ons have published prices (₹15,000 and ₹20,000/month) — they're modular, not hidden.
If AI writes the tests, what are the humans for?
Verification. AI generates and maintains the suite; a named engineer reviews every generated test before it merges and re-runs every failure before it reaches your report. You never triage flaky-test noise — that's the core of the product.
What if a test breaks because the UI changed, not because of a bug?
Self-healing selectors handle most UI drift automatically. When intent actually changes, your engineer updates the test the same day — that maintenance is included in the flat fee, not billed as change requests.
Which stacks and platforms do you cover?
Web (Chrome, Firefox, Safari), mobile web, and native iOS/Android via Appium on Growth and above. API testing covers REST, GraphQL, and gRPC. If your stack is unusual, email us before starting the pilot and we'll tell you honestly whether we're a fit.
How do bugs reach my team?
Auto-filed into Jira or Linear with repro steps, video, trace, and the suspect commit — before the 9am report. The report links to the tickets, so standup starts with everything already triaged.
Does my code leave my repository?
No. We work inside your repo via scoped app permissions — read on application code, write only on the test directory and CI config. No mirrors, no forks. Full details on the Security page.
Do you sign NDAs?
Yes, before we see anything — our mutual NDA template or yours. A DPA for GDPR / India DPDP is included with every plan.
Who at QAShift can see my code?
Two named people: your dedicated engineer and one backup, both identified in your onboarding doc. Access is SSO with hardware-key MFA and is logged.