How Descant handles your code

Each authoring run uses its own temporary compute environment and repository checkout. Commands and tests execute in a separate sandbox, keeping customer-code execution apart from the services that call models and access your repository.

Temporary execution environments are separate from the run records and artifacts retained to support recovery, inspection and cost reporting.

The customer-code execution network has no direct route to the public internet. Every outbound connection from the execution side passes a network firewall that allows only named hosts, then a NAT gateway, and nothing reaches an execution host from outside. It uses restricted DNS and controlled sources for dependencies and repository archives.

Services that communicate with GitHub and AI model providers operate under a separate network policy with outbound filtering.

Descant uses short-lived GitHub installation credentials scoped to the repository being worked on. Authoring and review use separate identities, with permissions tailored to their roles.

API access is scoped to your organization and permitted operations. API keys are stored as hashes, can be revoked and support expiration. Removing an organization member also revokes the API credentials they created for that organization.

Descant processes repository content to plan, implement, verify and review the work you assign. Relevant code, diffs, issue descriptions and task instructions are sent to AI model providers as part of that work.

Our privacy policy prohibits using customer repository content to train models. Provider processing and retention are covered separately in our data-processing disclosures.

Privacy policySubprocessors

Descant’s infrastructure is configured to encrypt its primary database, cache and run-artifact storage at rest.

Run records, working context and supporting artifacts have different retention schedules. Some records can contain repository content or model conversations. Temporary workspace cleanup does not mean every record associated with a run is immediately deleted.

Repository disconnection, account closure and data erasure are separate operations. Financial and legally required records may be retained. Commits, pull requests, issues and comments published to your GitHub repository remain under your control.

Descant delivers changes through pull requests. Configure automatic merging for a repository or leave the final merge to your team, alongside the checks and protections configured in GitHub.

Organization owners can disconnect a repository to stop new runs and begin shutting down active work.

Descant is designed with the security needs of demanding engineering organizations in mind. Isolated execution, scoped access, encrypted storage and recorded activity are part of that foundation.

We’re preparing for an independent SOC 2 examination, with support from advisors experienced in SOC 2 auditing and technical implementation. Our readiness work covers the system’s controls, operating policies and the evidence needed to demonstrate how they work.