Pricing

Pricing that tracks what you run.

Credits, not seats. You pay for the browsers, emulators, and devices your tests actually use. Start with $10 in credits, no card.

Free
$0
For kicking the tires.
  • $10 in credits (1,000 credits), no card required
  • 14-day window
  • Cloud browsers, emulators, and Device Farm access
  • MCP server and 65 tools
  • Community support
Start free
Pay-as-you-go
$0.01= 1 credit
For light or bursty workloads.
  • Buy credits, spend them on anything Kifas runs
  • No monthly commitment
  • The autonomous loop and self-healing
  • Email support
Buy credits
Pro
$199/mo
For teams shipping real features.
  • Everything in Pay-as-you-go
  • Monthly credit allowance at the best per-credit rate
  • GitHub-connected autonomous loop
  • Self-healing with configurable break thresholds
  • Auth Catalog, vibe testing, hybrid engine
  • Priority email support
Choose Pro
Custom
Let's talk
For teams testing on real devices at scale.
~40% less
than teams pay BrowserStack for real devices*
  • Everything in Pro
  • Dedicated real devices in our Device Farm
  • Highest concurrency
  • SSO, audit logs and a DPA
  • Premium support and onboarding
Talk to us
Switching from BrowserStack?

Real devices for about 40% less.

Teams moving from BrowserStack typically save around 40%. Based on quotes we've given to teams currently on BrowserStack. Your saving depends on your devices and concurrency; send us your quote and we'll show you the number.

How credits work

One currency for everything Kifas runs.

A credit is a unit of compute, worth about a penny. Spawning a browser, running a flow, holding a device open: each draws credits at a published rate. You are never billed per seat, so adding teammates costs nothing on its own. Idle costs nothing. You spend when tests run.

2 cr
Cloud browser
per minute
5 cr
Mobile emulator
per minute
22 cr
Device Farm
real devices · per minute
1-12 cr
AI step
vibe · explore

Real devices cost more because they are real hardware, held exclusively for your run. Emulators cover most flows at 5 credits/min. Reach for the Device Farm when you need the real thing: camera, biometrics, GPU, or hardware quirks.

Cloud browser per minute · Chromium, Firefox2 cr
Mobile emulator per minute · Android5 cr
Device Farm per minute · real physical devices22 cr
AI step: Lite vibe / explore1 cr
AI step: Pro vibe / explore4 cr
AI step: Premium vibe / explore12 cr
Held state & long sessions drawn while they are openmetered
Self-heal & exploration runs draw like any other runmetered
Calculator

Estimate before you commit.

Set a few numbers and watch the monthly estimate update.

Estimated monthly credits
94,080 credits / month
at ~$0.01 / credit
$941/mo
9,600 runs/mo · 19,200 device-minutes · 10% on real devices
Self-heal usually lowers this over time by killing redundant retries, and emulators are the cheaper default for most mobile flows.

Full feature comparison

Free
Pay-as-you-go
Pro
Custom
Getting started
Free credits to start
$10
$10
$10
$10
Card required to start
✕
✕
✕
✕
Resources
Cloud browsers (2 cr/min)
✓
✓
✓
✓
Mobile emulators (5 cr/min)
✓
✓
✓
✓
Device Farm, real devices (22 cr/min)
✓
✓
✓
✓
MCP server and 73 tools
✓
✓
✓
✓
Cold start p50 under 3s
✓
✓
✓
✓
The autonomous loop
GitHub-connected loop
✕
✓
✓
✓
Self-healing tests
✕
✓
✓
✓
Configurable break threshold
✕
✓
✓
✓
Real-bug routing (PR comment, CI break, webhook)
✕
partial
✓
✓
Auth Catalog
✓
✓
✓
✓
Vibe testing
✓
✓
✓
✓
Hybrid engine and Playwright export
✓
✓
✓
✓
Named state handles
✓
✓
✓
✓
Scale & governance
Concurrency
Low
Standard
High
Highest
Dedicated real devices
✕
✕
✕
✓
SSO and audit logs
✕
✕
✕
✓
DPA
✕
on request
on request
✓
Support
Community
Email
Priority email
Premium

FAQ

Yes. $10 in credits, no card, 14 days. When the credits or the window run out, nothing auto-charges. You decide whether to add a payment method.
Because they are real hardware, leased exclusively for your run. Emulators handle most flows at 5 credits/min. The Device Farm is there for the things only real hardware can do: camera, biometrics, GPU behavior, and hardware-specific bugs.
No. Pricing is credit-based, so adding teammates does not add cost. You pay for what your tests run.
About a penny. Per-action rates are published above and shown live on your usage dashboard.
No. Self-heal runs draw credits like any other run, and they usually lower your total spend by cutting pointless retries and the engineer-hours that follow them.
Always. Everything compiles to standard Playwright, and you can export and run it in your own CI whenever you like.
Dedicated real devices in our Device Farm, the highest concurrency, SSO, audit logs, a DPA, and premium support with onboarding.

Try it on your own repo.

$10 in credits, no card, 14 days. That is enough to connect GitHub, get suggested tests, and watch a real self-heal happen.

Start freeGet a quote