<- BACK TO WORK DIRECTORY
● CLIENT WORK

Live Deployed Application: This platform is deployed and live. You can launch the interactive system directly via the Live System button above.

Organization Project

Central Calculator Engine

A single, centralized source of calculator logic and shared UI components, powering embedded tools across 350+ client websites.

Next.jsTypeScriptNode.jsREST APITailwind CSS
arch://central-calculator-engine
1 engine → 350+ sites
fix once, ship everywhere
-70% duplicate code
01 // ORIGIN & CONTEXT

The Backstory

Why this system was engineered, what existed previously, and the core operational bottlenecks it solves.

Before this engine existed, every website that needed a calculator (loan EMI, tax, unit conversion, and dozens of other tools) shipped its own copy of the logic — meaning the same formula could exist in 350 slightly different states across the site network.

The Central Calculator Engine centralizes every calculator's logic and UI components into one app that other sites consume, not copy. A rate change, a formula fix, or a new calculator type ships once and is live everywhere it's embedded.

02 // HUD.TELEMETRY & BENCHMARKS100% PRODUCTION VERIFIED
● ACTIVE
350+
Connected Websites
● ACTIVE
1
Single Source Engine
● ACTIVE
99.9%
Service Uptime
● ACTIVE
-70%
Duplicate Code Removed
03 // PROBLEM SPACE & ARCHITECTURAL REMEDIATION
[DEFECTS & BOTTLENECKS]

The Challenge

  • 01.Calculator logic was duplicated across dozens of independent codebases, with no guarantee any two copies matched.
  • 02.No shared design system for calculator UI, causing inconsistent look-and-feel across properties.
  • 03.Adding a calculator to a new site meant rebuilding it from scratch, including edge cases already solved elsewhere.
  • 04.No central place to update rates, formulas, or business rules used across multiple calculators simultaneously.
[ENGINEERED REMEDIATION]

The Solution

  • 01.Extracted every calculator's logic into a single centralized service with versioned, reusable modules.
  • 02.Built a shared, themeable component library so every embed looks and behaves consistently regardless of host site branding.
  • 03.Exposed the engine through a lightweight embed contract so any site can integrate in minutes, not days.
  • 04.Centralized shared config (rates, constants, formulas) so one update propagates to every consuming site.
04 // SYSTEM ARCHITECTURE

Modular Capabilities

MODULE 01
Single source of truth

Unified Logic Layer

One implementation per calculator type, consumed everywhere instead of forked per site.

MODULE 02
Reusable across sites

Themeable UI Components

Components accept a theme/token set so each site's branding still looks native.

MODULE 03
Fast integration

Lightweight Embed API

New sites integrate via a small config object and script/embed tag.

MODULE 04
Rates & business rules

Centralized Config

Shared constants live in one place and cascade to every calculator that uses them.

MODULE 05
Safe rollout per site

Versioned Modules

Sites can pin to a version and upgrade on their own schedule.

MODULE 06
Zero duplication

Horizontal Scale

Adding calculator #40 doesn't mean copying calculator #39's infrastructure.

05 // ENGINEERING SPEC

Technical Deep Dive

~/architecture/spec.ts
TYPESCRIPT 5.x
01.

Each calculator is a self-contained module exposing a typed input/output contract, so consuming sites get compile-time safety on what a calculator expects and returns.

02.

Shared constants (interest rates, tax slabs, conversion factors) are stored centrally and fetched at build/runtime depending on how volatile the value is — static values are baked in at build for speed, frequently-changing ones are fetched live.

03.

The embed layer ships as a lightweight script + config pattern rather than an iframe, so calculators inherit the host page's fonts and can be styled with the site's own theme tokens instead of looking like a foreign widget.

04.

Versioning is handled at the module level, not the whole engine — a site can stay on an older EMI-calculator version while picking up the latest tax-calculator update, avoiding forced all-or-nothing upgrades.

06 // INTERFACE SCHEMATICS

Project Gallery

07 // VERIFIED IMPACT

Business & Velocity Value

Direct outcomes, architecture speedups, and developer feedback delivered in production.

One engine, one fix, 350+ sites updated at once.
08 // ENGINEERING LESSONS

Post-Mortem Takeaways

TAKEAWAY 01

Centralization Compounds

Maintenance savings grow with every additional consuming site.

TAKEAWAY 02

Contract Design Matters

A well-designed embed/API contract is what makes 350+ integrations possible without one-off code.

TAKEAWAY 03

Version Discipline

Careful, module-level versioning prevents one site's update from silently breaking another's calculator.

🔒
Access Note

Underpins live client websites. Links above are placeholders — real URL to be added once cleared to share.

● OPEN FOR ENGINEERING PROJECTS

Have a similar project in mind?

Let's build a scalable, high-performance solution from architecture to deployment.