000
Compiling the experience

Case study 03 — Architecture decision

Choosing Next.js for a multi-store SaaS platform

A written technical comparison that supported the team's decision to build KoninPay on Next.js.

Company
Konin Cloud
Role
Senior Frontend Developer
When
May 2023 — Sep 2025
Stack
React, Next.js, TypeScript

( 01 ) — Context

Konin Cloud's KoninPay is a multi-store SaaS platform: merchant and store creation, platform operations, payment workflows and a dedicated digital wallet. I was a Senior Frontend Developer, remote.

The challenge

The initial plan was HTML, Sass and Blade, for a product that had to scale and keep evolving.

( 02 ) — The options

Two ways to go.

Option A

HTML, Sass and Blade

The initially proposed approach.

What we went with

Next.js

Components, server rendering with per-page metadata, and room for the product to grow.

( 03 ) — What I did

01

Advocate, with reasons

I advocated Next.js, focusing on scalability, maintainability, development efficiency and long-term product evolution.

02

Write it down

I wrote a technical comparison of both approaches: architectural differences, advantages, trade-offs and maintainability, so the team could decide on evidence.

03

Make the SEO case

Storefront product pages needed proper titles and link previews. With Next.js they render on the server with their own metadata.

The result

The comparison supported the team's technology decision. Product pages became shareable and indexable, and seven live storefronts run on the platform today.

ReactNext.jsTypeScriptMaterial UIREST APIsReact Testing Library

Lesson: A written comparison persuades better than an opinion, especially for people outside frontend.

( ✦ ) — Related

More from Konin Cloud.

What it adds up to

Strengths→