Skip to content

Commit

Permalink
Documentation edits made through Mintlify web editor
Browse files Browse the repository at this point in the history
  • Loading branch information
UtpalJayNadiger committed Feb 21, 2024
1 parent b7be069 commit c316f38
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/readme/pricing.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -51,9 +51,9 @@ Yes

**If you pay for digger, what are you actually paying for, since you ask users to bring their own compute, and their own state?**

We ask users to bring their own compute and state management system as we believe that the number of privileged environments in an organisation needs to be kept to a minimum. The orchestrator backend, therefore, does not have access to your cloud account, states, plans, tfvars, or any other sensitive data. So what you pay for if you are a paying customer is:
We ask users to bring their own compute and state management system as we believe that the number of privileged environments in an organisation needs to be kept to a minimum. The orchestrator backend, therefore, does not have access to your cloud account, states, plans, tfvars, or any other sensitive data.

For Digger Enterpris, users pay for Audit Log Retention, SAML, SSO & SCIM, Private VCS support (Github, Gitlab and Bitbucket), Compliance Frameworks and Enterprise Support. Book a [demo](https://calendly.com/diggerdev/digger-pro-demo-clone-1) here if you’re interested.
For Digger Enterprise, users pay for Audit Log Retention, SAML, SSO & SCIM, Private VCS support (Github, Gitlab and Bitbucket), Compliance Frameworks and Enterprise Support. Book a [demo](https://calendly.com/diggerdev/digger-pro-demo-clone-1) here if you’re interested.


We truly value community feedback and suggestions. Feel free to join our [slack](https://bit/ly/diggercommunity) if you have any questions that aren’t answered above.
Expand Down

0 comments on commit c316f38

Please sign in to comment.