Flexible Pricing That Scales
with Your Team
See how widely acclaimed open-source projects use Foresight
Foresight never sees your secrets or source code
Full plan comparison
/month
/month
/month
/month
/month
/month
FAQ
A committer is a real developer who commits a code in the last 30 days into a repository watched by Foresight. We use GitHub's official API to fetch the committers. We omit bots from your committer list.
We automatically fetch the latest active committers by using GitHub API. However, we don't charge you without your knowledge. You can always adjust your committer limit. Whether there is a new committer added or you have less committer than your limit, you can always change your limit for the next billing period. Team admins will receive an email a few days before payment each month recapping what the bill will be and highlighting new committers.
Apart from your own developer count, you can see your active committer list on Foresight's Billing page. You need to watch at least 1 private repository to see the committer list.
Any owner, admin, and billing user can adjust the payments by entering payment information.
You can always cancel your Foresight plan. If you've paid a plan and decided to cancel, you will be able to use Foresight within your limits until the next billable month. When you cancel your plan, your plan will be automatically downgraded to a Free plan with a 20 committer limit. If you want to delete your Foresight account please contact us.
Yes, you are able to see your invoice from your "Billing" page.
No. Foresight is, and always will be, free for open-source projects and their committers.
Foresight doesn't have any feature limits according to your package. All the features such as Change Impact Analysis, Workflow Monitoring, Test Monitoring, and Rules will be available in every package.
We are very strict about the security and privacy of our customers' information. Foresight applies the least privilege principles and requires minimum permission to process your integration. We use the official GitHub application to gather workflow and test data. However, you can also create your own GitHub app with your own privileges and take control of the security. In addition, Foresight also supports on-prem and GHES in the Enterprise package. Please, contact our Sales team to get a quote.
Paid subscriptions require a Visa, Mastercard, Amex, Discover, or a Paypal account. We only accept online payments. All payments are non-refundable.
Still confused? Ask us anything.
"I got the ideas on how to optimize the build pipeline and say goodbye to the slow builds"
Foresight gives us a nice dashboard to see the project build status with clear highlights on the most important information. The detailed process performance metrics help us identify the performance bottlenecks. I got the ideas on how to optimize the build pipeline and say goodbye to the slow builds.
"Foresight gives you an overview of your workflows"
We have always kept our main (trunk) branch release-ready, but due to unstable and flaky test that is not always easy. GitHub Actions is an excellent tool for testing purposes, but it is not easy to get a quick glance at the overall healthiness of your tests. Foresight on the other hand gives you an overview of your workflows across all individual runs, and we believe this will be a valuable tool to help us keep our tests healthy.
“Since we can customize the access right that we give, Foresight is a definitely a fully PCI-DSS compliant solution”
Foresight helped us to monitor all the GitHub workflows, runs and test results from one single place, to improve the CI pipeline by the alerts, and to save a lot of time. I highly recommend it to the community.
"Foresight helped visualizing the hotspots and prioritize the tests that needs to be optimized first"
Testcontainers' own test suite is massive, because nothing is worse than an unstable testing tool. We always knew that there are opportunities to reduce its execution time by optimizing some of these tests, but Foresight helped visualizing the hotspots and prioritize the tests that needs to be optimized first. With this kick in the... err... build, we are ready to stop procrastinating and start optimizing!
