How long does it take to set up Deviera?

Most teams are fully set up in under 5 minutes. Install the GitHub App (1 minute), connect your project management tool via OAuth (2 minutes), and enable your first automation templates (2 minutes). Your first signal typically arrives within 30 minutes of the next CI event in your repositories.

Do I need to add code or modify my CI configuration?

No. Deviera works entirely through GitHub App webhooks and GitLab OAuth — no code changes, no CI configuration modifications, and no agents to install. You install the GitHub App or connect GitLab OAuth, and Deviera starts receiving events automatically.

What GitHub permissions does the GitHub App require?

Deviera requests read access to repository metadata, commit statuses, and pull requests — and write access only for features that require it (posting PR comments and creating GitHub issues). Deviera never requests access to your repository contents or source code.

Can I connect only specific repositories, or does it have to be the whole organization?

You can choose. When installing the GitHub App, GitHub lets you select either all repositories in the organization or a specific subset. You can change this selection at any time from your GitHub organization's installed Apps settings.

When will I see my first signal in the Signal Feed?

Typically within 30 minutes of your next GitHub or GitLab event (a CI run, a push, or a PR event). If you want to see a signal immediately, you can push a commit, open a PR, or trigger a CI run in any connected repository.

Does Deviera work with both GitHub and GitLab simultaneously?

Yes. You can connect GitHub (via the GitHub App) and GitLab (via OAuth) to the same Deviera workspace. Automations can reference triggers from either platform. Cross-provider deduplication prevents the same signal from creating duplicate tickets in your project management tools.

How do I invite teammates to my workspace?

Go to Settings → Team and enter your teammate's email address. They will receive an invitation to join your workspace. Free workspaces support up to 3 members; Pro up to 5; Team up to 20; Enterprise is unlimited.

Does Deviera have any free tools I can use without signing up?

Yes. Deviera offers two free public tools that work without an account — CI Health Score (/tools/ci-health-score) and PR Cycle Time (/tools/pr-cycle-time). Enter any public GitHub repository URL to instantly analyze its CI reliability and PR velocity. No login required.

What happens to my data if I cancel my subscription?

Your workspace data is retained for 30 days after cancellation so you can export it or reactivate. After 30 days, all workspace data is permanently deleted. Your integration connections (GitHub, GitLab, Linear, Jira, ClickUp, Sentry, Vercel, Slack) are not affected — you can reconnect without reinstalling if you reactivate within the retention window.

What is the Friction Score and how is it calculated?

The Friction Score is a real-time 0–100 number that reflects your team's engineering overhead — lower is better. It weighs signals from the last 7 days across five categories: CI failures (highest weight), stale PRs, deployment failures, flaky test detections, and code debt signals. It updates within seconds of each incoming event. Think of it as a sprint-planning signal: if it's climbing, something is slowing your team down.

What do the Friction Score ranges mean?

0–25 is Healthy — normal background noise, no action needed. 26–50 is Moderate — some friction accumulating, worth reviewing this sprint. 51–75 is Stressed — friction is measurably slowing delivery, intervention recommended. 76–100 is Critical — engineering is under severe load, immediate action required.

Why is my Friction Score high even though we shipped a release this week?

The Friction Score measures unresolved signals, not output. A team can ship a release while carrying significant friction — CI failures that were ignored, PRs that needed multiple re-runs, deployment rollbacks that were handled manually. The score reflects the overhead your team absorbed, regardless of whether you shipped through it.

How do I reduce my Friction Score?

The fastest reductions come from resolving the highest-weighted signals first. Enable automation rules for CI failure detection — these will auto-create tickets and enable structured triage. Then address stale PRs with automated reviewer reminders. Flaky test quarantine requires investigation of the non-determinism; the CI Intelligence panel shows which tests are alternating.

Is the Friction Score per-repository or team-wide?

The main Friction Score is team-wide — it reflects aggregate load across all connected repositories. Per-repository health is visible in the Repo Health table on the CI Intelligence page, which shows failure rate, flaky test count, and trend direction for each repo.

How is the Friction Score different from DORA Metrics?

They measure different things. The Friction Score is operational and real-time — it reflects what is happening right now (CI failures firing, PRs going stale, deployments failing). DORA Metrics are historical delivery benchmarks — Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery — computed over weeks or months. Use the Friction Score for day-to-day triage; use DORA Metrics for quarterly trend analysis and executive reporting.

How does deduplication work to prevent duplicate tickets?

