Skip to content

Engineering / Software Delivery · Preview

Understand how changes reach production.

Connect delivery evidence to five DORA metrics for one service at a time. See the deployments, incident classifications and gaps behind each result.

Open Software Delivery

Sign in to your workspace, or create an account. An owner or administrator sets up collection. Review access and billing.

Five measures. Visible evidence limits.

Frequency and lead time use GitHub or GitLab deployment records. The remaining metrics need incident evidence and explicit deployment links; without that evidence, they stay unknown.

Deployment frequency
Successful production deployments per week, with the underlying deployment count.
GitHub · GitLab
Change lead time
Median commit-to-production time, with p75/p90 and explicit commit-history gaps.
GitHub · GitLab
Failed deployment recovery time
Impairment to recovery for deployment-caused incidents. Closing an issue or completing a rollback does not prove recovery.
GitLab incident evidence required
Change failure rate
The share of deployments explicitly linked to production impairment. Unrelated outages are excluded.
GitLab incident evidence required
Deployment rework rate
The share of deployments explicitly identified as unplanned corrections to production incidents.
GitLab incident evidence required

Automate collection. Review ambiguous incidents.

Opted-in services collect evidence through the existing integration sync. GitLab incident collection requires separate consent. Explicit automation labels can supply incident classifications; owners and administrators can record audited corrections. A changed source record makes a previous review stale.

WardBee distinguishes source assertions from human reviews. A nearby deployment, a “hotfix” label or an issue closing is never enough to infer causality or recovery.

Start with a clear scope

This preview supports up to three services per connection, each with one repository and production environment. Snapshots cover up to 60 days. Provider history reads are bounded to 500 deployment records; larger or incomplete histories are reported as unavailable or partial.

AWS ECS runtime confirmation and PagerDuty/Jira incident collection are planned and are not available here. Delivery metrics do not change compliance control decisions or create a certification or performance ranking.

What's new · v1.0.0

ScanComb and WardBee 1.0: compliance checks, TISAX and SOC 2 readiness, and a new public site

This is the first release of ScanComb and WardBee. WardBee brings automated compliance checks, framework workspaces, reports and task tracking for engineering, security and compliance teams. scancomb.com adds free checks and a TISAX readiness check, plus guides and news.

Highlights

  • TISAX readiness check Answer a public questionnaire and get a free readiness score by email. A paid report adds findings, an action plan for each chapter, a roadmap and a PDF. You can import the gaps into a WardBee workspace as tasks.
  • Dedicated TISAX section in WardBee Manage TISAX in one place. Set the scope, keep a self-assessment register, follow an action plan with tasks, track audits and labels, and manage suppliers and exports.
  • SOC 2 readiness Work through a readiness questionnaire, criterion guidance, a policy pack and reviews. Criteria are explained in plain words and questions can be answered in the side drawer. You can download a SOC 2 readiness report as a PDF.
  • Sovereignty Profile free check Run the free Sovereignty Profile check and get a report. The scores are explained in plain words.
  • Projects with a shared scan pool Run several projects or clients in separate workspaces that share one pool of scans. A For consultants page explains the setup.

Improvements

  • Resource inventory See an inventory of your resources with filters, saved views and notifications.
  • EU Cyber Resilience Act support Prepare for the EU Cyber Resilience Act with product classification and a continuous technical file.
  • NIS2 Supplier Check Assess suppliers against NIS2 with the NIS2 Supplier Check.
  • Free AI security check and AI Shield playbooks Take a free AI security check and read practical playbooks on AI agent permissions, prompt injection, shadow AI and more.
  • Manual control verification Verify controls that cannot be checked automatically, using a clearer drawer for manual controls.
  • Clearer controls and findings Findings and resource names are easier to read, you can filter to checks-only scans, and you can compare one scan with the previous one.
  • Faster control and dashboard pages Controls, the dashboard and risks load faster. App pages show a loading state right away.
  • Better start for new workspaces New workspaces start with ISO 27001 and SOC 2, with an explanation of what scans do. If no frameworks are chosen, a Choose frameworks step guides you.
  • Support tickets, announcements and notification bell Open support tickets inside WardBee and get email updates. Announcements appear in a header bell.
  • New site design, menu and guides scancomb.com has a new look and a grouped menu with News, Free checks and Guides. WardBee uses the same visual style, and the in-app docs are task-focused guides.
  • What's New and Framework Watch A What's New dialog shows release notes on scancomb.com. A weekly Framework Watch news issue is also published.
  • Team invitations and two-factor sign-in Invite teammates by email with consistent role names. Two-factor setup includes a QR code.

Fixes

  • Security improvements to sign-up and sign-in Sign-up and sign-in are now better protected.
  • More accurate AWS multi-factor authentication checks All MFA device types are now recognized, and users who only use programmatic access are no longer flagged.
  • Confirmed failures are shown correctly A confirmed failure now outranks an error in a control's status.
  • One critical-control email per scan You now get a single critical-control email per control for each scan.
  • Smoother onboarding and failed checks Workspaces without frameworks are sent to setup. Checks that fail are refunded, and queued checks show as Queued.
  • Correct access errors Signed-out or unauthorized requests now get a proper access error instead of a server error.