Enterprise platform architecture

The business context

Floranow is a cross border B2B floral supply and cold chain business, sourcing from Kenya, Holland, Ecuador and Thailand into the GCC. The platform carries eleven applications across that footprint: eight Next.js web applications and three React Native applications, sustained by a two engineer frontend team.

The problem

A growing portfolio, a two person frontend team, and every new application solving again authentication, HTTP, UI, configuration and CI from scratch.

The decision

A single workspace with a shared package layer, so a new application inherits single sign on, typed backend access and quality gates on day one.

The result

Seven of eight applications scaffolded onto that platform, three of them within a single fortnight.

The governance

Contract driven integration: backend interface specifications are version controlled and types are generated rather than hand written, so a contract change breaks the build instead of production.

The durability

Written operating rules that let AI agents and backend engineers work safely in the workspace, plus a handover guide and a contract map.

Architecture view

Business domain: a cross border cold chain sourcing from four origins into GCC customers. Data domain: backend interface specifications held under version control, with types generated rather than hand written. Application domain: eleven applications, eight web and three mobile, sustained by two engineers. Technology domain: a single workspace with a shared package layer carrying single sign on, typed backend access and quality gates.

As Is: every new application solving again the same five concerns. To Be: a new application inheriting all five on day one. Governance: contract driven integration, written operating rules, a handover guide and a contract map.