Know your app broke
before your users do.

No. You describe the flow in plain English and Klyk turns it into steps you can edit, reorder, or extend. There is nothing to install and no test framework to learn.

Minutes. Sign in, paste your app's URL, describe the first flow, and watch it run live.

You get an email right away. It links to the run report: full video, step screenshots, and the console and network errors pinned to the step that failed.

Each stored credential is envelope-encrypted with AWS KMS before it reaches the database and decrypted only in memory at the moment a run signs in. No screen or API ever returns a stored value, values are scrubbed from traces and logs, and no screenshot is taken on password steps.

Yes, both kinds: your app's own sign-in form, and staging sites behind the browser's built-in password prompt (HTTP auth). Store either per scenario and scheduled runs authenticate unattended. Credentials are encrypted at rest, scrubbed from traces and logs, and no screenshot is taken on password steps.

Klyk drives a real browser, so a run creates real page visits and real form submissions on whatever URL you give it. Point scheduled runs at a staging URL, or use test accounts and test data when you need to test production itself. You control the target and the schedule for every scenario.

One run is one execution of one scenario, up to 15 steps; typical scenarios are always exactly one. A banner and an email warn you from 80% of quota. At the line, runs pause unless you switch extra runs on, so nothing ever bills by surprise.

Not yet. A CLI for CI and cron is scheduled for development: it will map verdicts to exit codes and pipe reports into GitHub Actions. Scheduled runs inside Klyk cover daily checks today.

Yes, every plan starts with a 3-day trial. Pick a plan and your card is not charged until the trial ends; cancel from the billing portal before then and you pay nothing.