All case studies
Smart hardwareGenerative AI · Compilers

A generative recipe engine that speaks motor RPM.

How we built upliance AI — a hardware-constrained personalization engine that turns natural-language cooking requests into safe, machine-executable workflows for the upliance smart appliance.

CLIENT
upliance
INDUSTRY
Smart kitchen hardware
MODEL
Self-hosted Qwen on vLLM
STACK
pgvector · Zod · WebSockets
“Make it low-carb, swap paneer for tofu, serve 4”
{
  "step": 4,
  "heat": { "stage": "saute", "temp_c": 160 },
  "stir": { "rpm": 40, "reverse": true },
  "scale": { "prompt": "tofu", "g": 400 },
  "safety": { "dry_run_lock": true }
}
user ›
“Make this low-carb, swap paneer for tofu, serve 4.”
COMPILEDstir.rpm = 40 · heat = 160°C · tare()

Free text can’t drive a heating coil.

The upliance appliance runs on precision actuators — automated stirring blades, induction heating and integrated weighing sensors. But it relied on static, hardcoded recipe programs that couldn’t handle real kitchens: keto, vegan or Jain diets, missing pantry items, portion changes or personal spice tolerance.

Generic chat LLMs weren’t the answer. Unconstrained text generation can’t be safely translated into the strict thermal limits, blade speeds and timed physical steps the hardware needs.

Four layers between a craving and a motor.

A · DISCOVERY

Semantic recipe discovery

pgvector RAG over the verified upliance recipe base, matching dietary profile, pantry and time constraints to the best base program.

B · ADAPTATION

Context-aware adaptation

A self-hosted Qwen on vLLM recalculates ingredient proportions, liquid-to-solid ratios and cooking duration on the fly.

C · COMPILER

Deterministic instruction compiler

Strict Zod schemas turn steps into motor speeds, multi-stage heat curves, timers and scale/tare prompts.

D · SYNC

Real-time appliance sync

Lightweight WebSockets to the touchscreen OS for live guidance, appliance control and taste-adjustment feedback.

From natural language to machine code — with a safety envelope around everything.

  1. LAYER 1User intentTouchscreen / voice
  2. LAYER 2ASemantic RAGPostgres + pgvector HNSW
  3. LAYER 2BAdaptation engineQwen via vLLM
  4. LAYER 2CHardware compilerZod enforcement
  5. HARDWAREupliance applianceActuators & sensors
SAFETY ENVELOPEBurn preventionBoil-over thermal ceilingsDry-run cutoffsLid-lock triggers
LAYERSUBSYSTEMCORE TECHNOLOGYRESPONSIBILITY
1User intent ingestionTouchscreen / voice NLPSubstitutions, dietary preferences, portion scaling
2ASemantic discovery & RAGPostgreSQL + pgvector HNSWMatches taste & pantry to certified base recipes
2BCulinary adaptation engineSelf-hosted Qwen via vLLMRecalibrates volume, moisture, duration & thermal curves
2CDeterministic hardware compilerZod schema enforcementValidated machine code for RPM, heat curves, scale calibration
SAFEHardware guardrail engineEmbedded firmware interlocksBurn, boil-over, dry-run and lid-lock protection

Personal recipes. Deterministic hardware.

Every stepschema-validated by Zod before it reaches the appliance
4hardware interlocks enforced on compiled output — burn, boil-over, dry-run, lid-lock
0recipe data sent to third-party LLM APIs — Qwen runs self-hosted

More case studies

Have hardware, data or a process that needs AI it can trust?Evaluate your use case

Evaluate your use case

Tell us what you want AI to do. We'll come back to you by email.