Deviera uses two layers of deduplication. Per-automation deduplication (24-hour window) prevents the same automation from firing twice for the same event within a day. Cross-provider deduplication (3-day window, title-based) prevents the same signal from creating tickets in both Linear and Jira if you have both connected. Together, these ensure each friction event generates at most one ticket across your entire toolchain.

Can I build custom automation rules, or am I limited to the 107 templates?

Both. The 107 templates are one-click starting points — enable them as-is or clone and customize. The visual rule builder lets you create rules from scratch: pick a trigger (any GitHub, GitLab, Vercel, or Sentry event), add conditions (filter by repository, branch, label, failure threshold, or time-based criteria), and choose an action. Rules can chain a primary and secondary action.

What trigger types are available?

There are 32 trigger types across five platforms: 21 from GitHub (CI failure, CI recovery, PR opened, PR stale, PR merged, deployment failure, deployment recovery, and more), 7 from GitLab (pipeline failed, pipeline recovered, MR opened, MR stale, MR merged, MR closed, push event), 2 from Sentry (error alert, issue created), 3 from Vercel (deployment created, deployment ready, deployment failed), and 1 CI-derived trigger (flaky test detected).

What actions can automations take?

There are 24 action types. Ticket creation: create a Linear issue, Jira ticket, GitLab issue, GitHub issue, ClickUp task, or Sentry issue. Auto-resolution: close a GitHub issue, Linear issue, Jira issue, or ClickUp task. Code collaboration: post a PR comment, post an MR comment, add/remove a GitHub label, request a GitHub reviewer, merge a GitHub PR, close a GitHub PR, or add a GitLab label. Notifications: send a Slack message, send an email, or send a custom webhook. Rules can chain a primary and secondary action.

What is the difference between a template and a custom automation rule?

Templates are pre-built rules built by Deviera for the most common engineering patterns — things like "open a Linear issue when CI fails on main" or "remind reviewers when a PR has been open for 3 days." There are 107 templates organized by integration and use case. Custom rules are built from scratch in the visual builder, giving you full control over trigger, conditions, and actions. You can also clone any template and customize it.

What happens if I hit my automation limit on the Free plan?

On the Free plan, you can have up to 5 active automation rules. When you reach the limit, you can deactivate existing rules to make room or upgrade to Pro (up to 20 rules). Rules above the limit are not deleted — they are paused and resume automatically if you upgrade or free up a slot.

Can I pause or disable an automation without deleting it?

Yes. Every automation rule has an active/paused toggle. Paused rules stop firing but retain their configuration, history, and position in your rule list. You can re-enable them at any time. This is useful for temporarily disabling rules during planned maintenance windows or incidents.

Can automations auto-close tickets when the problem resolves?

Yes. Auto-resolution is supported for CI failures, deployment failures, and flaky tests. When a CI pipeline recovers, Deviera can automatically close the corresponding ticket in Linear, Jira, ClickUp, GitLab Issues, GitHub Issues, or Sentry. This keeps your issue tracker synchronized with actual system state without manual cleanup.

Is there a log of every time an automation fired?

Yes. The Signal Feed is a real-time, timestamped log of every event Deviera has processed and every automation that fired. Each entry shows the trigger, the matched rule, the action taken, and whether it succeeded. You can filter by integration, rule, or time range. Signal Feed history is retained for 30 days on Free, 90 days on Pro, 180 days on Team, and 365 days on Enterprise.

Which integrations does Deviera support?

Deviera connects to 8 platforms: GitHub (via GitHub App or OAuth), GitLab (OAuth — cloud and self-hosted), Linear, Jira (Atlassian Cloud), ClickUp, Sentry (OAuth), Vercel (API token), and Slack (Incoming Webhooks). GitLab requires a Team plan or higher; Sentry requires Pro or higher; all other integrations are available on every plan.

What is the difference between the GitHub App and GitHub OAuth?

The GitHub App is the recommended connection method. It operates at the organization level, uses short-lived installation tokens (not personal access tokens), supports per-repository scoping, and receives webhook events with per-installation HMAC-SHA256 signature verification. GitHub OAuth is a per-user personal access token — it works but is fragile (tokens expire, users leave organizations). Deviera supports both but recommends the GitHub App for production use.

Does Deviera support GitLab self-hosted (GitLab CE/EE), or only GitLab.com?

Both. Deviera supports GitLab.com (cloud) and GitLab self-hosted instances (Community Edition and Enterprise Edition). For self-hosted, you provide your instance URL during OAuth setup. GitLab integration requires a Team plan or higher.

Does Deviera support Jira Server (on-premise) or only Jira Cloud?

