Canonical demo build — fictional product
LogPilot: compliance log retention for small MSPs
LogPilot is fictional. Every product, feature, integration, security, customer, and comparison fact on these pages was invented for this demo and must never be reused as a real claim.
Set retention per client at 30, 90, or 365 days with immutable retention locks, then export to CSV or JSON when the auditor asks. Per-client workspaces keep one client's policy from leaking into another's.
LogPilot integrates with six verified platforms, listed with their scopes on the integrations page — and nothing that is not verified.
Who this is for, and who it is not
Built for managed service providers with 5–50 technicians preparing client audits. If you need SIEM-scale analytics or real-time correlation, LogPilot is the wrong tool — it retains and exports, it does not correlate or alert. That boundary is a sourced fact, not modesty.
How this demo was built
These pages execute the B2B SaaS build playbook: the site type where invented integrations, security claims, and competitor superiority language are the dominant failure mode. The source chain is preserved (demo-logpilot-discovery.md → demo-logpilot-facts.json → demo-logpilot-page-brief.json), two claims proposed at intake are blocked in the ledger, and the machine-readable record is at /demo-build.json.
Demo routes
- Product: capabilities and explicit boundaries.
- Use cases: buyer and workflow mapping.
- Integrations: the six verified platforms only.
- Comparison: dated factual differences with caveats.
- Schema endpoint: machine-readable demo facts with claim IDs.