Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.dacard.ai/llms.txt

Use this file to discover all available pages before exploring further.

Quick answers on scoring, DAC, accounts, integrations, and privacy. Click any question to expand.

Frequently asked questions

Scoring

Scores read observable signals from your product’s public surface, documentation, and UX. They give a strong directional read but may not capture internal capability that isn’t externally visible. Wiring up adapters (GitHub, Linear) adds operational ground truth for tighter scoring.
Yes. Drop any public URL and we’ll score it. Common use case for benchmarking. Competitor scores won’t have adapter data, so they read solely on public signal.
We recommend re-scoring after major product releases or quarterly at minimum. Score history is preserved automatically so you can track your trajectory over time.
Scores reflect the current state of your product’s public signal. Moves on your website, documentation, pricing page, or observable features will affect scores. Our scoring engine also improves over time, which may surface minor scoring shifts. We surface engine refreshes in the changelog so you can tell them apart.
Score your product’s main landing page or marketing site. Broadest view of your positioning, features, and integration. You can also score specific feature pages for dimension-level analysis.

DAC

DAC pulls from established product management frameworks and seasoned practice. Recommendations are directionally strong but should be validated against your specific context. Verify before making critical calls.
DAC maintains conversation history within a session. If you close the rail and reopen it on the same page, the conversation continues. Moving to a different product resets the conversation context.
DAC only accesses the scoring data for the product you’re currently viewing. It doesn’t access your code, internal documents, or data from connected adapters beyond what surfaces in your scoring data. It uses your scoring result and framework knowledge to surface recommendations.

Account and team

Orgs are created automatically by email domain. Users with the same domain (@acme.com, for example) land in the same org.
Team members can sign up directly and they’ll join your org automatically by email domain. Admins manage roles from Settings > Organization.
Dacard.ai uses hierarchical roles: Member, Lead, Executive, and Admin. Higher roles inherit all permissions from lower roles. Roles are assigned during onboarding based on job title and can be changed by admins. See Roles & Permissions for the full matrix.
Currently, each user belongs to one organization based on their email domain. Multi-org support is on the roadmap.

Integrations

Integrations access operational metrics only: PR velocity, cycle times, review patterns, issue throughput. They do not access code content, message content, or personal data.
Connected sources sync daily via automated jobs. You can also trigger a manual sync at any time from the Sources page.
Yes. Go to Settings > Integrations and click Disconnect. This removes all synced data from that source.

Privacy & Security

Your scoring data is private to your organization by default. Shared result links (/r/) are public, but the URL is unguessable, so only people you share it with can view it.
Scoring data is stored in Turso (SQLite edge database). Authentication is handled by Clerk. Payment processing by Stripe. All connections are encrypted in transit.
Yes. Contact support to request full data deletion. You can also delete individual products and scores from the dashboard.