Currently Jira Cloud only (Atlassian OAuth 2.0). Jira Server and Jira Data Center use a different authentication model that is not yet supported. Jira Cloud integration is available on all plans.

Does Deviera integrate with Sentry?

Yes. Deviera connects to Sentry via OAuth 2.0. You can trigger automations from 2 Sentry event types — error alerts and issue-created events. The create_sentry_issue action lets you push signals from GitHub or GitLab directly into Sentry. Auto-resolution is also supported: when a Sentry issue resolves, Deviera can close the corresponding ticket in your project management tool. Sentry integration requires a Pro plan or higher.

How does the Vercel integration work?

The Vercel integration uses API token polling rather than inbound webhooks. Deviera polls the Vercel API every 5 minutes for deployment state changes. When a deployment is created, succeeds, or fails, the relevant automation rules fire. This means Vercel signals may arrive up to 5 minutes after the deployment event.

Can I connect multiple Slack channels for different signals?

Yes. Slack uses incoming webhook URLs, and each automation rule specifies its own webhook URL independently. You can route critical CI failures to an engineering-alerts channel, stale PR summaries to a standup channel, and deployment notifications to a releases channel — all from different rules pointing to different webhook URLs. Slack is available on all plans.

Can I connect multiple GitHub organizations or GitLab groups to one Deviera workspace?

Currently, each Deviera workspace connects to one GitHub organization and one GitLab group. If you have repositories across multiple GitHub organizations, you can create separate Deviera workspaces — one per org — and manage them under the same account.

Why does Deviera say my integration needs to be reconnected?

Deviera runs a daily health check on all connected integrations at 08:00 UTC. If an OAuth token has expired or been revoked at the provider (common after rotating API keys, revoking app access, or extended inactivity), Deviera marks that integration as needing reconnection. Go to Settings → Integrations and click Reconnect to re-authorize via OAuth. Your automation rules resume automatically once reconnected.

Can I use both Linear and Jira at the same time?

Yes. You can connect Linear and Jira (and ClickUp) simultaneously. Cross-provider deduplication (3-day title-based window) ensures that the same signal does not create duplicate tickets across your connected trackers. You can configure which automation rules target which tool.

What is the DORA Metrics dashboard?

The DORA Metrics dashboard shows your team's four core delivery benchmarks: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery (MTTR). These are the industry-standard engineering performance metrics used by teams and executives to track delivery health over time. The dashboard is computed automatically from your existing event history — no extra configuration needed. Available on Pro and above.

What is the PR Cycle Time dashboard?

The PR Cycle Time dashboard shows median and P75 time from PR opened to merged, broken down by repository or across your whole workspace. It surfaces bottlenecks in your code review process — which repos are slowest, which time periods have the most delays, and how your cycle time trends week over week. No extra configuration needed beyond a connected GitHub App. Available on Pro and above.

What is the Repo Health dashboard?

The Repo Health table shows per-repository CI health metrics: failure rate, flaky test count, deployment success rate, and trend direction (improving or worsening). It gives engineering leads a fast view of which repositories are generating the most friction. Available on Pro and above.

What is the Value Dashboard?

The Value Dashboard shows the business impact of your automation rules — how many issues were auto-created, how many were auto-resolved, and how much manual triage work was avoided. It gives engineering managers a way to report automation ROI to leadership. Available on all plans.

What is the Public Signal Wall?

The Public Signal Wall is a shareable, read-only view of your team's engineering signal feed that can be shared with stakeholders outside your Deviera workspace. It shows recent CI, deployment, and PR events without exposing internal automation rules or configuration. Available on Team and Enterprise plans.

What is Investment Distribution?

Investment Distribution breaks down where your team's engineering time is going — new features, bug fixes, maintenance, and CI/infrastructure overhead — based on PR labels and automation event patterns. It gives VPs of Engineering a data-backed answer to "how much of our capacity is going to maintenance vs. product work?" Available on Pro and above.

What are the available plans?

Deviera has four plans. Free ($0): 1 repo, 5 automations, 3 members, GitHub / Linear / Jira / ClickUp / Vercel / Slack. Pro ($29/month): 5 repos, 20 automations, 5 members, adds Sentry integration and all analytics dashboards (DORA, PR Cycle Time, Repo Health, Investment Distribution). Team ($25/seat/month, minimum 5 seats): unlimited repos and automations, 20 members, adds GitLab, Public Signal Wall, and all AI features. Enterprise (custom): unlimited everything, audit log, SSO/SAML, dedicated onboarding, and SLA. All new accounts start with a 14-day Pro trial.

