Frequently Asked Questions
Everything you need to know about security, integrations, review flow, and automated reporting.
Focused on the questions teams ask before adopting DevCite across engineering and leadership workflows.
Security
The biggest concern is usually data access
Most teams want to confirm that DevCite reads metadata only, uses read-only scopes, and avoids source-code storage.
Public-site operating model
Workflow
Auto-send is the default model
Managers can review and override reports, but the system is designed to remove recurring reporting rituals by default.
Public-site operating model
Integrations
Structured for leadership visibilityGitHub, Bitbucket, Jira, Linear, Trello, and Slack can be configured with project-specific boundaries and delivery routes.
Metadata only
No source-code storage
Access stays limited to read-only metadata and delivery context.
Delivery model
Auto-send by default
Managers can review when needed, but the system is built to run itself.
Adoption fit
Project-based pricing
DevCite is designed to stay simpler and more cost-efficient than seat-heavy tooling.
1How does DevCite know what to put in the report?
How does DevCite know what to put in the report?
DevCite uses read-only access to ingest metadata from your GitHub commits, Jira ticket transitions, and Slack discussions. It cross-references these sources using an AI engine to determine the actual outcomes of the engineering work, removing the noise.
2Does DevCite read or store my actual source code?
Does DevCite read or store my actual source code?
No. We only request metadata scopes (e.g., commit messages, PR titles, Jira ticket descriptions). We never see or store your actual source code. All ingested metadata is encrypted using AES-256-GCM.
3Can I review the report before it sends?
Can I review the report before it sends?
Yes. By default, DevCite can automatically send reports to specific Slack channels or emails. However, you can configure it to require manual manager approval, giving you full control to edit the draft before dispatching it.
4Which integrations do you currently support?
Which integrations do you currently support?
We currently integrate with GitHub, Bitbucket, Jira, Linear, Trello, and Slack. All connections are configured on a per-project basis so you can maintain strict access bounds.
5Is it safe for enterprise use?
Is it safe for enterprise use?
Absolutely. We employ zero-training data policies for our AI models (your data is not used to train public LLMs), and all sync caches are securely isolated per project.
6What is the pricing model?
What is the pricing model?
We are currently in a closed beta with early access partners. Pricing will eventually be a flat subscription fee based on the number of active projects, rather than per-seat pricing. Early beta users will receive a lifetime discount.