👥 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.
Who's it for?
One platform. Ten ways in.
Pick your role — we explain TesterPayKit in your language.
Build Market Earn Invest Discover
Tap your role
Developers Indie & AI-built apps Freelancers Ship client apps with proof Agencies Repeatable client QA Businesses Real-user validation Open Source Free for OSS projects Influencers Launch apps to your audience Marketing Promote apps that actually work Testers Earn money testing apps Investors The distribution thesis Users Discover real, tested apps
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
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.
Two ways to test. Both honest.
Bring your own testers and pay only for the toolkit — or use our paid pool and pay per run. No seat quotas, no hidden payout cuts.
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.
Bring your own testers
Toolkit
You already have people — staff, community, a Discord. Pay only for the platform that tracks, proves, and routes the testing. Nobody is paid through us, so there is no payout cut.
Free / OSS
€0
Bring your own testers — staff, community, friends.
- Your own testers, unlimited
- 1 project
- Full console + bug reports
- Session evidence (screens, time)
- 7-day retention
- Free forever for OSS maintainers
Most popular
Team
€49 /mo
For companies testing with their own people.
- Everything in Free
- Up to 10 projects
- SDK + automatic bug capture
- Fix loop into Claude Code / Cursor (MCP)
- Screen recordings + structured reports
- 1-year retention · email support
Business
€199 /mo
For agencies and larger in-house QA.
- Everything in Team
- Unlimited projects + seats
- SSO (SAML/OIDC)
- API access & webhooks
- White-label / exportable reports
- Dedicated support · invoice billing
We bring the testers
Managed pool
No testers of your own? We recruit and pay real everyday testers. You pay per test run — their time plus our margin, never less than we pay them.
Gate
from €299 / run
Clear the Google Play 12-testers-for-14-days gate.
- 12+ real, paid testers
- Opted in for the full 14 days
- Daily opted-in count
- Pool replacements if someone drops
- Status tracking in your console
Most popular
Evidence
from €499 / run
Know testing really happened — not hope it did.
- Everything in Gate
- Validated sessions: screens, time, what was exercised
- Screenshots
- Short human-readable test report
Bug Hunt
from €1,199 / run
Ship with a fix list, not a shrug.
- Everything in Evidence
- Structured bug reports + repro steps + device data
- UX-friction notes + launch-readiness checklist
- Pull bugs into Claude Code / Cursor via SDK + MCP
🚀
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