What is the difference between Pro and Team?

Pro adds all analytics dashboards (DORA Metrics, PR Cycle Time, Repo Health, Bottleneck Radar, Investment Distribution) and Sentry integration over Free. Team adds GitLab integration, Public Signal Wall, all AI features (natural-language automation builder, root-cause analysis, AI PR comments), and unlimited repos and automations over Pro. If your team needs GitLab or wants AI-powered automation building, Team is the right tier.

Is there a free trial for paid plans?

Yes. All new workspaces start with a 14-day Pro trial — no credit card required. You get full access to Pro features including up to 20 automation rules and all analytics dashboards. After 14 days, you can upgrade to keep Pro features or continue on the Free plan.

Is there annual pricing?

Yes. Annual billing is available at a 2-month discount: Pro is $290/year (equivalent to $24.17/month), and Team is $250/seat/year (equivalent to $20.83/seat/month). Annual plans are billed upfront and renew automatically each year.

What does the Team plan minimum of 5 seats mean?

The Team plan is priced per seat with a minimum of 5 seats. If your team has fewer than 5 engineers, you still pay for 5 seats. For teams larger than 5, you pay per seat. You can add or remove seats at any time from the billing page — changes are prorated.

How does per-seat billing work? Who counts as a seat?

A seat is any user who is an active member of your Deviera workspace. Invited members who have not accepted their invitation do not count. Removing a member from Settings → Team frees that seat immediately.

What happens to my automations if I downgrade to a lower plan?

Your automation rules are not deleted, but they are capped at the new plan's limit. On the Free plan, only 5 rules can be active at once; others are paused. GitLab integration requires a Team plan — if you downgrade below Team, GitLab automation rules pause. Sentry integration requires Pro — if you downgrade to Free, Sentry automation rules also pause. Rules resume automatically if you upgrade again.

Can I change my plan mid-cycle?

Yes. Upgrades take effect immediately and are prorated for the remainder of your billing period. Downgrades take effect at the end of the current billing period so you keep access until the period ends.

Is there an Enterprise plan, and what does it include?

Yes. Enterprise includes unlimited repos, automations, and members; audit log; SSO/SAML; granular admin roles; dedicated onboarding; custom integrations; and an SLA. Pricing is custom based on team size and requirements. Contact us at the pricing page to get a quote or join the waitlist.

What AI features does Deviera offer?

Deviera includes five AI-powered capabilities: AI issue enrichment (automatically adds context, severity, and affected-service tags to created issues), signal summaries (plain-language summaries of what triggered an automation and why), natural-language automation builder (describe a rule in plain English and Deviera generates it), root-cause analysis (surfaces likely root causes for recurring CI failures), and AI PR comments (posts a short review summary on opened PRs). Issue enrichment and signal summaries are available on Pro and above; all AI features are available on Team and Enterprise.

Does Deviera use its own AI, or do I bring my own API key?

Deviera uses a Bring Your Own Key (BYOK) model. You connect your own API key from Anthropic, OpenAI, or Gemini in Settings → AI. Deviera applies no markup — you pay your AI provider directly at their standard rates. This keeps AI costs transparent and under your control.

Support

Frequently asked questions

Everything you need to know about Deviera. Can't find what you're looking for? Contact us.

Start your 14-day free trial →

Getting started Friction Score Automations Integrations Dashboards & metrics Pricing & billing AI features Security

Getting started

