HiveOps
Frontend Engineer (contract)
Multi-tenant DBaaS · 2024 to 2025 · Archived
A three-month contract owning the frontend of a multi-tenant Database-as-a-Service product. The work was translating dense Figma specs into a production component library, wiring it to a Go and Vespa backend, and shipping Stripe subscription flows. My involvement ended with the contract, and the product has since moved past what I built.
The problem
Operators need to inspect and manage database instances across tenants, and self-serve their own billing, without the dashboard becoming unusable as instance counts grow.
Architecture
- Client
- Next.js, TypeScript, Tailwind CSS. Reusable components built to spec from Figma; verified across Chrome, Safari, Firefox, and Edge.
- State
- React Query for live server state, Redux Toolkit for cross-view UI state.
- API
- REST against a Go + Vespa backend; Stripe for subscription and billing flows.
Decisions
Dashboards that stay responsive under real data volume
Lazy loading, route-level code splitting, and bundle trimming kept the data-visualisation views usable as tenant instance counts grew rather than degrading with them.
Billing is the part you cannot ship broken
Subscription state has more edge cases than it looks: mid-cycle changes, failed payments, plan limits. Cypress and Jest coverage went here first, ahead of cosmetic UI.
Outcomes
- Stripe subscription and billing flows shipped end to end
- Cross-browser data-visualisation dashboards backed by real-time APIs
- UI test coverage with Cypress and Jest on the billing paths
Built with
- Next.js
- TypeScript
- Tailwind CSS
- React Query
- Redux Toolkit
- Stripe
- Cypress
Screens
