👥 01
Real testers
A curated pool of verified everyday testers — diverse devices, locations and generations, not the same power-users who already know your app.
Public Beta · Free during launch
Shipped 80% with AI? We bring real testers for the last 20%.
Crowd testing for AI-built apps — real human testers in 48 hours.
Built your app with Cursor, Claude Code or Lovable — Flutter, React or Next.js?
Outside of you, nobody has really used your app yet. Friends install once, tap around, then ghost. TesterPayKit puts real everyday people on your app, Flutter or web, and you only pay for validated sessions: scored, deduplicated, checked against click-farming.
How it works ↓ Drop-in SDK · Flutter + Web (React, Next.js, Astro)
Pay only for validated sessions
Privacy-first · GDPR-aligned
Feedback in 24–48 hours
Google Play wants 12 testers for 14 days? We organise them →
Who it's for
Built for both sides of the testing market
TesterPayKit connects the people who need testing done with the people who want flexible micro-income. We start in DACH + EU and grow from there.
For builders
Indie · Solo · Vibe-Coding devs
You built it with Cursor, Claude Code or Lovable — in Flutter, React or Next.js. You're alone or in a tiny team. You don't have a QA budget but you need real humans to break your app before launch.
- Drop-in SDK for Flutter & web (React, Next.js, Astro)
- Pay only for validated sessions, no retainer
- 10 free sessions during beta
For SMEs
SMEs with their own app
Your app is in production but you lack an in-house QA team. You need diverse, real-user feedback from people who aren't already power-users. Without paying agency rates.
- Real testers on real devices in your target markets
- Validation queue + payout pipeline included
- EU-hosted, GDPR-aligned, German support
For agencies
Digital agencies + studios
You ship apps for clients. You need repeatable, reportable validation that fits into your delivery process, and that you can resell or white-label.
- Multi-project console, per-client separation
- Exportable PDF + CSV reports
- API + webhooks for your own pipeline
For testers
Earn money testing apps
Students, retirees, retail- and gastronomy workers, parents on the school run: anyone with a phone and a few free minutes. Test apps for indie developers and earn flexible income.
- Short tasks: 10 to 40 minutes
- Transparent payout shown before you accept
- Privacy-first: you choose what to attach
Why developers choose TesterPayKit
Everything you need to test your app with real users, without the enterprise price tag.
📱 02
Real devices
Test on actual phones and tablets, not emulators. Feedback from the devices your users actually own.
⚡ 03
Fast turnaround
Detailed bug reports and structured feedback in 24–48 hours. Ship with confidence.
🔒 04
Privacy-first
GDPR-aligned by default. No PII or raw input content leaves the device unless a tester explicitly attaches it.
✅ 05
Validated sessions
You pay only for sessions that pass: scored for quality, deduplicated, with intentional control-bugs planted to catch click-farmers. No retainer, no minimum.
💰 06
Affordable
Platform-access subscription. You set tester payouts. A transparent transaction fee keeps the platform running.
📊 07
Structured reports
Bug reports with screenshots, widget-level annotations, device info and reproduction steps.
How it works
Get started in minutes. No complex setup, no long-term commitments.
- 01
Drop in the SDK
Add the SDK to your app — Flutter or web (React, Next.js, Astro) — and ship a build. Set up takes minutes.
- 02
Define what to test
Create a project, set focus areas, optionally plant intentional bugs as quality signals, set your payout rules.
- 03
Testers do their job
Real testers in our DACH + EU pool install your app on their real devices and follow your scenarios.
- 04
Review + pay
Validate submissions in the queue, approve payouts in one click. Iterate, ship, repeat.
This is not a mockup. This is what real testing looks like here.
Screenshots from our own local instance, as of June 2026.
Why we exist
We built TesterPayKit for ourselves first
We're a studio that ships a lot of our own apps — and every one needs real testing before launch. Pro testers are expensive and rare; friends test once and ghost. So we built the tool we needed ourselves. Being customer number one isn't a tagline — it's where the product came from.
Built from real need
Dogfooded on our own apps before we opened it up. If it does not work for us, it does not ship.
Fair to both sides
Developers get affordable real-human testing. Everyday people get a fair way to earn flexible extra income — short tasks, transparent payout.
Honest before launch
No invented numbers, no fake social proof. What is beta, we call beta. Pricing stays placeholder until it is final.
Under the hood
Easy to use. Not easy to build.
From the outside, TesterPayKit looks like a small SDK and a dashboard. Underneath, seven systems have to interlock — built, broken and rebuilt over nine months of daily dogfooding. That depth is the product.
Capture SDKs
Shake-to-report, session capture, breadcrumbs and an offline-safe outbox — native in Flutter, TypeScript/Expo and Swift, all held to a single wire contract.
Evidence pipeline
Every bug arrives with its session: timeline, steps, device context, screenshots, screen recording. Testers do not write essays. Developers do not guess.
Marketplace engine
Job postings, applications, tester validation and reputation — the matching layer between apps that need testing and people who test.
Payout engine
Server-side payout calculation with per-project rules. Real money to real people — including the compliance homework that comes with it.
Two-sided console
One web console, two worlds: developers manage projects, jobs and reports; testers browse, apply and earn.
Agent-native tooling
A CLI and an MCP server feed bugs and sessions straight to AI coding agents — your agent reads the report and ships the fix in the same loop.
API backbone
110+ endpoints carrying auth, roles, magic links, notifications and payouts — the part nobody notices until it breaks.
By the numbers
- 9 months of building
- 110+ API endpoints
- 3 SDKs, one contract
- 1,000+ automated tests
Could someone copy it? Sure — after they rebuild all seven. We will keep shipping in the meantime.
How TesterPayKit compares
We build for indie developers shipping with AI tools. Compared against the two crowd-testing alternatives we get asked about most.
| TesterPayKit | UserTesting | TestFi | |
|---|---|---|---|
| Starting price | €0/month · pay-per-tester | $49–$150 / session | $1.99–$3.99 / tester |
| SDK integration | Optional (for deep telemetry) | None | None |
| AI-built app focus | Yes — Cursor, Claude Code, Lovable, Flutter | Generic | Generic |
| Auto-captured repro steps | Yes (breadcrumbs + crash context) | No | No |
| Paid testers from pool | Yes — DACH focus | Yes (US-centric) | Yes (12+ countries) |
| Hosting | EU (Hetzner) · GDPR-compliant | US | Unknown |
| Agentic fix loop (Claude Code) | Yes — tpk CLI + plugin | No | No |
Sources: vendor pricing pages (as of 2026-05). Feature claims from each vendor’s own marketing site at time of comparison.
Platform access + transparent tester pay
A monthly platform fee gives you access. You set tester payouts. A small transaction fee on payouts keeps the platform running.
Placeholder pricing. The numbers below are illustrative only. We are still setting our final tariffs. Use them as a mock-up to understand the plan structure, not as a commitment. Final pricing will be announced at launch.
Your costs:
Platform subscription
+ Tester payouts (you set the rate)
+ Transaction fee on payouts
Free
€0
Try TesterPayKit with your first tests
- 5 test sessions/month
- 1 project
- 1 team member
- Basic bug reports
- 7-day report retention
- Community support
- 15 % tester payout fee
Indie
€29 /month
For solo devs and small apps
- 50 test sessions/month
- 3 projects
- 2 team members
- Detailed bug reports
- Screenshots & recordings
- 90-day retention
- Email support
- 10 % tester payout fee
- GitHub integration
- Custom payout rules
Most popular
Team
€99 /month
For growing teams with regular testing
- 200 test sessions/month
- 10 projects
- 10 team members
- Full annotated reports
- API access & webhooks
- 1-year retention
- Priority support
- 8 % tester payout fee
- Intentional bug checks
- Export & CSV reports
Business
€299 /month
For agencies and larger QA teams
- 1,000 test sessions/month
- Unlimited projects
- 50 team members
- Priority tester pool
- SSO (SAML/OIDC)
- Unlimited retention
- Dedicated support
- 5 % tester payout fee
- Full API & reporting
Enterprise
Custom
For organizations with advanced needs
- Unlimited sessions
- Unlimited everything
- Dedicated project manager
- Custom integrations
- 3–5 % tester payout fee
- Invoice billing
- On-premise option
- Priority tester pool
🚀
50 % startup discount
First year, for companies under 2 years and < €1M funding.
💚
30 % non-profit discount
For registered non-profit organizations.
🧪
Free during the beta
No one pays anything before final pricing is published.
Frequently asked questions
How much does crowd testing cost compared to UserTesting? +
TesterPayKit starts at €0/month — you only pay testers who actually run your app. UserTesting charges $49–$150 per session. For indie apps with a few test cycles per month, TesterPayKit is multiple times cheaper.
Do I need to install an SDK to use TesterPayKit? +
No. The SDK is optional and gives deeper telemetry (breadcrumbs, crash reports, screen recordings), but you can run tester campaigns and collect feedback without it.
How do testers get paid? +
Testers receive transparent per-task payouts, released after your approval. Rates run through the TesterPayKit platform; testers see what they will earn before they start a task.
Can I crowd-test a Flutter app without my own user base? +
Yes — that’s the whole point. TesterPayKit brings real people (students, retail workers, retirees) as testers for apps that do not yet have an audience.
What is crowd testing for indie developers? +
Crowd testing is a model where a distributed pool of real users tests an app on real devices, instead of in-house QA only. For indie developers, that means realistic feedback without owning a user base.
How long does a test campaign take? +
Typical campaigns deliver first feedback within 24–48 hours. More complex multi-session tests run for 5–7 days.
Is TesterPayKit GDPR-compliant? +
Yes. TesterPayKit is EU-hosted (Hetzner), and we avoid storing tester clear-text data or app content server-side beyond what testing requires. Privacy + DPA are part of the standard setup.
Build with AI. Ship with humans.
The first 80 % is AI. The last 20 % — the bugs real thumbs find — is us. Start free, no card required.
No credit card required · Free plan available · Cancel anytime