Personal AI · on-device

Remember More.
Explain Less.

Orby is a memory and context layer for your phone.

Speak it, shoot it, or circle it on screen. Orby stores what it means, connects it to your week, and brings it back the moment it matters.

Capture
Voice · camera · circle
Memory
Meaning, not raw text
Runs
On-device, NPU
9:41

Listening

“Whenever I take a train, remind me to carry my charger, neck pillow and the printed ticket.”

Stored as memory

Train travel kit — charger, neck pillow, printed ticket

PreferenceTrigger: trainVoice

The gap

You didn’t forget. It just never reached you in time.

Scattered
Email, chats, lectures, posters, things said out loud.
Manual
Every note, task and reminder is you doing the structuring.
Too late
The packing list surfaces after the train has left.

Capture

Three ways in. No forms, no folders.

Your phone already has a microphone, a camera and the screen you’re looking at. Orby uses all three.

9:41

Listening

“Whenever I take a train, remind me to carry my charger, neck pillow and the printed ticket.”

Stored as memory

Train travel kit — charger, neck pillow, printed ticket

PreferenceTrigger: trainVoice

Speak

Say it like you'd say it to a person. Orby reads intent, not keywords.

11:48

Camera · capture

Vaccination follow-up — 2nd dose after 28 days

Read & understood

Second dose due 11 November

HealthComputed dateCamera

Nudge 2 days before · stays on device

Capture

Point at a whiteboard, a prescription, a printed schedule. Orby extracts the facts and computes what follows.

16:03

Messages · Lab Group

hey has anyone started the report yet
DSP submission moved — Friday 5 PM, Lab 204
hard copy only btw
oh no, thanks

Circled · remember this

DSP report — Friday 5:00 PM, Lab 204

DeadlineHard copySource: Lab Group

Calendar entry drafted · print reminder set

Circle

Circle anything on screen. The source and the surrounding conversation stay with the memory.

Memory

It doesn’t store what you said. It stores what it meant.

A note app keeps a string. Orby keeps a typed record with a trigger, a source and a confidence — so the memory can find you instead of waiting to be searched.

Corrections travel upward
Fix it once and the memory updates — not just that one reminder.
Acceptance is signal
Nudges you act on get stronger. Ones you dismiss retire themselves.
Preferences become defaults
Once a pattern holds, Orby stops asking. The more it learns, the less you explain.
memory.recordlocal
content
"charger, neck pillow, printed ticket"
type
preference · travel
intent
standing_rule
trigger
event.category == "train"
source
voice · 21 Sep, 21:04
confidence
0.94
links
routine.packing → calendar.trips
residency
on-device

The trigger is part of the record — so Orby knows this matters the next time a train shows up in your week.

Context

Retrieval is table stakes. Connection is the product.

Orby joins what you told it to what’s actually happening — your calendar, your routines, your week. Then it speaks first.

Example 01

You mentioned it three weeks ago. Orby brings it back the night before.

Nothing about that calendar event mentions a charger or a neck pillow. Orby holds the rule you spoke once, sees the trigger, and raises it while there’s still time to pack.

10:12

Tuesday, 14 October

10:12

Orby · now

Your train to Pune leaves at 6:40 tomorrow.

You usually carry a charger, neck pillow and the printed ticket. Want tonight’s checklist?

Add checklistNot now

Connected: travel preference (spoken 3 weeks ago) + calendar event

08:20

Thursday · conflict found

09:30Signals lecture
12:00Lunch — Riya
14:00Viva — Lab 204
14:30Mentor sync

⚠ 30 min overlap

Orby suggests

Move the mentor sync to 17:30.

  • ·Viva can't move — it's graded
  • ·You rarely take calls before 10:00
  • ·Both of you are free after 17:00
Send requestEdit
Example 02

Two things collide. Orby proposes the fix, with its reasoning.

It weighs what can’t move, when you actually work, and what you’ve rescheduled before — then drafts the message and waits for you to approve it.

Why it’s different

Not another chatbot. Not another task manager.

How information gets in

AI chatbot

You type it, every time

Task manager

You fill a form, every time

Orby

You speak, capture or circle it

What it keeps

AI chatbot

The current conversation

Task manager

The fields you entered

Orby

Meaning, intent, source and context

When it speaks

AI chatbot

When you open it

Task manager

When a due date fires

Orby

When your context makes it useful

Where it runs

AI chatbot

Someone else's servers

Task manager

Someone else's servers

Orby

On your phone, NPU-accelerated

On-device inference
Understanding and reasoning run locally.
Built for the NPU
Snapdragon acceleration keeps context cheap in battery.
Context stays yours
The memory graph lives on the phone. Cloud is opt-in, per task.
You approve actions
Orby drafts. Nothing sends until you confirm.

Remember More. Explain Less.

For students, professionals and anyone whose information arrives faster than they can file it.

On-device · No account required to try