63 articles published

A hosting platform should never put its own credentials inside your application, and never make you guess which ones yours needs. We got the first half right and the second half wrong.

Clients earn a real discount by taking part in their project. We measured what was actually reachable and got 5%. Six of sixteen rewards could only be earned by our own staff.

We found a confirmation dialog whose entire body was `return null`, imported by 118 files. Every destructive control in the platform silently did nothing — and every automated check we had passed.

What's coming: real-time WebSocket streaming for deployments, CRM analytics dashboards, multi-tenant improvements, and the trading bot project.

How we test at Boottify: TDD workflow, Playwright for E2E, 4-phase systematic debugging, and the RED-GREEN-REFACTOR cycle enforced at every commit.

Boottify's TypeScript codebase: 248,564 lines, 1,677 files, zero 'any' types, 165 Zod validation files, and 516 safeParse() calls. How we maintain strict mode at scale.

A technical walkthrough of the Agencies CRM: 20+ API routes, 7 database tables, Kanban pipeline, ML duplicate detection, email sequences, and analytics.

How Boottify's auth works: Lucia v3 sessions, Google/GitHub OAuth via Arctic, TOTP 2FA with backup codes, 15-minute idle timeouts, and role-based access.

How Boottify runs on K3s with Traefik ingress, Let's Encrypt DNS-01 challenges, and Hetzner bare metal. Zero CloudPanel, zero Nginx.

ForgeHub meets Boottify billing: payment-first provisioning, Stripe confirmation before deployment, and no deployment record until payment clears.

Behind the scenes of Boottify's blog: Prisma-seeded posts, A2E-generated cover images, editorial typography passes, and responsive WebP thumbnails.

Dark, sharp, typographic. How we built Boottify's cyber-industrial design system with 0-2px corners, one accent color, and uppercase geometric headings.