We enabled Greptile for our open-source…
We enabled Greptile for our open-source repositories but were not aware that doing so would result in a paid plan or usage-based billing being activated.
Later, we discovered invoices for usage that our team had never knowingly approved. The team member who originally enabled the integration was also not aware that billing would be activated for repository authors.
In our view, moving users from a free/open-source setup into paid or flex usage should require a clear and explicit confirmation before any charges begin. A notification after usage has already occurred is not the same as getting consent beforehand.
This is especially concerning for larger open-source projects, where an integration may be enabled by one team member and potentially generate charges across repository activity without the organization realizing that paid billing has been activated.
We have contacted Greptile and asked them to review and cancel the invoices. We will update this review depending on how they handle the situation.
Regardless of the outcome, we believe billing and plan changes should be communicated very clearly and require explicit opt-in before customers start accumulating charges.



