HexLabs

Appearance

👋 Welcome, Developers! ​

This section is for the engineering team and anyone brave enough to peek under the hood.

Speed is our default. Precision is our discipline.

We move fast by mastering our tools, automating ruthlessly, and sticking to a consistent stack that scales. No trend-chasing. Just results.

🧱 Tech Stack Overview ​

A consistent stack means faster onboarding, better collaboration, and fewer WTFs at 2AM. Until we hit a real limitation (rare), we stick to what works — and we learn it deeply.

Here’s what powers our operation:

  • Nuxt – The frontend framework we build everything on.
  • Nitro – Nuxt’s server engine. Used for APIs, microservices, and scheduled jobs.
  • Firebase – Auth, Firestore, Storage, Functions, Hosting. Out of the box and battle-tested.
  • TypeScript – Static typing across the entire stack. Strict mode. No exceptions.
  • Nx Monorepo – Manages our monorepo, dependency graph, caching, and CI workflows.
  • Stripe – Payments, subscriptions, billing logic.
  • Arktype – Runtime validation with static inference. The brains behind our form schemas.

🖥 Frontend ​

  • Nuxt – Fast, flexible, and SSR/SSG-friendly.
  • Vue 3 – Composition API all the way.
  • Pinia – For global state when needed. Usually not needed, thanks to Nuxt’s useState().
  • Arkform – Our custom-built form library. Small, powerful, fully typesafe.
  • Arkfire – Internal Firebase Nuxt module. Handles connection, emulator setup, and provides a typed Firestore ORM.

🧠 Backend ​

  • Firebase – Auth, Firestore, Storage. Scales with us and gets out of the way.
  • Nitro – Used for all server-side logic: API routes, microservices, schedulers.
  • Custom Services – Email, PDF generation, job scheduler, etc. Modular, isolated, and growing steadily.

⚙️ Tooling ​

  • Nx – Manages all projects, libraries, builds, and tests from a single workspace.
  • TypeScript – Strict mode. Full send.
  • Vitest / Cypress – For unit and end-to-end testing. Nuxt-native, fast, and modern.
  • ESLint + Prettier – Enforced. Automatically. Always.

Style ​

Return types for the win. We have tools built around using them effectivly, giving us rich and predictable errors.

📚 Docs Etiquette ​

  • Keep things clear and concise.
  • Write like the next dev has no context — because they probably don’t.
  • If you fix a “WTF” moment, document it. Future-you will thank you.
  • Keep sections organized — treat these docs as a living, evolving resource.
  • Full documentation for internal libraries, patterns, and edge cases lives in the Libs section.
  • Undocumented code = technical debt. Don’t leave it behind.