Access by responsibility
Each organization operates separately. Users can access only the projects and resources assigned to them.
Security and control
Establish organization access and delivery conditions. Autonomous development supervision operates within those policies, with project permissions and records.
Principles
Each organization operates separately. Users can access only the projects and resources assigned to them.
Copilot requests explicit confirmation before performing an action that modifies the project.
Test environments are separate from production, with access authorized through the platform.
Work is delivered in your organization's GitHub or GitLab repositories, according to its delivery rules.
Statuses, actions, decisions and technical evidence are recorded.
DevSense does not merge. An authorized person decides on final integration.
Action controls
Copilot presents the proposed action and the resource it will change. Approving that operation is different from supervising every development step: once scope is authorized, DevSense directs technical execution and corrections.
Each authorization applies to one action and is valid for a limited time. If the resource changes in the meantime, the operation is not executed.
How Copilot operatesReview the proposed change and its effect.
The operation is not executed.
The action is performed and its result is recorded.
Integrations
Platform API keys must have an expiration date, can be revoked immediately and have every use recorded. AI provider keys supplied by your organization are validated and stored encrypted.
Enterprise data and infrastructure
The customer owns the code generated for its project. DevSense uses Azure as its foundation and can expand to agreed Enterprise regions, with customer infrastructure connectivity defined during implementation.
Enterprise evaluation
Every organization has its own access, infrastructure and audit requirements. Discuss with our technical team how DevSense fits into your environment.