Skip to main content

What is FlowBeacon?

FlowBeacon is a governance and observability layer for workflow automation. It reads scenarios (today: Make.com; roadmap: n8n, Zapier, Power Automate), evaluates them against a catalog of governance policies (security, access control, data integrity, architecture, monitoring, cost), and produces:

  • Per-scenario violations with severity and compliance-framework mappings.
  • Module-level badges that overlay your canvas.
  • Plain-language remediation steps that link back into the scenario editor.
  • An organization-wide rollup with score, top violations, and framework coverage.

It does not mutate your scenarios. All reads are scoped to one organization.

Who is the API for?​

  • Make.com agency partners building Custom Apps.
  • Platform engineers building internal admin tools or CI gates.
  • Security engineers wiring evaluation into pre-deploy checks.
  • SOC 2 / ISO auditors who need machine-readable evidence.

What does the platform do that this API exposes?​

  • Governance catalog — 20+ policies across security, access_control, data_integrity, architecture, monitoring, cost_management.
  • Compliance mapping — every policy is mapped to one or more of SOC 2, GDPR, PCI-DSS, HIPAA, ISO 27001.
  • Module-level evaluation — violations identify the specific scenario module that triggered them.
  • Remediation generation — ordered, display-ready steps per violation.
  • Watermarked responses — every authenticated response carries an opaque watermark for leak tracing.

How does this compare to…​

  • Policy-as-code tools (OPA, Rego) — FlowBeacon ships an opinionated catalog. You consume policy results; you don't write policies. Custom policies are a roadmap item for enterprise plans.
  • Generic API gateways — those secure your APIs; FlowBeacon governs the automation logic itself.
  • APM / observability — those track runtime; FlowBeacon evaluates the design of the workflow before it runs.
Last updated on