Graphify Enterprise

Graphify Enterprise gives engineering organizations a shared knowledge graph of their software, with graph-aware pull request review and formal verification running in infrastructure they control. It is for teams that need to understand dependencies across repositories, give coding agents grounded context, and meet enterprise deployment and procurement requirements.

​

At a glance

​

What your team can do

​

Understand the codebase as a graph

Graphify connects code symbols, dependencies, and repositories so a developer or agent can follow relationships instead of reconstructing them from isolated search results. Use the graph to investigate a call path, understand the reach of a change, and navigate shared code across services. The graph foundation is shared with the open-source engine. Enterprise adds the deployment and organizational capabilities around that foundation. See how Graphify works and graph provenance.

​

Review changes with dependency context

Graph-aware PR review looks beyond the changed lines to the code that calls, depends on, or overlaps with them. Teams can inspect findings alongside the affected code and use that context in their existing review workflow. Review findings are advisory analysis. They should be assessed alongside tests, code review, and the evidence attached to each result. See pull request reviews.

​

Verify behavior changes

Formal verification compares changed functions with their earlier implementations. Results can include a proof within the supported model, a distinguishing input that demonstrates different behavior, or an explicit unsupported or failed outcome. A completed run is not a blanket proof that an application is correct. Inspect analysis bounds, per-function verdicts, and whether a reported witness was reproduced. See formal verification for the result types and their meaning.

​

Give people and agents shared context

The Graphify product also includes the following workflows. Review the required feature set with your account team for your Enterprise deployment, especially when planning a restricted-network environment. These product guides describe the Cloud workflow. Your deployment’s configuration determines which integrations and UI flows are enabled.

​

Deployment and infrastructure

​

Self-hosting and network boundaries

Enterprise is the commercial offering for running Graphify on your own infrastructure. The enterprise offering includes BYOC and air-gapped VPC deployment discussions; on-premises and VPC requirements can be included in the access request. In a self-hosted deployment, ingested code and graph data stay in your infrastructure. Plan the complete data path, including code hosts, identity providers, model endpoints, connected assistants, and CI systems. An external coding assistant remains subject to its own configuration and provider terms. For an air-gapped deployment, agree the supported feature set, local dependencies, update process, and integration paths before rollout. A hosted connector recipe alone is not an air-gap deployment guide.

​

Capacity and operations

Sizing depends on the repositories you index, graph size, change volume, review and verification concurrency, and enabled features. Bring those requirements to deployment planning rather than treating the hosted plan allowances as Enterprise capacity guarantees. Define responsibility for infrastructure, upgrades, backups, recovery, and monitoring during scoping. Any required availability target, recovery objective, or maintenance window should be part of that discussion.

​

Enterprise, Cloud, and the open-source engine

Running the open-source engine locally does not require an Enterprise license. See the local setup guide.

​

Security, privacy, and identity

​

Data ownership and model training

You own the code and content you ingest, and the graphs built from them. Graphify treats ingested content as confidential and does not train models on your code. See the Terms of Service and Privacy Policy. The hosted service uses subprocessors, including OpenAI and Anthropic for inference under their API terms. Self-hosted data handling is distinct from the hosted service; review the subprocessor list and agree the model and network configuration for your deployment. Independently connected assistants can send prompts or retrieved context to their own providers.

​

SSO and access

Enterprise includes SSO/SAML and GitHub Enterprise support. During setup, identify your identity provider, code-host installation, workspace administrators, and the repositories users should access. Validate the intended access boundaries with representative users before expanding the rollout. Workspace membership and administrative actions are permissioned. The Graphify workspace provides Members, Settings, and Billing controls where available; repository and integration setup may require an owner or administrator. Confirm your provisioning and offboarding requirements during evaluation.

​

Compliance and audit evidence

Graphify’s SOC 2 Type II engagement has started; no report is available yet. Exportable audit logs are also described as part of the Enterprise early-access track. Review the current Security page and Trust Center for updates and available evidence. Bring required encryption standards, audit exports, certifications, and security questionnaires to the evaluation. Confirm the controls and evidence for the proposed deployment instead of assuming that an in-progress control is already delivered.

​

Retention, export, and deletion

On self-hosted deployments, retention is governed by your own infrastructure. Agree how graph storage, backups, logs, and deletion should work with your internal policy. The Privacy Policy documents hosted retention separately and explains how to request export or deletion. A DPA is available, with custom terms supported for Enterprise.

​

Licensing and commercial terms

Enterprise is licensed per developer seat with custom pricing. The quote is scoped with your account team, rather than purchased through the self-service checkout. The enterprise offering supports:

• Custom invoicing and payment terms.
• A custom DPA and terms of service.
• Deployment and capacity scoped to your organization.
• License renewal and seat arrangements agreed with your account team.

Include your expected developer count and growth, deployment footprint, required capabilities, and procurement timeline when requesting a quote. Confirm seat definitions, minimum commitments, capacity, renewal, and any third-party or infrastructure costs in the proposal. There is no public fixed Enterprise price or universal hardware specification.

​

Support and rollout

Both Teams and Enterprise include a dedicated Slack support channel. If you require specific response times, coverage hours, an escalation process, onboarding services, or an availability SLA, agree them during procurement. The public plan does not specify a universal SLA. Use the following evaluation sequence to align engineering, security, and procurement:

​

Prepare for an enterprise discussion

​

Frequently asked questions