Skip to main content

Overview

Devin is designed for seamless integration into enterprise environments, with deployment options that balance speed, security, and compliance. Devin can be initiated through the web interface, Slack, or API, ensuring flexibility in how teams engage with the system. Upon activation, Devin operates within a dedicated workspace that includes:
  • A shell for executing commands.
  • A browser for web-based interactions.
  • A code editor for reading and writing code.
Devin’s workspace operates under the control of its brain, which always resides within Cognition’s Cloud.

Devin’s Architecture

Devin’s architecture consists of two key components:
  • The Brain: A stateless, cloud-based service that powers Devin’s intelligence, always residing in Cognition’s Cloud (similar to GitHub Copilot’s architecture).
  • The Devbox: A secure virtual environment where Devin executes code, connects to resources, and interacts with your systems.
The deployment model you choose determines where the Devbox runs and how it connects to your infrastructure.

Enterprise SaaS Architecture

Diagram showing Devin's brain and Devbox both running in Cognition's secure multi-tenant cloud with encrypted data flow
In the Enterprise SaaS model, both Devin’s brain and Devbox run in Cognition’s secure, multi-tenant cloud. All data stays encrypted in transit and at rest. Each Devin session runs on its own isolated machine, keeping customer data segregated by default.

Customer Dedicated SaaS Architecture

Diagram showing Devin hosted in a customer-isolated single-tenant environment with Private Link connection to customer infrastructure
In the Customer Dedicated SaaS model, Cognition hosts Devin in an auto-scaling, customer-isolated environment within a single-tenant VPC. Your VPC connects via AWS Private Link (or IPSec tunnel), allowing Devin to securely access your privately networked resources. Customer data stays encrypted in transit and at rest, and is processed in an isolated tenant.
For detailed steps on configuring AWS PrivateLink connectivity, see Dedicated SaaS Private Networking.

Deployment Options

Devin supports two primary deployment models to meet varying enterprise requirements:
Deployment ModelBrain LocationDevbox LocationNetwork SetupPrimary AdvantageBest For
Enterprise SaaSCognition CloudCognition CloudPublic / IP WhitelistFastest setup, managed infrastructureOrganizations with public or IP-whitelistable resources
Customer Dedicated SaaSCognition CloudCustomer-dedicated single-tenant VPCAWS Private Link or IPSec TunnelTenant isolation with managed infrastructureStrategic enterprises with private networks

Choosing a Deployment Model

Enterprise SaaS Deployment is recommended for most organizations looking for a quick setup with minimal operational overhead. Deployment can be completed within minutes. This model works well when your source code management (GitHub.com, GitLab.com, Azure DevOps Cloud) and artifact stores are publicly accessible or can support IP whitelisting. Customer Dedicated SaaS is ideal for strategic enterprises whose resources are on private networks and cannot support IP whitelisting. In this model, Cognition hosts Devin in an auto-scaling, customer-isolated environment within a single-tenant VPC. Your VPC connects to Cognition’s infrastructure via a secure AWS Private Link (or IPSec tunnel), allowing Devin to access your privately networked resources while maintaining tenant isolation. This deployment model supports MFA VPN access to your internal resources.
Important Networking Considerations:
  • Devin’s Devbox must be able to reach your source code management systems (GitHub, GitLab, Bitbucket, Azure DevOps), artifact stores (Artifactory, CodeArtifact), and other development tools.
  • MFA VPNs are not compatible with Enterprise SaaS deployments. If your resources require MFA VPN access, consider Customer Dedicated SaaS.
  • OpenVPN is supported with Customer Dedicated SaaS deployments, enabling secure connectivity to your internal resources through your existing VPN infrastructure.
  • For self-hosted tools (GitHub Enterprise Server, GitLab self-hosted, Artifactory), you’ll need either IP whitelisting (for SaaS) or a dedicated deployment model.
Once a deployment model is chosen, the next critical step is integrating source code repositories.

Deployment Specifications

Customer Dedicated SaaS Requirements

For Customer Dedicated SaaS deployments, Cognition manages the infrastructure on your behalf. Requirements include:
  • Network Connectivity:
    • AWS Private Link (preferred)
    • IPSec tunnel (alternative option)
    • Ability to establish secure tunnel between your VPC and Cognition’s single-tenant VPC
  • Access Configuration:
    • DNS resolution for your internal resources
    • Network routing configured to allow Devin’s Devbox to reach your SCM, artifact stores, and other development tools

Cross-Tenant Communication

Devin’s architecture ensures secure communication between your environment and Cognition’s Cloud.
Diagram showing secure WebSocket communication between customer environment and Cognition's Azure-hosted tenant
FeatureRequirement
NetworkingEgress access required
PortsHTTPS/443
ConnectionOn startup, Devin establishes a secure WebSocket connection to an isolated container in Cognition’s tenant
CommunicationAll subsequent operations occur over this secure channel
IsolationBackend session isolation for enhanced security
Granting internet access to Devin’s workspace is strongly recommended to ensure full functionality. Devin needs to access your source code repositories, artifact stores, and other development tools.

SSO Guides

Use the following guides to configure single sign-on (SSO) for your enterprise deployment.

FAQs & Additional Information

Devin is a compound AI system and does not currently support third-party LLM API keys.
Please contact our sales team for information on Google Cloud Platform support.
OpenShift support is available upon request. Please reach out to our sales team for details.

Next Steps