Enterprise
Trusted code intelligence for engineering organizations adopting AI-assisted development.
Work with us to define repository access, data handling, deployment requirements, rollout, and support in a written Enterprise agreement.
Who it is for
Engineering organizations that want their teams to use AI-assisted development with a clear, written understanding of how code is accessed, handled, and retained — and who need that understanding documented in a contract rather than assumed.
What an engagement can cover
An Enterprise engagement is a conversation about your requirements. It can cover:
- Organization rollout and onboarding
- Getting your repositories indexed and your teams' assistants working, at the scale and pace your org needs.
- Repository access and permission requirements
- How access to each repository's index is scoped, and which permission model fits how your organization works.
- Security and data-handling review
- A walk through how your code is processed and stored, so your security team can evaluate it against your requirements.
- Retention and deletion requirements
- Defining how long indexed data is kept and how it is removed, to match your retention obligations.
- Deployment architecture evaluation
- Reviewing your environment and constraints to determine what deployment approach is feasible for your organization.
- Support and operational expectations
- The support and operational commitments your teams need, defined and written down.
- Procurement, legal review, and contract terms
- Working through procurement, legal review, and the contract terms that formalize the engagement.
How it works
- 01
Discovery
We learn how your organization works, which repositories are in scope, and what your teams need from AI-assisted development.
- 02
Technical and security review
We evaluate your requirements — access, data handling, deployment, identity — and confirm what is feasible together.
- 03
Written scope and contract
Agreed commitments are documented in a written Enterprise agreement, subject to procurement and legal review.
- 04
Pilot and rollout
We start with a scoped pilot, then roll out to your organization against the plan we defined together.
Have a specific security, deployment, identity, or contractual requirement? Tell us what you need. We’ll confirm feasibility during technical review and document agreed commitments in writing.
Requirements can be discussed, but availability is determined during technical review and captured in the signed contract. There is no public Enterprise price; scope and terms are defined per engagement.