How long does it take to set up Deviera?: Most teams are fully set up in under 5 minutes. Install the GitHub App (1 minute), connect your project management tool via OAuth (2 minutes), and enable your first automation templates (2 minutes). Your first signal typically arrives within 30 minutes of the next CI event in your repositories.
Do I need to add code or modify my CI configuration?: No. Deviera works entirely through GitHub App webhooks and GitLab OAuth — no code changes, no CI configuration modifications, and no agents to install. You install the GitHub App or connect GitLab OAuth, and Deviera starts receiving events automatically.
What GitHub permissions does the GitHub App require?: Deviera requests read access to repository metadata, commit statuses, and pull requests — and write access only for features that require it (posting PR comments and creating GitHub issues). Deviera never requests access to your repository contents or source code.
Can I connect only specific repositories, or does it have to be the whole organization?: You can choose. When installing the GitHub App, GitHub lets you select either all repositories in the organization or a specific subset. You can change this selection at any time from your GitHub organization's installed Apps settings.
When will I see my first signal in the Signal Feed?: Typically within 30 minutes of your next GitHub or GitLab event (a CI run, a push, or a PR event). If you want to see a signal immediately, you can push a commit, open a PR, or trigger a CI run in any connected repository.
Does Deviera work with both GitHub and GitLab simultaneously?: Yes. You can connect GitHub (via the GitHub App) and GitLab (via OAuth) to the same Deviera workspace. Automations can reference triggers from either platform. Cross-provider deduplication prevents the same signal from creating duplicate tickets in your project management tools.
How do I invite teammates to my workspace?: Go to Settings → Team and enter your teammate's email address. They will receive an invitation to join your workspace. Free workspaces support up to 3 members; Pro up to 5; Team up to 20; Enterprise is unlimited.
Does Deviera have any free tools I can use without signing up?: Yes. Deviera offers two free public tools that work without an account — CI Health Score (/tools/ci-health-score) and PR Cycle Time (/tools/pr-cycle-time). Enter any public GitHub repository URL to instantly analyze its CI reliability and PR velocity. No login required.
What happens to my data if I cancel my subscription?: Your workspace data is retained for 30 days after cancellation so you can export it or reactivate. After 30 days, all workspace data is permanently deleted. Your integration connections (GitHub, GitLab, Linear, Jira, ClickUp, Sentry, Vercel, Slack) are not affected — you can reconnect without reinstalling if you reactivate within the retention window.

Friction Score

What is the Friction Score and how is it calculated?: The Friction Score is a real-time 0–100 number that reflects your team's engineering overhead — lower is better. It weighs signals from the last 7 days across five categories: CI failures (highest weight), stale PRs, deployment failures, flaky test detections, and code debt signals. It updates within seconds of each incoming event. Think of it as a sprint-planning signal: if it's climbing, something is slowing your team down.
What do the Friction Score ranges mean?: 0–25 is Healthy — normal background noise, no action needed. 26–50 is Moderate — some friction accumulating, worth reviewing this sprint. 51–75 is Stressed — friction is measurably slowing delivery, intervention recommended. 76–100 is Critical — engineering is under severe load, immediate action required.
Why is my Friction Score high even though we shipped a release this week?: The Friction Score measures unresolved signals, not output. A team can ship a release while carrying significant friction — CI failures that were ignored, PRs that needed multiple re-runs, deployment rollbacks that were handled manually. The score reflects the overhead your team absorbed, regardless of whether you shipped through it.
How do I reduce my Friction Score?: The fastest reductions come from resolving the highest-weighted signals first. Enable automation rules for CI failure detection — these will auto-create tickets and enable structured triage. Then address stale PRs with automated reviewer reminders. Flaky test quarantine requires investigation of the non-determinism; the CI Intelligence panel shows which tests are alternating.
Is the Friction Score per-repository or team-wide?: The main Friction Score is team-wide — it reflects aggregate load across all connected repositories. Per-repository health is visible in the Repo Health table on the CI Intelligence page, which shows failure rate, flaky test count, and trend direction for each repo.
How is the Friction Score different from DORA Metrics?: They measure different things. The Friction Score is operational and real-time — it reflects what is happening right now (CI failures firing, PRs going stale, deployments failing). DORA Metrics are historical delivery benchmarks — Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery — computed over weeks or months. Use the Friction Score for day-to-day triage; use DORA Metrics for quarterly trend analysis and executive reporting.

Automations

