Overview & core concepts

What the platform is, the tier model, and how storage degrades gracefully.

Passwordless OTP sign-in, the limits that apply, and disposable-email handling.

Plans, prices & quotas

Every SKU and quota, read live from the platform catalog.

Every tool on the platform, grouped by category, listed live from the catalog.

Multi-tenant log ingestion, detection and AI triage — with API examples.

QR enrolment, the installable PWA, posture signals and fleet reporting.

Website monitoring & agent

Register a site you own, prove control of the domain, install the PHP agent, and watch events arrive.

Seats, invitations, and the Team Security Center.

Free modules, progress sync, AI tutor, and verified certificates.

Authentication, every endpoint, rate limits and status codes.

Security & privacy model

What is never stored, the defences in force, and how to report a vulnerability.

Quick reference (printable)

Every tool on one page: tier, what it takes, whether it uses AI, and whether it stores anything.

What each panel means: usage, quotas, pack balances and account state.

The problems users actually hit, and what to do about each.

How prepaid passes work, what expiry means, receipts, and where the binding terms live.

// tool reference · Governance & Advisory

AI DevSecOps Automation Pro

Explainable CI/CD security gates with an aggregated release verdict.

Open AI DevSecOps Automation →

What it does

Designs pipeline security: where to place SAST and DAST, how to gate on severity, secret scanning, and supply-chain controls — without turning CI into a 40-minute wait.

When to use it

Adding security to CI; deciding what should block a merge versus warn.

Inputs

Field names are the actual form parameters, verified against source.

Field	Type	Required	Notes
format	select	optional	Pipeline platform.
max_critical	number	optional	Gate threshold.
allow_secrets	checkbox	optional	Allow-list behaviour for secret scanning.
authorized	checkbox	required	Authorisation confirmation.

What you get back

A pipeline design with gates and rationale.

Worked example

Input

format = GitHub Actions   max_critical = 0

Output (abridged)

PIPELINE DESIGN

PRE-COMMIT (local, seconds)
  - secret scan. The cheapest place to catch a key is before it exists
    in history. After a push, rotation is the only remedy.

PR (blocking, target <5 min)
  - SAST on the DIFF, not the repo. Full-repo SAST on every PR is how
    teams learn to skip the pipeline.
  - Dependency audit -- fail on CRITICAL (max_critical = 0).
  - IaC scan if infra/ changed.

MAIN (non-blocking)
  - Full SAST, DAST against staging, container scan.

GATE RATIONALE
  Block on: criticals, secrets, KEV-listed dependencies.
  Warn on:  everything else.
  A gate that blocks on 'medium' gets disabled within a month. A gate
  nobody disables is worth more than a strict one nobody runs.

How it works

AI generation over a DevSecOps reference model.

Limits

Read live from the platform configuration.

Rate limit

30 requests / 60s (platform default)

Limitations — what it does not do

A design, not a working pipeline. It cannot see your build times or flakiness -- tune thresholds against reality before enforcing them.

Privacy

Sent to the AI provider.

Standards

OWASP DevSecOpsSLSA conceptsNIST SSDF

← All tools Manual home