The problem
Every client has its own brand, but the basics repeat: fast pages, forms, logins, payments, bookings. Rebuilding them from scratch every time is slow, and every rebuild is another chance for the same bug to come back.
InternalPlatform
PeakQ Frontend Platform
Our own monorepo of shared components, brand theming and a CLI. It is how we ship client sites faster without cutting corners.
What we built
One monorepo of more than 50 packages: UI components, a brand theming system, motion primitives, and ready business modules for blogs, CMS, bookings, catalogues and stores, memberships and payments.
Every vendor plugs in through an adapter: Midtrans, Xendit or Stripe for payments, Claude or OpenAI for AI. Changing vendor means changing an adapter, not rewriting the feature.
How we keep it honest
The modules are tested against a real Postgres running inside the test process, not a mock. Every flow that moves money is tested end to end with Playwright.
The CLI creates a new app with the client's brand already applied in one command, so every project starts from the same foundations.
What it means for clients
Project time goes on what makes your business different, not on rebuilding logins and checkouts.
Built with
- Turborepo
- pnpm
- Next.js
- React
- TypeScript
- Tailwind CSS
- Hono
- Drizzle
- PostgreSQL
- Vitest
- Playwright
Crafts on this project
Got an idea? Let’s build it.
- hello@peakq.studio
- Based in Jakarta, Indonesia