Risk & controls
Connect GRC and audit data on Supabase, build audit and operational risk dashboards, and ask questions about findings, KRIs, and vendor risk — modeled on Veridian Group.
2 to build
Dashboard + chat
Internal audit, Risk management
Vizkraft — Risk & controls
Works with
Pick whichever connector your team already uses.
What it does
Brings audit findings, risk register entries, KRI readings, SoD conflicts, and vendor assessments into dashboards and chat. Built for GRC teams who need committee-ready views without a separate analytics project.
How it works
- 1
Connect Supabase
Add a hosted PostgreSQL connector pointed at your GRC schema on Supabase.
- 2
Index GRC tables
Mark audit findings, controls, risk register, KRIs, vendors, and SoD conflicts during indexing.
- 3
Ask audit and risk questions
Try "How many open audit findings do we have by severity?" or vendor tier breakdowns.
- 4
Build committee dashboards
Create audit findings overview and operational risk exposure views for leadership reviews.
Dashboards to build
Audit findings overview
Open vs. closed findings, severity mix, and aging.
Operational risk exposure
KRI breaches, SoD conflicts, and high-scoring risks.
Questions to try
- “How many open audit findings do we have by severity?”
- “What is the breakdown of vendors by risk tier?”
- “Show control test pass and fail counts by month for the last year.”
Setup
- Connect Supabase (or PostgreSQL) with your GRC and audit schema.
- Mark the 13 core tables during indexing per the cookbook.
- Define risk score and KRI breach rules in connector memory.
Related cookbooks
PostgreSQL or MongoDB
E-commerce / D2C retail
Connect retail data, build five dashboards, and ask revenue, marketing, and support questions — modeled on a D2C brand like ShopNova.
PostgreSQL
B2B SaaS
Connect subscription and product usage data, build four dashboards, and track MRR, retention, and trial conversion — modeled on CloudFlow.
PostgreSQL
Fintech / payments
Connect payment and merchant data, build four dashboards, and monitor volume, fraud, and settlements — modeled on PayStream.
Stop waiting on engineering for reports.
Most of our customers were ops or CS leads who'd been blocked for weeks. They booked a demo, connected their database in 10 minutes, and never looked back.