Website and Service Portal for Zenstrom

Zenstrom needed more than a marketing website. It needed a usable service portal for real customer workflows. I independently built and operated the public website and authenticated service portal as two Astro products with React/Svelte, PWA capabilities, ArangoDB, the Lumenaza API, and AWS SNS.

The important part was connecting product surface, integrations, and operations: tariff calculator, registration, login, password flow, customer data, invoices, meter readings, and portal communication had to work together reliably. Woodpecker CI, Vitest, Cypress, Ackee, Bugsnag, and clear deployments kept quality and runtime behavior visible.

• Website: Astro SSR/CSR, tariff calculator, registration flow, SEO, sitemap, robots.txt, and performance work
• Service portal: Auth flow, password reset, customer data, invoices, meter readings, and active contract checks
• Integrations: Lumenaza API, ArangoDB, AWS SNS, Slack notifications, Ackee analytics, and HubSpot-adjacent flows
• Operations: Woodpecker CI, staged deployments, Traefik, monitoring, error notification, and portal noindex rules
• Built-in quality: Vitest, Cypress E2E, form validation, API error handling, and security-relevant password hashes with Argon2

• Product and operations together: Treat website, service portal, API integration, and deployment as one product system
• Kanban as a visibility model: Keep work, blockers, and next decisions inspectable
• Built-in quality: Bring tests, performance work, password hashing, error handling, and noindex rules into delivery early
• Keep architecture decisions small: separate codebases, clear portal boundaries, and direct integrations only where they carry product value
• Knowledge transfer: Treat documentation, maintenance recommendations, and client training as part of handover readiness