ComplianceBot

ComplianceBot is a concept for continuous compliance software — the category of tool that helps companies stay audit-ready for frameworks like SOC 2 and ISO 27001 year-round instead of scrambling before an audit. The site is explicit throughout that it makes no real certification or audit claims.

Compliance software lives or dies on trust, which is a strange thing to fake convincingly in a portfolio demo. The challenge was building something that reads as genuinely operational — live checklists, evidence chains, a risk heatmap — while being unmistakably honest that every figure shown is simulated.

Surface what is overdue, what is at risk and what is resolved at a glance, so a compliance officer's first action is never a search.

I built the story around a control's full lifecycle — signal, control, evidence, readiness, trust — expressed as an evidence chain a visitor can click through node by node, backed by a readiness snapshot (SOC 2 / ISO 27001 percentages), a filterable control checklist, and a scoped auditor-portal view showing only what an auditor would actually need.

A clean, structured dark UI with status-coded controls (ready, attention, overdue) that reads like real compliance tooling, with a persistent "demo environment" label so the simulated nature of the data is never in doubt.

Built with semantic HTML5, modular CSS and vanilla JavaScript. Every readiness percentage, evidence count and redaction example on the site is demo data — the footer states plainly that no certifications, audits or security claims made on the site are implied to be real.

A compliance-software concept that demonstrates how continuous readiness tracking could be visualized and interacted with, while being unambiguous — in its footer and throughout — that no real certification, audit or security claim is being made.

Workflow software should make the next required action obvious at every screen — compliance interfaces fail when the user has to go looking for what's overdue.