We connect to 54 product tools to pull operational signal into scoring. Adapter signal grounds your scores in real data, not just public-surface read. GitHub and Linear are the highest-leverage adapters to start with.
Integrations and sources
We connect to product tools to pull operational signal into scoring and intelligence. Instead of leaning only on URL crawling, adapters provide ground-truth data about how your team actually builds, ships, and operates, across all 27 Team Operations dimensions.Platform architecture
How integrations work
1
Connect
Authorize a source via OAuth or API key.
2
Select
Choose which repositories, projects, or workspaces to sync.
3
Sync
Runs automatically on a daily schedule, or manually on demand.
4
Normalize
Raw data is mapped into Dacard’s universal signal format.
5
Score
Real integration data is incorporated alongside crawl-based signals for more accurate scoring.
Available integrations
54 integrations across 10 categories, covering all 27 Team Operations dimensions.Engineering
GitHub
Category: Engineering | Auth: Personal Access Token | Dimensions: 5 Code patterns, deployment frequency, PR cycle times, and AI-assisted development detection. The deepest engineering signal source for delivery velocity and code quality. Signals extracted:
Authentication: Generate a Personal Access Token at GitHub > Settings > Developer Settings > Personal Access Tokens. Requires
repo scope for private repositories.
Discovery: Repositories (owner, collaborator, and organization-affiliated).
Notes: AI-assisted development detection is automatic. Scans merged PR bodies and titles for Co-Authored-By trailers mentioning Claude, Copilot, Cursor, GPT, Gemini, Codeium, Tabnine, and Generated with tool mentions.
Jira
Category: Engineering | Auth: Email:API Token:Domain | Dimensions: 2 Project management, sprint tracking, and issue workflow signals from Jira Cloud. Signals extracted:
Authentication: Provide in the format
email:api_token:domain. Create an API token at Atlassian > Account Settings > Security > API Tokens. Domain is your Jira Cloud instance (e.g., yourcompany.atlassian.net).
Discovery: Jira projects via REST API.
LinearB
Category: Engineering Intelligence | Auth: API Key | Dimensions: 2 Cycle time percentiles, PR throughput, deployment frequency, and code activity breakdown (new work, refactoring, rework). Signals extracted:
Authentication: API Key provided via
x-api-key header. Contact LinearB for API access.
Discovery: Teams or services.
Hivel
Category: Engineering Intelligence | Auth: API Token | Dimensions: 2 DORA metrics (deployment frequency, lead time, change failure rate, MTTR), deployment tracking, and incident management. Signals extracted:
Authentication: API Token via
X-API-Token header.
Discovery: Teams.
Jellyfish
Category: Engineering Intelligence | Auth: API Key | Dimensions: 4 Engineering time allocation across work categories (feature, maintenance, support) and strategic investment mapping. Signals extracted:
Authentication: API Key (Bearer token). Contact Jellyfish admin for API access. Available to Enterprise customers.
Discovery: Teams.
Notes: Customer-gated API. Endpoint paths are inferred and may need adjustment once API access is granted.
Operations
Linear
Category: Operations | Auth: API Key | Dimensions: 10 The deepest single integration. Extracts 16 signal types from Linear’s GraphQL API covering sprint velocity, backlog health, lead time, triage time, estimation accuracy, bug density, priority distribution, canceled work, workload concentration, project completion, and process hygiene. Signals extracted:
Authentication: API Key. Generate at Linear > Settings > API > Personal API Keys.
Discovery: Teams within the workspace.
Notes: All 16 signals are derived from data already available in Linear’s GraphQL API. Most signals (lead time, triage time, unestimated work, label hygiene, workload, priority, bugs, orphan issues) require zero additional API calls beyond the existing completed issues query. Canceled work, stale backlog, and project completion use 3 additional queries per team.
Slack
Category: Communication | Auth: Bot Token | Dimensions: 2 Communication patterns, thread ratios, unique author counts, and cross-team handoff velocity. Signals extracted:
Authentication: Slack Bot Token (starts with
xoxb-). Create a Slack App at api.slack.com with channels:history and channels:read scopes.
Discovery: Public channels in the workspace.
LaunchDarkly
Category: Feature Management | Auth: API Access Token | Dimensions: 2 Feature flag changes, progressive rollout patterns, and flag-based experimentation velocity. Signals extracted:
Authentication: API Access Token. Generate at LaunchDarkly > Account Settings > Authorization.
Discovery: LaunchDarkly projects.
DX
Category: Developer Experience | Auth: API Token | Dimensions: 3 Developer experience survey snapshots, scorecard check pass rates, and improvement initiative tracking. Signals extracted:
Authentication: API Token (Bearer). Generate at getdx.com settings.
Discovery: Teams.
Fibery
Category: Work Management | Auth: Account:API Token | Dimensions: 3 Custom workspace entities, workflow transitions, and cross-entity relationships from Fibery’s flexible work management platform. Signals extracted:
Authentication: Format:
account-name:api-token. Create an API token at Fibery > Settings > API Tokens.
Discovery: Spaces (workspaces with custom entity types).
Design
Figma
Category: Design | Auth: Personal Access Token | Dimensions: 3 Design file version iteration speed and design system component coverage across projects. Signals extracted:
Authentication: Personal Access Token. Generate at Figma > Account Settings > Personal Access Tokens.
Discovery: Teams, then projects within each team.
Analytics
Amplitude
Category: Analytics | Auth: API Key:Secret Key | Dimensions: 4 Product analytics events, retention cohorts, and funnel performance metrics. Signals extracted:
Authentication: Format:
api_key:secret_key. Find both at Amplitude > Settings > Projects > API Keys.
Discovery: Configurable event names in sync settings.
PostHog
Category: Analytics | Auth: Personal API Key | Dimensions: 4 Feature adoption tracking, experiment results, and product event trends. Supports self-hosted instances. Signals extracted:
Authentication: Personal API Key. For self-hosted instances, use format
key:host. Generate at PostHog > Settings > Personal API Keys.
Discovery: PostHog projects.
CRM & Finance
Attio
Category: CRM | Auth: API Key | Dimensions: 3 Deal pipeline outcomes, customer signal aggregation, and relationship intelligence from Attio’s modern CRM. Signals extracted:
Authentication: API Key (Bearer token). Generate at Attio > Settings > API Keys.
Discovery: Lists (pipelines) in the workspace.
HubSpot
Category: CRM | Auth: Private App Access Token | Dimensions: 5 Deal pipeline, contact lifecycle stages, support tickets, marketing campaign performance, and lead source diversity. Signals extracted:
Authentication: Private App Access Token (Bearer). Create at HubSpot > Settings > Integrations > Private Apps.
Discovery: Deal pipelines.
Salesforce
Category: CRM | Auth: Access Token:Instance URL | Dimensions: 4 Opportunity pipeline, win/loss analysis, case management, and customer health signals via SOQL queries. Signals extracted:
Authentication: Format:
access_token:instance_url. Use a Connected App or session token with your Salesforce instance URL (e.g., https://yourorg.my.salesforce.com).
Discovery: Salesforce objects (Opportunity, Case, Lead, Account).
Stripe
Category: Revenue | Auth: Secret Key | Dimensions: 3 Revenue metrics, subscription health, MRR tracking, plan distribution, and churn analysis. Signals extracted:
Authentication: Stripe Secret Key (starts with
sk_live_ or sk_test_). Find at Stripe Dashboard > Developers > API Keys.
Discovery: None (syncs all subscription and charge data).
Orb
Category: Billing & Usage | Auth: API Key | Dimensions: 3 Usage-based billing costs, subscription cost breakdowns, and token/compute usage metering for SaaS products with capability-rich workloads. Signals extracted:
Authentication: API Key. Find at Orb > Settings > API Keys. Use a live mode key for production data.
Discovery: Customers (filter sync to specific customers or sync all).
Notes: Automatically identifies AI/infrastructure-relevant metrics by detecting metric names containing “token”, “compute”, “api_call”, or “request”.
Strategy & Portfolio
Dragonboat
Category: Product Portfolio | Auth: API Key | Dimensions: 3 Product portfolio health, OKR progress with key result tracking, and initiative alignment across portfolios. Signals extracted:
Authentication: API Key (Bearer token). Contact Dragonboat for API access.
Discovery: Portfolios.
Notes: Customer-gated API. Endpoint paths are inferred based on Dragonboat’s product capabilities.
Productboard
Category: Product Management | Auth: API Token | Dimensions: 6 Feature prioritization, initiative planning, objective progress, release cadence, and customer feedback notes. The broadest product management signal source. Signals extracted:
Authentication: API Token (Bearer). Generate at Productboard > Settings > Integrations > Public API.
Discovery: Products.
Dotwork
Category: Strategy | Auth: API Key | Dimensions: 3 Strategic priority alignment, initiative outcomes, and cross-team alignment reporting. Signals extracted:
Authentication: API Key (Bearer token). Contact Dotwork admin for API access. Available to early access customers.
Discovery: Workspaces.
Notes: Customer-gated API. Endpoint paths are inferred based on Dotwork’s product capabilities.
Klue
Category: Competitive Intelligence | Auth: API Key | Dimensions: 2 Competitive intel cards, sales battlecards, and competitor coverage tracking for market intelligence. Signals extracted:
Authentication: API Key. Access at Klue > Apps & Integrations > Content API. Available to Klue customers.
Discovery: Competitors tracked in the platform.
Notes: Customer-gated Content API. Tracks competitor coverage freshness (average days since last card update per competitor).
Infrastructure
AWS Cost Explorer
Category: Infrastructure | Auth: Access Key:Secret Key:Region | Dimensions: 1 Per-service AWS infrastructure cost attribution with daily spend breakdown. Uses the GetCostAndUsage API with per-service grouping. Signals extracted:
Authentication: Format:
AccessKeyId:SecretAccessKey:Region (e.g., AKIAXXXXXXXX:wJalrXXXXXXXX:us-east-1). Create an IAM user with ce:GetCostAndUsage and ce:GetDimensionValues permissions.
Discovery: AWS services with spend (via GetDimensionValues for SERVICE dimension).
Notes: Each API call costs $0.01. The adapter uses daily granularity grouped by SERVICE for cost attribution. Uses AWS Signature V4 authentication.
Vercel
Category: Infrastructure | Auth: API Token | Dimensions: 3 Deployment frequency, build performance timing, deploy error rates, and hosting cost tracking via Vercel’s billing charges API. Signals extracted:
Authentication: API Token. Create at Vercel > Settings > Tokens. Use a full-access token for billing data.
Discovery: Vercel projects in the account or team.
Notes: Billing charges use Vercel’s
/billing/charges endpoint (launched Feb 2026) which returns data in FOCUS v1.3 open-standard format as newline-delimited JSON. Billing data may not be available on all plans.
Signal normalization
Raw data from each integration is normalized into Dacard’s universal signal format before scoring. Examples across categories:AI-assisted development detection
The GitHub integration automatically detects AI-assisted development by scanning merged pull requests for co-authorship patterns and tool mentions. Detected patterns:Co-Authored-Bytrailers mentioning Claude, Copilot, Cursor, GPT, Gemini, Codeium, or TabnineAI-generatedorAI-assistedmarkers in PR body or titleGenerated withtool mentions (Claude Code, Cursor, v0, Bolt, Lovable)- Bot co-author patterns
ai_assisted_pr_count_14d: Number of AI-assisted PRs in the last 14 daysai_assisted_pr_count_30d: Number of AI-assisted PRs in the last 30 days
AI attribution is automatic. No configuration needed. Connect GitHub and the signals are extracted on every sync.
Sync schedule
Managing integrations
Access integration settings at Settings > Integrations (requires Lead role or above):Integrations require a Pro plan or above. Free users can connect one source as a trial.