All work
Python // Engineering SaaS

Frankcore LPS

Cloud software for lightning-protection engineers — risk assessment, 3D design, bill of quantities, and compliance certificates in one workflow, replacing spreadsheets and email.

Highlight
Built to NFPA 780 and IEC 62305-2
Role
Software Engineer, Frankcore Inc.
Status
Live
Year
2025 — Present
Stack
ReactThree.jsReact-Three-FiberExpressPythonFastAPINumPySciPyPostgreSQLDocker

The problem

Designing a lightning-protection system (LPS) is standards-driven engineering work. Consultancies traditionally move a project through risk assessment, design, costing, and certification using spreadsheets, CAD files, and email — slow, error-prone, and hard to audit.

LPS Digital Nexus puts the whole lifecycle in one place, built around the NFPA 780 and IEC 62305-2 standards.

The workflow

Each project moves through five steps, and each step produces a server-generated PDF:

  1. Client intake — the structure and project details.
  2. Risk assessment — calculated against NFPA 780 or IEC 62305-2.
  3. 3D design — an interactive model of the building with air terminals, down conductors, and grounding placed by the Rolling Sphere Method.
  4. Bill of quantities — materials and a cost-benefit analysis.
  5. Compliance certification — the final certificate for the client.

Architecture

Three containers on one private network, each with health checks:

  • React client — renders the 3D design with React-Three-Fiber and Three.js.
  • Express API gateway — authentication, tenancy, quotas, and persistence through Prisma.
  • Python engine — a stateless FastAPI service that runs the standards calculations and the 3D design pipeline with NumPy and SciPy. It's reachable only from the gateway.

Data, authentication, and file storage live in Supabase (PostgreSQL).

Key decisions

The browser is a display, not a calculator. All engineering math and report templates run on the server. The frontend only renders the coordinates the engine returns, so the company's calculation logic never ships in the JavaScript bundle.

A quarantined, stateless engine. The engine has no database access and no public endpoint. The gateway owns all state, which keeps the engine simple to test and safe to scale.

Quotas that can't be gamed. Usage is counted when a project is created, in a durable monthly counter — deleting a project doesn't free up a slot.

Don't reveal what exists. Requests for another tenant's resources return 404, not 403, so nobody can probe for valid IDs.

My role

As a software engineer at Frankcore, I built the platform's backend, the calculation engine's service layer, and the containerized deployment. The engine is covered by 54 automated tests across the standards calculations, design pipeline, API, and PDF output.