Data and code ownership
DevSense runs on Microsoft Azure infrastructure in Chile and Brazil. Enterprise deployments can expand to regions requested by the customer, with connectivity and data handling requirements agreed during implementation.
What is processed and where
The platform uses your project’s intent, code and authorized context to prepare and execute development. Model interactions use the providers and credentials enabled for that execution.
Intent, repository, rules and data authorized for the work.
Authorized software development and validation.
Anthropic, OpenAI or Gemini receive the context needed for configured model interactions.
Project code and the reports or evidence published for delivery review.
Ownership and exit
Code generated through development for your project belongs to the customer. You can retain and take all that code from your repository, continuing work with your own team or another provider.
Approved specifications, acceptance criteria and the customer-visible decision history also belong to the customer and can be exported. You can keep these records and continue development outside DevSense with your project’s agreed scope and decisions.
This does not transfer the platform, supervision technology or proprietary internal DevSense artifacts that are not made available to the customer. Reports and evidence published for the project are distinct from those internal artifacts.
Enterprise implementation
Connectivity is designed with the teams responsible for the network and systems. Accessible services, authorized identity and communication rules are agreed using Azure technology and the customer’s existing infrastructure.
The platform’s infrastructure base is in Chile and Brazil. Enterprise deployment can expand to customer-requested Azure regions, subject to service availability and the agreed design. Component locations and AI provider processing are reviewed separately.
Implementation can use site-to-site VPN through Azure VPN Gateway or private connectivity through ExpressRoute where required by the design. The solution integrates with the customer’s networks, devices and controls.
Microsoft: Azure VPN GatewayRoutes, DNS, firewall rules and identity permissions are reviewed for access to repositories, dependencies and test environments. Connectivity does not imply general access to the customer’s entire network.
Information handling
The pilot defines permitted sources and whether scenarios use synthetic or authorized test data. Personal data is included only within the scope and permissions agreed for the service.
Implementation terms must identify retention and deletion for environments, evidence, logs and project data. Code retained in the customer repository remains under the customer’s own controls.
Not by themselves. Self Hosted defines where the platform is installed; BYOAI defines who owns provider credentials. External model interactions process authorized context under the selected provider’s terms and configuration.
Your project’s code, approved specifications, acceptance criteria and customer-visible decision history belong to you. Code stays in your repository, and that documentation can be exported so you can continue with your team or another provider. This does not include the DevSense platform or its proprietary internal artifacts.
Yes. Regional expansion and connectivity are agreed during Enterprise implementation. The design considers Azure service availability, customer technology and authorized access permissions.
Include project objectives and any region or connectivity requirements in your request. Infrastructure and data handling details are agreed before access is enabled.