How does deduplication work to prevent duplicate tickets?: Deviera uses two layers of deduplication. Per-automation deduplication (24-hour window) prevents the same automation from firing twice for the same event within a day. Cross-provider deduplication (3-day window, title-based) prevents the same signal from creating tickets in both Linear and Jira if you have both connected. Together, these ensure each friction event generates at most one ticket across your entire toolchain.
Can I build custom automation rules, or am I limited to the 107 templates?: Both. The 107 templates are one-click starting points — enable them as-is or clone and customize. The visual rule builder lets you create rules from scratch: pick a trigger (any GitHub, GitLab, Vercel, or Sentry event), add conditions (filter by repository, branch, label, failure threshold, or time-based criteria), and choose an action. Rules can chain a primary and secondary action.
What trigger types are available?: There are 32 trigger types across five platforms: 21 from GitHub (CI failure, CI recovery, PR opened, PR stale, PR merged, deployment failure, deployment recovery, and more), 7 from GitLab (pipeline failed, pipeline recovered, MR opened, MR stale, MR merged, MR closed, push event), 2 from Sentry (error alert, issue created), 3 from Vercel (deployment created, deployment ready, deployment failed), and 1 CI-derived trigger (flaky test detected).
What actions can automations take?: There are 24 action types. Ticket creation: create a Linear issue, Jira ticket, GitLab issue, GitHub issue, ClickUp task, or Sentry issue. Auto-resolution: close a GitHub issue, Linear issue, Jira issue, or ClickUp task. Code collaboration: post a PR comment, post an MR comment, add/remove a GitHub label, request a GitHub reviewer, merge a GitHub PR, close a GitHub PR, or add a GitLab label. Notifications: send a Slack message, send an email, or send a custom webhook. Rules can chain a primary and secondary action.
What is the difference between a template and a custom automation rule?: Templates are pre-built rules built by Deviera for the most common engineering patterns — things like "open a Linear issue when CI fails on main" or "remind reviewers when a PR has been open for 3 days." There are 107 templates organized by integration and use case. Custom rules are built from scratch in the visual builder, giving you full control over trigger, conditions, and actions. You can also clone any template and customize it.
What happens if I hit my automation limit on the Free plan?: On the Free plan, you can have up to 5 active automation rules. When you reach the limit, you can deactivate existing rules to make room or upgrade to Pro (up to 20 rules). Rules above the limit are not deleted — they are paused and resume automatically if you upgrade or free up a slot.
Can I pause or disable an automation without deleting it?: Yes. Every automation rule has an active/paused toggle. Paused rules stop firing but retain their configuration, history, and position in your rule list. You can re-enable them at any time. This is useful for temporarily disabling rules during planned maintenance windows or incidents.
Can automations auto-close tickets when the problem resolves?: Yes. Auto-resolution is supported for CI failures, deployment failures, and flaky tests. When a CI pipeline recovers, Deviera can automatically close the corresponding ticket in Linear, Jira, ClickUp, GitLab Issues, GitHub Issues, or Sentry. This keeps your issue tracker synchronized with actual system state without manual cleanup.
Is there a log of every time an automation fired?: Yes. The Signal Feed is a real-time, timestamped log of every event Deviera has processed and every automation that fired. Each entry shows the trigger, the matched rule, the action taken, and whether it succeeded. You can filter by integration, rule, or time range. Signal Feed history is retained for 30 days on Free, 90 days on Pro, 180 days on Team, and 365 days on Enterprise.

Integrations

Which integrations does Deviera support?: Deviera connects to 8 platforms: GitHub (via GitHub App or OAuth), GitLab (OAuth — cloud and self-hosted), Linear, Jira (Atlassian Cloud), ClickUp, Sentry (OAuth), Vercel (API token), and Slack (Incoming Webhooks). GitLab requires a Team plan or higher; Sentry requires Pro or higher; all other integrations are available on every plan.
What is the difference between the GitHub App and GitHub OAuth?: The GitHub App is the recommended connection method. It operates at the organization level, uses short-lived installation tokens (not personal access tokens), supports per-repository scoping, and receives webhook events with per-installation HMAC-SHA256 signature verification. GitHub OAuth is a per-user personal access token — it works but is fragile (tokens expire, users leave organizations). Deviera supports both but recommends the GitHub App for production use.
Does Deviera support GitLab self-hosted (GitLab CE/EE), or only GitLab.com?: Both. Deviera supports GitLab.com (cloud) and GitLab self-hosted instances (Community Edition and Enterprise Edition). For self-hosted, you provide your instance URL during OAuth setup. GitLab integration requires a Team plan or higher.
Does Deviera support Jira Server (on-premise) or only Jira Cloud?: Currently Jira Cloud only (Atlassian OAuth 2.0). Jira Server and Jira Data Center use a different authentication model that is not yet supported. Jira Cloud integration is available on all plans.
Does Deviera integrate with Sentry?: Yes. Deviera connects to Sentry via OAuth 2.0. You can trigger automations from 2 Sentry event types — error alerts and issue-created events. The create_sentry_issue action lets you push signals from GitHub or GitLab directly into Sentry. Auto-resolution is also supported: when a Sentry issue resolves, Deviera can close the corresponding ticket in your project management tool. Sentry integration requires a Pro plan or higher.
How does the Vercel integration work?: The Vercel integration uses API token polling rather than inbound webhooks. Deviera polls the Vercel API every 5 minutes for deployment state changes. When a deployment is created, succeeds, or fails, the relevant automation rules fire. This means Vercel signals may arrive up to 5 minutes after the deployment event.
Can I connect multiple Slack channels for different signals?: Yes. Slack uses incoming webhook URLs, and each automation rule specifies its own webhook URL independently. You can route critical CI failures to an engineering-alerts channel, stale PR summaries to a standup channel, and deployment notifications to a releases channel — all from different rules pointing to different webhook URLs. Slack is available on all plans.
Can I connect multiple GitHub organizations or GitLab groups to one Deviera workspace?: Currently, each Deviera workspace connects to one GitHub organization and one GitLab group. If you have repositories across multiple GitHub organizations, you can create separate Deviera workspaces — one per org — and manage them under the same account.
Why does Deviera say my integration needs to be reconnected?: Deviera runs a daily health check on all connected integrations at 08:00 UTC. If an OAuth token has expired or been revoked at the provider (common after rotating API keys, revoking app access, or extended inactivity), Deviera marks that integration as needing reconnection. Go to Settings → Integrations and click Reconnect to re-authorize via OAuth. Your automation rules resume automatically once reconnected.
Can I use both Linear and Jira at the same time?: Yes. You can connect Linear and Jira (and ClickUp) simultaneously. Cross-provider deduplication (3-day title-based window) ensures that the same signal does not create duplicate tickets across your connected trackers. You can configure which automation rules target which tool.

