Sitebot learns how your website works by analyzing users' clicks.
It then automatically tests that your site keeps working as it should.
Test patterns are automatically created for the most important tasks on your website.
Sitebot continuously tests your website and alerts with an email when something goes wrong!
3 test patterns
5 API calls/day
60 min monitoring interval
10 test patterns
10 API calls/day
5-60 min monitoring interval
Unlimited test patterns
Unlimited API calls
I'm Hannu Jaakkola, the founder of sitebot.ai. As a web developer, I need to make sure the websites I'm developing always work.
I created Sitebot to help me and others build & maintain websites with more confidence.
Broken websites cost money. Don't make your users notify you of bugs!
Websites need to be tested periodically for errors. Sitebot saves your time by automating the testing process.
Sitebot tests your website with a real browser to catch every issue. It emails you screenshots and error messages to help you discover and fix bugs, regressions and other issues as soon as they appear.
It also tracks test running times and detects slowly loading pages.
You don't need to run anything yourself, Sitebot provides everything for you automatically.
Sitebot runs tests using a headless browser that's technically identical to a browser that your real users use.
Sitebot knows how to log in to most sites. You can provide test user credentials and Sitebot automatically logs in to your website.
You can run tests on multiple versions of the same website with webhooks or the API.
Sitebot can run tests by using webhooks, for example from GitHub, Gitlab or BitBucket. You can also call the API programmatically.
The snippet only collects clicks anonymously. No data will be shared with third parties. The script is tiny; you can view the source code here.
Depending on how your tests are set up, they may not catch every error. Your tests might require maintaining when you make changes to your website.
In the beta phase, Chrome is the only browser to run tests with because it's the most popular one. Running tests with Firefox and Internet Explorer are on the development roadmap.