Cypress.io is an avid supporter of open source. We use and contribute to open source projects every day to make our products better, and believe it’s vital for supporting other developers and the ecosystem.
To support the community we provide the Open Source plan for projects to take advantage of our Dashboard service.
- Your team or organization is a non-commercial entity
- Source code is available in a public location with an OSI-approved license
Always free and open source. No restrictions or limitations.
Open Source Plan
- Test recordingsUnlimited
- Test parallelization
- Run grouping
Learn more about Cypress pricing
What's the difference between the Test Runner and the Dashboard Service?
The Cypress Test Runner is an open-source, downloadable application that facilitates running your tests in a browser. This is always free to use and is provided under the MIT licence. Our Dashboard Service is a web application that gives you insight into your tests run in Continuous Integration including video recording, screenshots, and logs. We offer a variety of plans for the Dashboard Service, including a free plan, an open source plan, and paid plans.
What counts as a test recording?
We consider each time the
it() function is called to be a single test. Only test runs configured to record to the Dashboard Service when running Cypress headlessly count toward your plan limit.
What's the difference between a public test recording and a private test recording?
During setup of the Dashboard Service, you can designate the project you are testing to 'private' or 'public'. Setting a project to 'private' means that only users you invite to your organization can see its recorded tests. A public project (OS project) means that anyone can see the tests’ recordings. Anyone who knows your project's ID will be able to see the recorded tests, screenshots, and videos for public projects. Any tests that you choose to record in a private project are counted as 'private test recordings'.
What's test parallelization?
Cypress can automatically balance your spec files and run your tests in parallel across available machines when run in Continuous Integration. This ensures that your tests run as fast as possible, with no need for manual configuration.
What's run grouping?
Run grouping helps you organize your tests. Cypress offers the ability to group separate `cypress run` tasks within the same run view. This is useful if you want to run the same group of tests across different environments, across several directories in a monorepo, and more. Read more about grouping in our docs.
Are there any limits on free, open source projects?
We love open source! The Cypress Test Runner is a free, open source application. The Dashboard Service is free to use for non-commercial open source, public projects and has no limitations on the number of public recorded tests per month. Check out our OSS plan.
Do I need a credit card to create an account?
No, you do not need a credit card to create an account. Once you set up a project in our Dashboard Service, you will be able to try it out under our free plan with no commitment.
What payment methods do you accept?
Cypress accepts all major credit cards for standard pricing plans. We accept invoice payments from customers on custom plans.
Can I change my plan?
Can I cancel my plan?
What happens if I go over my plan’s limits?
If you reach either the user or private test recording limits on your plan you will be prompted to upgrade your account. If you exceed your test recordings you will be contacted immediately.
What if I need a custom plan?
Contact us. We can customize any plan to help organizations of any size meet their needs.
What levels of support are included?
Community and public chat support are offered to every user of Cypress. Email support is available for paid plans. Priority support is available for customers on custom plans.
Have more questions? Contact us.
We have a roadmap packed with ongoing improvements. Cypress is getting better and better every day.
Our docs are super thorough and cover every API command, plus examples to help you and your team maintain quality tests.