Lantern

Inside Lantern.

How analytics becomes a decision, who makes it, and what happens next.

Try a week in Lantern.

Four actions for four teams at a components maker. Approve one, or dismiss it with a reason.

Owned
Every action has an owner and a team
Explained
The reason and the money at stake
Discussed
Threads, mentions and answers from Lantern
Approved
By a person, flagged when a second check is needed
Drafted
Messages translated for the reader
Recorded
Every decision, append-only, read back by SAS Viya

ExpediteHigh priorityDo Minh Khoa, Buyer

Expedite PO-002071

SUP-04 delivered 97% of its orders more than 2 days late in the last 26 weeks. This order carries HYD-03, which the model rates at high stockout risk this week.

₫2,818,000at stake

Request to expedite PO-002071 - due 13 Oct 2025

Dear Lin Yu-ting, purchase order PO-002071 is due on 13 Oct 2025. Recent deliveries from SUP-04 have arrived several days late, and this order is important to our production plan. Please confirm a ship date that meets the promised date. Best regards, Do Minh Khoa, Purchasing

Built on what SAS Viya does best.

Five parts of SAS Viya run underneath Lantern. Each one becomes something a person can see and use.

SAS Lineage

In SAS Viya
Traces every table from the department file it started as, through each cleaning flow, to the action it fed.
In Lantern
Each action shows its trail back to the files it came from.
RAW_PO_2024
RAW_PO_2025_V2
RAW_PO_2025_V3
RAW_PRODUCT
cln_03_purchasing
CLN_PO_LINE
GOLD_ACTIONS
Expedite PO-002071
Source fileSAS flowClean tableDecision tableLanternOne purchase-order line, from source files to an action
  • Model Studio and Model Manager

    In SAS Viya
    Seven stockout models compared on the same held-back weeks. The champion is registered in Model Manager, and a challenger is retrained every week.
    In Lantern
    Each action shows the rule that raised it and, for stock risks, the champion’s probability.

    7

    models compared

    0.94

    AUC of the champion on held-back weeks

    133 of 138

    stockouts caught in its 300 riskiest

  • Intelligent Decisioning

    In SAS Viya
    Two rule sets turn a model score into an action: six rules choose what to do, fourteen set priority, owner and review.
    In Lantern
    The reason and the owner on every card come straight from these rules.
    1. Stockout model
    2. 6 rules: choose the action
    3. 14 rules: priority, owner, review
    4. Action in Lantern
  • Visual Analytics

    In SAS Viya
    Reports for analysts and managers: a 13-page analytics story and a 5-page control tower.
    In Lantern
    The same charts beside the action they explain. Embedding them is on the roadmap.
  • Job Execution

    In SAS Viya
    A scheduled job rebuilds the actions every Monday at 06:00 and reads back what people decided.
    In Lantern
    A fresh list each Monday, with last week’s decisions already counted.
    1. Mon06:00
    2. Tue
    3. Wed
    4. Thu
    5. Fri
    6. Sat
    7. Sun

    SAS ViyaLantern

How Lantern works.

  1. 01 · Collect

    19

    department files, loaded as they are

  2. 02 · Clean

    28,098

    rows fixed by 40 traceable rules

  3. 03 · Predict

    0.927

    AUC on stockout risk

  4. 04 · Decide

    306

    actions, each with an owner

  5. 05 · Act

    DiscussApproveSendTrack

    together, then recorded

Controls live in the database.

Lantern’s own stack is open source, and yours to host.

  • Lantern appNext.js
  • APIPostgREST
  • DatabasePostgreSQL
  • SAS ViyaAnalytics engine
  • n8nEmail delivery
  • Row-level security
  • Append-only audit trail
  • Revocable sessions
  • No keys in the browser
  • Least-privilege database roles
  • Self-hostable, so data can stay in-country; you choose the AI model

See Lantern at work.

The demo runs on Meridian, a fictional manufacturer built on a real supply chain dataset. Sign in and work this week’s actions the way its team would.