Dashboards & metrics

What is the DORA Metrics dashboard?: The DORA Metrics dashboard shows your team's four core delivery benchmarks: Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Mean Time to Recovery (MTTR). These are the industry-standard engineering performance metrics used by teams and executives to track delivery health over time. The dashboard is computed automatically from your existing event history — no extra configuration needed. Available on Pro and above.
What is the PR Cycle Time dashboard?: The PR Cycle Time dashboard shows median and P75 time from PR opened to merged, broken down by repository or across your whole workspace. It surfaces bottlenecks in your code review process — which repos are slowest, which time periods have the most delays, and how your cycle time trends week over week. No extra configuration needed beyond a connected GitHub App. Available on Pro and above.
What is the Repo Health dashboard?: The Repo Health table shows per-repository CI health metrics: failure rate, flaky test count, deployment success rate, and trend direction (improving or worsening). It gives engineering leads a fast view of which repositories are generating the most friction. Available on Pro and above.
What is the Value Dashboard?: The Value Dashboard shows the business impact of your automation rules — how many issues were auto-created, how many were auto-resolved, and how much manual triage work was avoided. It gives engineering managers a way to report automation ROI to leadership. Available on all plans.
What is the Public Signal Wall?: The Public Signal Wall is a shareable, read-only view of your team's engineering signal feed that can be shared with stakeholders outside your Deviera workspace. It shows recent CI, deployment, and PR events without exposing internal automation rules or configuration. Available on Team and Enterprise plans.
What is Investment Distribution?: Investment Distribution breaks down where your team's engineering time is going — new features, bug fixes, maintenance, and CI/infrastructure overhead — based on PR labels and automation event patterns. It gives VPs of Engineering a data-backed answer to "how much of our capacity is going to maintenance vs. product work?" Available on Pro and above.

Pricing & billing

What are the available plans?: Deviera has four plans. Free ($0): 1 repo, 5 automations, 3 members, GitHub / Linear / Jira / ClickUp / Vercel / Slack. Pro ($29/month): 5 repos, 20 automations, 5 members, adds Sentry integration and all analytics dashboards (DORA, PR Cycle Time, Repo Health, Investment Distribution). Team ($25/seat/month, minimum 5 seats): unlimited repos and automations, 20 members, adds GitLab, Public Signal Wall, and all AI features. Enterprise (custom): unlimited everything, audit log, SSO/SAML, dedicated onboarding, and SLA. All new accounts start with a 14-day Pro trial.
What is the difference between Pro and Team?: Pro adds all analytics dashboards (DORA Metrics, PR Cycle Time, Repo Health, Bottleneck Radar, Investment Distribution) and Sentry integration over Free. Team adds GitLab integration, Public Signal Wall, all AI features (natural-language automation builder, root-cause analysis, AI PR comments), and unlimited repos and automations over Pro. If your team needs GitLab or wants AI-powered automation building, Team is the right tier.
Is there a free trial for paid plans?: Yes. All new workspaces start with a 14-day Pro trial — no credit card required. You get full access to Pro features including up to 20 automation rules and all analytics dashboards. After 14 days, you can upgrade to keep Pro features or continue on the Free plan.
Is there annual pricing?: Yes. Annual billing is available at a 2-month discount: Pro is $290/year (equivalent to $24.17/month), and Team is $250/seat/year (equivalent to $20.83/seat/month). Annual plans are billed upfront and renew automatically each year.
What does the Team plan minimum of 5 seats mean?: The Team plan is priced per seat with a minimum of 5 seats. If your team has fewer than 5 engineers, you still pay for 5 seats. For teams larger than 5, you pay per seat. You can add or remove seats at any time from the billing page — changes are prorated.
How does per-seat billing work? Who counts as a seat?: A seat is any user who is an active member of your Deviera workspace. Invited members who have not accepted their invitation do not count. Removing a member from Settings → Team frees that seat immediately.
What happens to my automations if I downgrade to a lower plan?: Your automation rules are not deleted, but they are capped at the new plan's limit. On the Free plan, only 5 rules can be active at once; others are paused. GitLab integration requires a Team plan — if you downgrade below Team, GitLab automation rules pause. Sentry integration requires Pro — if you downgrade to Free, Sentry automation rules also pause. Rules resume automatically if you upgrade again.
Can I change my plan mid-cycle?: Yes. Upgrades take effect immediately and are prorated for the remainder of your billing period. Downgrades take effect at the end of the current billing period so you keep access until the period ends.
Is there an Enterprise plan, and what does it include?: Yes. Enterprise includes unlimited repos, automations, and members; audit log; SSO/SAML; granular admin roles; dedicated onboarding; custom integrations; and an SLA. Pricing is custom based on team size and requirements. Contact us at the pricing page to get a quote or join the waitlist.

