What is shadow IT? The tools your team built because it had to
A critical process one person runs from a personal spreadsheet. Correctly, most days.
Security and compliance
Questions this topic answers
Explainer
6 articles
Why internal tools become production risks
A tool built as a side project ends up running a core process, with no access control, no audit log, and no owner.
What it costs to build a production-ready internal tool
Screen count barely moves the price. Scope, integrations, access rules, and audit requirements do.
Four controls that make an internal tool safe to rely on
Access control, audit trails, separate environments, and change management, and what each one prevents.
Custom code on the new Retool, with the controls IT asks for
What changed in Retool for teams that need custom code and still have to pass an IT review.
What your security team will ask about low-code, and the answers
Access control, data exposure, integrations, and compliance: the four questions every low-code review comes back to.
How-to
1 article
The security and compliance checklist to run before buying low-code
RBAC, audit logging, encryption, SSO, and the compliance frameworks to check before a low-code platform reaches procurement.