After talking to a potential customer a few days ago, he mentioned that while they currently pays over $8k/mo for our competitor - they are worried about the uptime of our system. A concern I can definitly relate to.
No time wasted - build an extensive ongoing status check. π
Up time and reliability are so important for CI and companies that want to deliver.
Yesterday we released our more advanced monitoring system which tracks availability and health of browsers and android devices. Every couple of minutes, we actually touch a service to make sure its available.
Take a look for yourself at our new status page: https://t.co/JaKOa08R7I
Up time and reliability are so important for CI and companies that want to deliver.
Yesterday we released our more advanced monitoring system which tracks availability and health of browsers and android devices. Every couple of minutes, we actually touch a service to make sure its available.
Take a look for yourself at our new status page: https://t.co/JaKOa08R7I
@__alexlazar__ 15-20 mins, you said you tell them to look through every nook and cranny, so it seems a bit short for a full e2e suite. So you have 0 persistant tests? you just tell it to test and point it to the PR
@__alexlazar__ what about the speed? i found that if i just give an mcp a simple prompt, it takes so long to run. can't really run it before deployment without creating a new bottleneck
Time wasted figuring out what went wrong when a test fails in CI used to drive me crazy. So building self-healing into https://t.co/IAOdqjJnlK is still one of my favourite things we've done.
You set the threshold, the agent fixes stale tests - only fails when actually needed!!
Ngl "pay only for what you run" is one of MANY things I'm proud of with https://t.co/IAOdqjJnlK. It writes, runs, and self-heals your e2e tests on real browsers + devices - plus you only pay for the minutes your tests run + whole team free.
1k free credits, take it for a spin :)
Flaky tests are the bane of every engineer's existence. A test fails and we can't quickly tell if it's the code or the test..
Kifas uses our Smart Test Fallback that reads both and decides - auto-fixing the test or flagging a real bug depending on what YOU decide it handles.
Take QA automation off your to-do list.
Kifas connects to your repo and agents write and run them - on real browsers, emulators, and our Device Farm. Or vibe-test in plain language.
Pay only for what you run: $0, $50, $199. Not $249β$449/mo.
See it in action - 1k free credits
Flaky tests are the bane of every engineer's existence. A test fails and we can't quickly tell if it's the code or the test..
Kifas uses our Smart Test Fallback that reads both and decides - auto-fixing the test or flagging a real bug depending on what YOU decide it handles.
Automating tests is a real pain point. Login alone needs credentials, auth providers, session state, token refresh.
Kifas simplifies this with our Auth Catalog: a pre-built library of secure login flows, saved even for future tests. If you know the pain, here's the fix :)
Working with many companies, I saw QAs become a bottleneck as AI skyrocketed dev work w/o giving QAs the same edge.
So.. we built Kifas to provide a vibecoding tool that does for QA what Cursor/Claude Code did for devs. Those who know the app best can now own the automation!!