Deviera Docs

#Getting Started

#Overview

Deviera monitors your GitHub and GitLab repositories in real time and automatically creates Linear issues, Jira tickets, GitLab issues, sends Slack messages, and logs signals whenever friction events occur — CI failures, stale PRs, flaky tests, deployment failures, and more.

The core loop is: GitHub/GitLab event → Automation rule fires → Action executes → Signal recorded. Your Friction Score aggregates all signals into a single team health metric you can track over time.

#Quick start (5 min)

1. 1Sign up at deviera.dev — free 14-day trial, no credit card required.
2. 2Install the Deviera GitHub App on your organisation (or connect GitLab via OAuth).
3. 3Select the repositories you want Deviera to monitor.
4. 4Connect Linear, Jira, or both for automatic issue creation.
5. 5Enable one of the 65 built-in automation presets (e.g. "CI Failure → Linear Issue").
6. 6Trigger a CI failure or open a PR — your first signal will appear within seconds.

#Connect GitHub

Deviera uses a GitHub App (not a personal access token) for secure, granular permissions. The app requests read access to code, metadata, checks, pull requests, and issues — plus write access to issues and pull-request comments for write-back actions.

1. 1Go to Dashboard → Integrations → GitHub.
2. 2Click "Install GitHub App". You'll be redirected to GitHub.
3. 3Choose the organisation or personal account, then select which repositories to grant access to.
4. 4After installation, return to the dashboard — Deviera will begin listening for webhook events immediately.

#Your first automation

Navigate to Dashboard → Automations → New. Pick a preset (e.g. "CI Failure Alert") or build from scratch. Every automation has up to four parts:

#GitHub Integration

#GitHub App install

The Deviera GitHub App is installed at the organisation or user level. Once installed, GitHub delivers webhook events to Deviera for every repository you've granted access to. You can update repository access at any time from your GitHub App settings.

#Webhooks

Webhooks are delivered by GitHub to Deviera's endpoint and verified using HMAC-SHA256 signatures. Supported event types:

#Monitored repositories

After installing the GitHub App, go to Dashboard → Integrations → GitHub and open the "Monitored Repositories" section. Check or uncheck repos to control which ones Deviera actively processes. Unchecked repos receive webhooks but events are silently discarded.

#GitHub write-back

All plans support GitHub write-back actions. Automations can:

• Create a GitHub Issue when a CI failure exceeds a streak threshold
• Close a GitHub Issue when CI passes again (auto-resolution)
• Post a comment on a PR when it goes stale

#Automations

#How automations work

An automation is a trigger → condition → action (→ optional second action) pipeline stored in the database and evaluated every time a matching GitHub or GitLab event arrives. Automations run asynchronously via a BullMQ job queue — webhook responses always return in <50ms regardless of action complexity.

#Triggers

#Conditions

Conditions are optional filters applied after a trigger fires. All conditions must pass for the action to execute.

#Actions

#Presets & templates

Deviera ships 65 built-in automation presets covering the most common friction patterns across GitHub, GitLab, Linear, Jira, and Slack. Access them at Dashboard → Automations → Templates. Presets can be used as-is or cloned and customised. The "For You" tab surfaces presets relevant to your connected integrations.

#Cooldowns & deduplication

To prevent alert storms, every automation has a configurable cooldown (default: 60 minutes). If the same automation fires within the cooldown window, the action is skipped and the event is logged as deduplicated.

Cross-provider title deduplication prevents two different automations from creating duplicate issues (across Linear, Jira, and GitLab) for the same root cause within a 7-day window. The dedup block is automatically lifted when the issue is closed or resolved in the external tracker — so if a problem recurs after being fixed, a fresh ticket is created immediately. When webhooks are not configured for a provider, the 7-day window acts as a fallback so long-standing open issues don't block re-firing indefinitely.

#Signal Feed

#What is a signal?

A signal is an AutomationEvent record created whenever an automation fires. It captures the trigger, the outcome (Linear issue URL, minutes saved), severity, and a dedup key for correlation. Signals are the source of truth for your Friction Score and the Value Dashboard.

#Severity levels

#Public Signal Wall

The Signal Wall is a public, read-only view of your workspace's signal activity. Enable it in Dashboard → Workspace Settings and share the URL with stakeholders or embed it in your team wiki — no login required for viewers.

#Friction Score

#How it's computed

The Friction Score is a 0–100 composite metric calculated from signal activity in the last 30 days. Lower is better.

