Comment on page
A trial makes it possible to fully test BugBug’s capabilities without any costs involved. After 14 days, the account will remain open, but certain functionalities will be limited.
You can pay with a credit card. The secure payment is provided by Stripe system.
We've put a lot of effort into securing BugBug. Most of our team have experience in security or compliance. Even the CEO has a security background.
- We built BugBug with the best software practices (SSL, encrypted passwords).
- We do security audits yearly, with a top security researcher (who is a shareholder of BugBug, by the way).
- BugBug uses DigitalOcean cloud infrastructure based on Kubernetes, giving us extra secure containerization.
- Our servers are located in London.
- Tests in the cloud are run separately from each other, which significantly reduces the risks.
- We have an internal policy with different roles for our employees. Only the IT department has access to the customers' data.
Yes, any time. When you buy a higher plan, it is activated instantly. If you downgrade, you will wait until the previous period is finished.
You can change your plan anytime you want in your Subscription settings.
You can cancel your plan anytime (switch to the Free Plan).
At the moment, BugBug is available exclusively as a cloud Software as a Service (SaaS). Therefore, it is not possible to install it on-premises on the LAN. However, in the future, we are planning to launch this service. If you are interested, contact us at [email protected].
Not at the moment. However, we are seriously considering adding this in the future.
At the moment we support only Chromium-based browsers.We don't support Firefox, Safari or Edge browser. This is a conscious trade-off. We are dedicated to providing the best-in-class experience of creating and running tests, and Chrome is the most popular browser with the best API to achieve that.
The data used in the test runs are recorded in our database and stored in the DigitalOcean cloud. Access to the database is provided exclusively as part of the BugBug application infrastructure. We make all the effort to prevent data leaks.
The easiest way is to have 2 different projects: one for desktop tests and one for mobile tests. Set a different window width per project in its project settings. We recommend creating all the important desktop tests, then duplicating the project and adapting the tests to the mobile version via re-recording test steps.
BugBug is explicitly designed for testing web applications. Currently, we do not support testing native mobile apps or desktop apps.