RedKit flows
Draw your own security checks as a flow and run it on your verified domains, by hand or on a schedule. Under RedKit > Flows, on every paid plan.
- A full-page editor: drag blocks from the palette, link them, and open any block to set it up and see what it takes in and gives out, with examples.
- HTTP, DNS, port and TLS checks, each one stating what it expects; a check that cannot run can be retried and sent down its own error path.
- Conditions on severity, count, title or anything a check recorded, a severity switch, and references such as {{target}} or a check's facts in any text.
- Five templates to start from: mail hygiene, web exposure, certificates expiring, exposed admin ports, and a quick perimeter check.
- Only your verified domains can ever be targets, and never one that resolves to a private address.
Schedules, versions and run history
Flows run on their own and you keep track of every change and every run.
- Run a flow every day or every week, on all your verified domains, those with a tag, or those of a given criticality.
- Save a draft as you work and publish it when it is ready; roll back to any earlier version.
- Every run is kept: open one to see what each block did, what it found, and what changed since the previous run.
- Run again in one click, test a single check on a domain before running the whole flow, and pin its result to build on.
- Alerts and cases can act on what is new only, so a schedule never repeats itself.
Transform, combine and reuse
Shape what the checks found before acting on it.
- Filter findings by severity or title, remove duplicates, merge branches and count what is left.
- Skip what you accepted: a finding set aside in your exceptions register is dropped from the run, with the same rules and audit as a vulnerability.
- Run a flow inside another: reuse Mail hygiene as one block in a bigger flow.
- Capri triage: Capri sorts the findings most urgent first and writes a summary and recommendations, on your AI tokens. It never drops a finding and never stops the flow.
Flows act through your integrations
Output blocks use what your organization already set up in Alerting.
- Send an alert to your webhooks and email rules, or open a case.
- Open a GitHub issue or a Jira ticket in a repository or project you connected.
- Trigger a PagerDuty incident; runs on the same domain group into one incident.
- Call one of your webhooks, signed, its address checked again before each call.
- Write a report of the run, to download as Markdown or PDF.
Flows in the API and for AI agents
Build, change and run flows from your own tools or from an AI agent.
- Read the block catalog, check a flow without saving it, create, import, update, publish and run flows, and read their runs.
- Three API key permissions: read flows, run flows, and create and edit flows. Editing is never part of full access: tick it by name.
- AI agents connected over MCP get the same tools. Writing and running flows stay off until you turn them on in Account settings, MCP.
- Export a flow as a JSON file and import it in another organization. No key and no agent can delete a flow.
A dashboard and a monthly allowance
See how your flows do, and how much of your plan they use.
- Over the last 30 days: runs and success rate per flow, findings found and still open, and the median time to fix.
- Each plan includes flow runs a month: 300 on Pro, 3,000 on Team, 30,000 on Enterprise, with checks, domains and time per run growing with the plan. See Pricing.
- A notice when 80% of the month is used. A schedule that cannot run is shown in the flow's history with the reason, and the allowance resets on the 1st.