If your production environment fails to render PDFs while your local machine handles them effortlessly, you're experiencing one of full-stack development's most classic container traps. This week inside JarvisOS, our proprietary operating system running our studio and apps from East London, South Africa, we hit this exact wall and pushed through to 69 passing end-to-end checks on our new Client Journey Engine.
The Problem with Cloudflare Containers and Headless Browsers
We relied on standard system browser dependencies for document generation. On our staging servers, it looked pristine. In production, every PDF and PNG render crashed because the minimal Cloudflare container lacked the necessary bundled Chromium binaries.
We solved it by baking a bundled Chromium instance straight into the container spec. Suddenly, generating a P1b agreement from a client's chosen option, attaching e-signature tokens, and embedding PayFast deposit links happened reliably in milliseconds.
Inbox Deduping and State Machines
When you're running lean, administering client portals, publishing essays, and managing outreach pipelines, context switching kills your throughput. We built twin-row resolution for our inboxes: answering a lead or comment in one lane automatically propagates across its duplicates. We also migrated enquiry and portal alerts into a shared Email Kit and gateway, backed by a comprehensive email design audit covering 42 send sites and 3 distinct design systems.
// Journey card auto-close state trigger
export function handleOwnerAction(journeyId: string, actionType: 'approve' | 'countersign') {
const card = fetchJourneyCard(journeyId);
if (card.status === 'pending_owner') {
card.status = 'active_execution';
card.closedAt = new Date().toISOString();
persistJourneyState(card);
}
}
Engineering is ultimately about building systems that protect your focus. By tightening our CI pipelines, retiring dead SOW workers, and automating our morning briefs, we keep the machine quiet so the actual work can breathe.
Top comments (0)