Production debugging block
A time-boxed engagement for teams whose Node.js service is failing, slowing, or corrupting data in production—or whose last rollback did not restore confidence.
Who this is for
Back-end leads, SREs, and founders who already have logs and metrics but lack bandwidth to isolate whether the fault sits in application code, dependency upgrades, queue workers, or infrastructure tuning. We work best when at least one engineer who deployed recently can join the session.
What you receive
- Minimum four contiguous hours (extendable same day if calendar allows)
- Live pairing on repro, profiling, and patch validation
- Written summary: symptom, root cause hypothesis, confirmed cause, and recommended fix with risk notes
- Optional 30-minute follow-up call within five business days to review merged fix
What we need from you beforehand
- Read access to the repository branch in question
- Log or trace samples covering the failure window (no customer PII in tickets—redact first)
- A single primary contact empowered to restart workers or approve hotfixes
Out of scope
Greenfield application builds, full rewrites, penetration testing, and 24/7 on-call coverage are separate arrangements. We may decline engagements without sufficient observability until basic health endpoints exist.
Delivery
Remote via screen share (default) or on-site at 92 Florida Road,Durban,KwaZulu-Natal,4001 for Durban-based teams. Sessions typically start within two business days of signed scope and deposit.
Pricing basis
ZAR 6,800 per four-hour block, prepaid. Additional hours billed at ZAR 1,750 per hour in 30-minute increments. Travel outside eThekwini quoted separately.