Nexus Orchestrator — a multi-tenant workflow-automation app for building, triggering, and monitoring automations end to end. built solo, phase by phase, with a test suite gating every phase before the next began.

The trade-off was adding a recursive-scan redaction pass (checking every nested object key against sensitive-name patterns: authorization, api_key, token, secret, password, cookie, session, etc.) to every Sentry event/breadcrumb and audit-log write — worth it because it's the only guard against secrets or PII leaking into third-party tooling or the persisted audit trail, which the production-readiness checklist explicitly requires verifying before launch.

The trade-off was routing all browser-side Sentry traffic through a same-origin proxy instead of calling sentry.io directly — a choice the code comment itself flags as something that 'can increase your server load as well as your hosting bill' — worth it because ad-blockers otherwise silently drop client-side error reports, so this is the only reliable way to capture real user errors.

The trade-off was checking the payload size twice — once cheaply against the declared Content-Length header, then again against the actual byte length after reading the full body — worth it because a spoofed or missing Content-Length header would otherwise let an oversized payload slip past the first, cheaper check.