FrictionScore = (
  (critical_signals × 4)
  + (high_signals × 2)
  + (medium_signals × 1)
) / maxExpected × 100

Signals are weighted by severity (critical×4, high×2, medium×1). Low-severity signals are excluded from the score. The score is capped at 100 and normalised against maxExpected — a baseline derived from the number of signals in the window.

#Interpreting your score

#Integrations

#Linear

Deviera uses Linear's OAuth flow to connect your workspace. Once connected, automations can create issues in any team you have access to, with custom titles, descriptions, priority levels, and labels.

1. 1Go to Dashboard → Integrations → Linear.
2. 2Click "Connect Linear" — you'll be redirected to Linear's OAuth page.
3. 3Grant access to your Linear workspace.
4. 4Return to Deviera and select a default team for issue creation.
5. 5Labels and priorities are automatically fetched from your Linear workspace.

#Jira

Deviera connects to Jira via Atlassian's OAuth 2.0 flow. Once connected, automations can create structured Jira issues with project mapping, issue type, priority, labels, and description templates. Token refresh is handled automatically.

1. 1Go to Dashboard → Integrations → Jira.
2. 2Click "Connect Jira" — you'll be redirected to Atlassian's OAuth consent screen.
3. 3Authorise access to your Atlassian Cloud site.
4. 4Return to Deviera and select a default project for issue creation.
5. 5Issue types and priorities are fetched automatically from your Jira instance.

When creating automations with the create_jira_issue action, you can configure:

• Jira project and board mapping per automation rule
• Issue type selection (Bug, Task, Story, etc.)
• Priority level (Highest, High, Medium, Low, Lowest)
• Labels — select from existing project labels
• Title and description templates with variable interpolation
• Cross-provider dedup — prevents duplicate issues across Linear and Jira

#GitLab

Deviera integrates with GitLab via OAuth 2.0, supporting both GitLab.com and self-hosted instances (configure via GITLAB_BASE_URL). Once connected, Deviera receives webhook events for pipelines, merge requests, and push events — the same signal detection engine as GitHub.

1. 1Go to Dashboard → Integrations → GitLab.
2. 2Click "Connect GitLab" — you'll be redirected to GitLab's OAuth page.
3. 3Authorise access to your GitLab groups and projects.
4. 4Return to Deviera — your groups and projects will be listed automatically.
5. 5Deviera registers webhooks on connected projects to receive events.

GitLab supports the following trigger types:

• gitlab_ci_failed / gitlab_ci_passed — pipeline completion events
• gitlab_mr_opened — new merge request created
• gitlab_mr_stale — MR with no activity (proactive scan)
• gitlab_push — code pushed to any branch

GitLab signals appear in the same Signal Feed as GitHub events, with unified repo health scoring and friction score computation across both providers.

#Slack

Slack integration uses an Incoming Webhook URL — no OAuth required. The webhook is validated before saving by sending a test ping.

1. 1Create an Incoming Webhook in your Slack workspace (api.slack.com/apps).
2. 2Copy the webhook URL.
3. 3Go to Dashboard → Integrations → Slack and paste the URL.
4. 4Click "Save" — Deviera will test the connection immediately.

#Vercel

The Vercel integration captures deployment events (created, ready, failed) via Vercel's API token. Connect once and Deviera polls or receives webhook events for all your projects.

1. 1Go to Dashboard → Integrations → Vercel.
2. 2Enter your Vercel API token (create one at vercel.com/account/tokens).
3. 3Deviera will list your Vercel projects and begin capturing deployment events.
4. 4Webhook events trigger automations for deployment_created, deployment_ready, and deployment_failed.

#API Reference

#Authentication

All API requests must include an API key in the Authorization header. Generate keys at Dashboard → Settings → API Keys.

curl https://deviera.dev/api/automation-events \
  -H "Authorization: Bearer dvr_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

#Endpoints

#Rate limits

#Billing & Plans

#Plans overview

See the full feature comparison on the pricing page.

#Trial & upgrade

All new workspaces start on a 14-day free Pro trial — no credit card required. At the end of the trial, the workspace downgrades to Free unless a paid plan is activated. Upgrade at any time from Dashboard → Billing.

#Cancel subscription

Cancel at any time from Dashboard → Billing → Cancel Subscription. Your workspace retains paid-plan features until the end of the current billing period, then downgrades to Free. Data is retained indefinitely — nothing is deleted on downgrade.