01
Connect a tool
Connect GitHub, GitLab, Jira or Slack. An action creates a ticket or sends a message in a tool you connect, not by scanning your cloud, so you always know what it did and where.
© 2026 devguard Ltd. All rights reserved.
Connect the tools your team already works in, and an action opens a GitHub, GitLab or Jira ticket, or sends a Slack message, from a template you write. It runs on a schedule you set, or when you trigger it by hand. You see every run, with a link to the ticket it created, and you can switch any action off.
An action is a template you write that creates a ticket or a message, set to run on a schedule or when you trigger it.
Connect GitHub, GitLab, Jira or Slack. An action creates a ticket or sends a message in a tool you connect, not by scanning your cloud, so you always know what it did and where.
Write the ticket or message the action sends, then set it to run on a schedule, like every quarter, or leave it to run when you trigger it by hand.
An action is a template you write plus a schedule you set. It opens a GitHub, GitLab or Jira ticket, or sends a Slack message, so you know exactly what each run will create.
On its schedule or when you trigger it, the action creates the ticket or message, and the run shows up in the list with a link to it and the time it ran. Switch any action on or off without touching the others.
Four choices behind how actions work here, each one something you can check, not an adjective.
An action runs on a schedule you set, or when you trigger it by hand. Every trigger is one you defined, so nothing fires that you didn’t set up.
Each action opens a GitHub, GitLab or Jira ticket, or sends a Slack message, from a template you write. A run is never a black box; you see exactly what it created.
Actions are individually switchable, so you can turn one off without disabling the rest, and roll one out before you enable the next.
Recent runs show the source, the time and a link to the ticket or message they created, so at audit you can show exactly what ran and where it landed.
Hosted in Switzerland by default, in German and English, with on-premise possible. Your data and evidence are yours and exportable in full at any time, with no lock-in.
An action doesn’t act in isolation. It opens a ticket, moves a risk forward, hits a deadline or hands off to the assistant, all in the same workspace.
Let a finding open a risk and move it toward treatment.
Turn a recurring action into a dated reminder with an owner.
Capture proof and attach it to the control it satisfies.
Hand a summary or a draft to the assistant to review.
No. Actions run on a schedule you set, or when you trigger them yourself. They create a ticket or send a Slack message in a tool you connect, like GitHub, GitLab, Jira and Slack. They do not scan your cloud accounts in the background, which is why you can see exactly what every run created.
It opens a GitHub, GitLab or Jira ticket, or sends a Slack message, from a template you write. You set it to run on a schedule or trigger it by hand, and each run shows up in the list with a link to the ticket or message it created.
A treatment action remediates a specific risk or finding and is tracked to closure in the register. An integration action creates a ticket or Slack message in a connected tool, on a schedule or when you run it. Both live in the same workspace; they’re just triggered differently.
A spreadsheet won’t open a ticket for you, and many GRC tools react by scanning your cloud and surfacing alerts you then reconcile by hand. Here, an action runs on your schedule or when you trigger it, creates a ticket or message in a tool you connect, and lists the run with a link to it.
Swiss-hosted by default, in German and English, with on-premise possible. Your actions and their run history are yours, exportable to CSV at any time, with no lock-in.
Connect a tool, write the template, set the schedule, and let the action open the ticket or send the message, with every run listed so you can show exactly what it created.
