Integrations and API

Connect DevSense to your repositories and CI/CD

Keep your organization’s repositories, CI/CD and release policies. Receive developed and tested changes in that workflow, and include CI/CD improvements in the scope when needed.

Your delivery workflow

Work with your existing CI/CD and improve it when needed

Changes are delivered to your GitHub or GitLab repository for its existing checks and integration process. If pipelines need new tests, build steps or configuration changes, include those improvements in scope for DevSense to implement and validate.

  1. DevSense

    Develops, reviews and tests the authorized change.

  2. Your repository

    Receives the PR/MR with code and supporting validation evidence.

  3. Your CI/CD

    Runs the build, tests and checks configured by your organization.

Visibility into delivery progress

Follow the changes submitted to your repository and the integration results available to your team.

DevSense validation and your CI/CD checks are complementary. Integration and production deployment remain subject to your organization’s permissions and release policies.

Integration with your organization

Keep delivery progress visible in your workflow

Project changes

Identify project changes that affect the work your team has authorized.

PR/MR and merge tracking

Relate the published changes to review and integration activity in the customer repository.

Available CI results

Consult the integration results available for the submitted changes.

Connections

DevSense in your working environment

Repositories retain the code. AI providers supply the models, and the platform brings together development, testing and delivery.

  • Register existing repositories or create a new one
  • Import issues as requirements
  • Publish requirements and milestones
  • Branches and pull or merge requests (PR/MR)
  • Record the merge when it occurs
API integration
DevSense
Repositories
GitHub · GitLab
AI providers
Anthropic · OpenAI · Gemini
Operations
Web · Conversation · API
Organization
Users · Groups · Permissions

DevSense API

Execute actions from your systems

Create projects and requirements, start development, manage Sandboxes and retrieve results from your portals and automation. The API operates through your organization’s authorized identity and permissions.

Platform access

Web, Copilot and API

Three ways to operate the same projects. Every action respects the permissions of the identity requesting it.

Access and approvals
DevSense
Web interface
Projects, development and testing
Copilot
Queries and operations through conversation
API
Systems and automations with an API key
Permissions
User or key owner's access

AI models

Use your organization's keys

With BYOAI (Bring Your Own AI), your organization uses its own Anthropic, OpenAI or Gemini API keys. Usage is charged to your provider accounts.

Register multiple keys per provider. When one is exhausted, DevSense uses the next available key. Backup through DevSense billing requires prior opt-in.

Integration documentation

The API reference, access conditions and integration guidance are provided during authorized customer onboarding. Public pages describe capabilities only.

Evaluate DevSense in your organization

Review the platform with a representative project and agreed acceptance criteria.

DevSense

Enlarge the image to read the details.

DevSense CopilotGuided demo
Open platform
A complete sessionCustomer portal · Sample project
Understand the need
Next question in the workflow

Continue the walkthrough or inspect a response in more detail.

Guided demo with fictional projects. No changes are made to the platform.