AI features

What AI features does Deviera offer?: Deviera includes five AI-powered capabilities: AI issue enrichment (automatically adds context, severity, and affected-service tags to created issues), signal summaries (plain-language summaries of what triggered an automation and why), natural-language automation builder (describe a rule in plain English and Deviera generates it), root-cause analysis (surfaces likely root causes for recurring CI failures), and AI PR comments (posts a short review summary on opened PRs). Issue enrichment and signal summaries are available on Pro and above; all AI features are available on Team and Enterprise.
Does Deviera use its own AI, or do I bring my own API key?: Deviera uses a Bring Your Own Key (BYOK) model. You connect your own API key from Anthropic, OpenAI, or Gemini in Settings → AI. Deviera applies no markup — you pay your AI provider directly at their standard rates. This keeps AI costs transparent and under your control.
Which AI providers are supported?: Anthropic (Claude), OpenAI (GPT-4 and above), and Google Gemini. You can switch providers at any time from Settings → AI without losing your automation configuration.

Security

Does Deviera access my source code?: No. Deviera does not request source code permissions on the GitHub App or GitLab OAuth. It receives webhook events (CI run results, PR metadata, deployment statuses) and reads repository metadata (name, branch, labels). It never reads file contents, commit diffs, or code.
Does Deviera support multi-factor authentication (MFA)?: Yes. Deviera supports TOTP-based MFA compatible with Google Authenticator, Authy, 1Password, and similar apps. MFA is available on all plans. Backup codes are generated at setup for account recovery. Team and Enterprise admins can enforce MFA workspace-wide from Settings → Security.
How are OAuth tokens stored?: OAuth access tokens and refresh tokens are encrypted at rest using AES-256-GCM before being stored in the database. They are decrypted in memory only when making an authenticated API call. GitHub App installation tokens are short-lived (1-hour JWT) and are not stored — they are generated on demand from the App's private key. Deviera also supports encryption key rotation without requiring users to reconnect their integrations.
How does webhook signature verification work?: Deviera verifies every inbound webhook using HMAC-SHA256. For the GitHub App, each installation has its own unique webhook secret — a compromised secret for one installation does not affect others. For GitLab and other integrations, a workspace-level secret is used. Requests that fail signature verification are rejected with a 401 before any processing occurs.
Is Deviera SOC 2 compliant?: Deviera is SOC 2 Type II hardened — MFA/TOTP, AES-256-GCM token encryption with key rotation, per-installation webhook verification, brute-force and rate-limit incident detection, idle auto-logout, granular admin roles, and audit logs are all implemented. Formal third-party certification is in progress. Enterprise customers can request a security review and data processing agreement (DPA). See the full security overview at /security.
Where is my data hosted?: Deviera's application runs on Vercel's global edge network. Data (database and file storage) is hosted on Supabase (PostgreSQL on AWS). Both Vercel and Supabase are SOC 2 certified providers. Enterprise customers can request data residency details as part of a DPA.
Can I export or delete my data?: You can export your workspace data from Settings → Data. Deleting your account permanently removes all workspace data, automation rules, and signal history. If you cancel a subscription, data is retained for 30 days before deletion. Enterprise customers can request a formal data deletion certificate.

Still have questions?

Our team responds within 24 hours. Enterprise and sales inquiries get a response within one business day.