TECHNOLOGY / CURRENT ARCHITECTURE

FROM CONTEXT
TO COORDINATED
ACTION.

Heylu separates the user experience, intelligence runtime, data layer and external providers so each can evolve without exposing infrastructure details to the user.

STACK / 01

THE CURRENT
INTELLIGENCE FLOW.

01

HEYLU EXPERIENCE

Chat, Vibe, Explore, Map, saved places and itineraries provide the user-facing coordination environment.

02

LU GATEWAY

Handles authentication, request validation, active-context authorization and trusted server-side execution.

03

OLYMPUS 0.1

The first public LU model identity, combining contextual understanding with the capabilities available through the LU runtime.

04

CONTEXT + MEMORY

Relevant conversation, itinerary, preference and user-controlled memory can be retrieved for continuity and personalization.

05

PROVIDER GATEWAY

Abstracts external LLMs and grounded data services so the product is not bound to a single model or vendor.

06

ACTIONS + PERSISTENCE

Structured plans, messages, itineraries and supported actions are persisted through governed server-side paths.

BOUNDARIES / 02

TRUST THE SERVER.
NOT THE CLIENT.

Security-sensitive decisions are designed to remain behind authenticated server boundaries.

CLIENT EXPERIENCE
AUTHENTICATED LU GATEWAY
CONTEXTMEMORYOLYMPUSTOOLSPOLICYUSAGE
PROVIDER GATEWAY
CONTROLLED RESULT

COMING SOON · VISION / 03

RESEARCH BEYOND
THE CURRENT PRODUCT.

LU Platform, LU Everywhere, LU OS and other future surfaces represent long-term direction. They are not presented as generally available products today.

VISION

LU PLATFORM

Future external access to selected LU capabilities through governed APIs and enterprise integrations.

VISION

LU EVERYWHERE

A future continuity layer that could preserve approved context across more products and surfaces.

VISION

LU OS

A long-term intelligence layer above existing device operating systems, not a replacement for them.