AI Driven SDLC
Login

AI Driven SDLC Documentation

Guides, references, and best practices for the AI Driven SDLC platform.

Onboarding · Step 2

Integrations Setup

Connect the systems Agentic Foundation and Insights need before those areas become available.

Minimum bar

These two areas are required before Agentic Foundation and delivery Insights become available:

  1. Source control (GitHub today), connected or pending approval
  2. Agent Execution Provider (how the platform runs Agentic Foundation scans)

HR and AI Insights tools are valuable next, but they do not block those areas. AI Usage stays locked until you connect Cursor and/or Claude.

If source control or agent execution later becomes disconnected, Agentic Foundation and delivery Insights lock again until you reconnect them.

Required

GitHub: Installs the AI Driven SDLC Insights app on your org with read-only access so we can see repos, receive webhooks, and queue scans. Connect GitHub sends you to GitHub; approve the org and repo list; you bounce back when it’s done. Optional security and financial Insights metrics are covered in GitHub integration. Write access for automated fix PRs uses a separate AI Driven SDLC Automations app when you enable that feature.

Need an org owner to do the install? Share this doc with them; you’ll see the green connected state once they finish.

Agent Execution Provider: Choose how the platform runs Agentic Foundation work. BYOK (Bring Your Own Keys) means your Cursor user API key or Claude API key (default for new workspaces). ThinkAI Managed Cursor Agent uses the platform’s managed Cursor account instead. See Bring Your Own Keys (BYOK) for what still leaves your environment under BYOK.

Cursor / Claude (AI Insights): Connect at least one AI Insights tool so usage and spend insights can populate. See Cursor and Claude.

HR & people: Upload an org chart CSV or connect an HR system (Personio / ZenHR / Zelt / HiBob when available). Columns like employee_id, name, email, manager_id, department, team work; the uploader lets you map different headers. See Personio, ZenHR, Zelt, and HiBob.

Optional

Everything with a “Coming soon” badge: Visible in the tech stack picker but not connectable yet. Full list.

CI/CD, monitoring, and other categories can be added anytime; they are not required for Agentic Foundation or delivery Insights.

Finish the step

With GitHub and Agent Execution ready, Save and continue. The platform checks those gates before Agentic Foundation and delivery Insights become available.

After that, repos from your GitHub install show up in Agentic Foundation. You choose which ones to scan from there.

v1 target: about 15 minutes from signup to first scan started when you can install the GitHub App yourself. Scan completion is usually 5–15 minutes after that for normal repos.

Next