← Back
App #1505 · 🇩🇪 Germany
Disaster score 570Legendary
Procurement built a custom password manager, somehow
✨ Friday deployment☠️ No known owner🧟 Builder has left🕸️ Load bearing
Users2
Departments0
Criticality12%
Money involved€550/yr
“We'll document it after the quarter.”— Group Controller
- Reason:
- Honestly? Because the meeting to fix it created 3 more meetings. With a logo generated at 23:14.
- Built by:
- Sarah, someone from Procurement
- Build time:
- an afternoon, mostly
- Built with:
- a webhook pointed at someone's ngrok tunnel
- Database:
- one table called everything
- Authentication:
- the audit log records "something changed"
- Deployment:
- deployed straight to production on a Friday, no staging
- Responsible:
- an external agency with no contract on file
- Documentation:
- a Slack thread from March
- Security situation:
- the pentest report is still marked draft
- Future disaster:
- It will be migrated into SAP and then quietly migrated back.
Accidentally connected to (6)
- → polls the API every 8 seconds
- → depends on a SharePoint list
- → depends on LibreOffice rendering the spreadsheet correctly
- → uses the same API key in test and production
- → depends on a vendor account nobody can log into
- → depends on a firewall rule labelled TEMP
⚠️ Removing this app may now destroy the company.
Age: 16 days · originally expected to last 3 weeks · 2 owners so far · last meaningful change 16 days ago · original builder left 38 days ago
Rated legendary mostly because: 6 accidental connections, nobody owns it, the builder has left.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility