← All work05 · Workflow · Data modelling

Service Studio

Business services described as data, not rebuilt as code.

Type
Schema-driven workflow builder
Context
Professional work
Stack
Node.js · Express · TypeScript · Knex

01The problem

Every new business service — a multi-step process of forms, fields and validation — was a custom build, so each one cost the same effort as the last.

02The solution

A builder in which a service is data: services contain steps, steps contain sections, sections contain forms, forms group fields into panels, and fields carry their own validation rules.

03Architecture

  • Relational model: services → steps → sections → forms → panel groups → fields → validation rules
  • Node/Express API with Knex migrations and strict seeding order to keep references valid
  • Object storage for uploaded documents (S3)
  • Security hooks so generated services still pass through platform access control

04Hard parts

  • A deep hierarchy has to stay consistent: ordering, references and validation all live in the data.
  • Configurability without turning the builder into a programming language.

05My contribution

your role on Service Studio

06Where it stands

what Service Studio made possible

07Built with

Node.jsExpressTypeScriptKnexSQLAWS S3
Next project · 06

Tenant Orchestrator →

The part of the system that creates the systems.