# Enterprise features What an Enterprise plan includes, how your Git server stays in your network, and what buying one involves. Plansmith sells itself for most teams. Enterprise exists for the ones where it has to clear procurement first, or where the Git server it reads has no route in from the internet. ## Who it is for [#who-it-is-for] * Teams that need volume pricing or contract terms of their own. * Teams whose purchase goes through a review before anyone signs. * Teams whose Git server only answers inside their network. ## What is included [#what-is-included] | Capability | Availability | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | | **Roles and per-plan access.** Owner, member and comment-only, with plans private by default and access set per plan. See [Members and roles](/docs/members-and-roles). | Every plan | | **Audit log.** Invites, role changes, connector changes and company settings. See [Audit log](/docs/audit-log). | Owners only | | **Self-managed GitHub, GitLab and Bitbucket**, plus the broker for a GitLab server with no route in from the internet. See [Deployment options](/docs/deployment-options). | Team and Enterprise | | **Self-hosted Plansmith.** Running Plansmith inside your own environment, scoped to your constraints. | By agreement | | **A named contact and dedicated onboarding.** Someone who knows your rollout, rather than a queue. | Enterprise | ## Procurement [#procurement] * Volume pricing and contract terms of your own. * Invoicing rather than a card. * A data processing agreement on request. * Security review: we answer questionnaires directly, and the [privacy policy](/privacy) covers what we store, who processes it and what leaves your workspace. ## What Plansmith does not do to your code [#what-plansmith-does-not-do-to-your-code] Worth stating plainly, because it is the first question a reviewer asks. Code grounding is read only. The agent reads the repositories you authorize so the Specs it writes match your stack, and it never opens a pull request, pushes a commit, or writes anything back. Push runs the other way: from Plansmith to your issue tracker, carrying exactly the plan you push. ## Talk to us [#talk-to-us] Thirty minutes. Bring a real business requirement from your backlog and we will plan it live.