Who
Operators who opened Hustle Launch product landers after packs flagged DEPLOYMENT_NOT_FOUND and found no live Vercel host.
What
Closed the restore batch across the hustle* suite and put *.vercel.app hosts back online:
- hustledesk-com#1 - https://hustledesk-com.vercel.app
- hustlecrm-com#1 - https://hustlecrm-com.vercel.app
- hustleconvert-com#1 - https://hustleconvert-com.vercel.app
- hustlechat-com#1 - https://hustlechat-com.vercel.app
- hustleforms-com#1 - https://hustleforms-com.vercel.app
- hustlemail-com#2 - PostCSS @tailwindcss/postcss fix plus https://hustlemail-com.vercel.app
Git-linked Vercel prod and Ship wiring where needed. Custom DNS stays a separate overnight park.
Where
Repos under the hustle* product set. Live review surfaces are the vercel.app hosts above.
When
September 8, 2026 evening ET: restore issues closed; packs that read DEPLOYMENT_NOT_FOUND now resolve.
Why
A lander with no deploy is a dead demo. vercel.app hosts unblock review while custom DNS waits.
Would you point custom DNS next, or smoke each vercel.app host against the pack checklist first?