Onai

Category: Family
Platform: Mobile, AI
Year: 2026; Built
Developer: Jake
Stat: 76; API endpoints
Stat: 23; AI tools
Stat: 16; database models

Preview

iPhone & Android

Want a portfolio like this?

It’s open source. Fork it on GitHub, swap in your own projects and make it yours.

An offline family assistant built by a team of four at the AppBuildersPH Hackathon 2026. One laptop at home runs the API, the database and a local AI. The family talks to Onai to set alarms for each other, hand out chores, plan the week and track spending, and it keeps working with the internet off.

What's Included

Talk to Onai by voice or text, e.g. "Wake Ana up at 6:15 tomorrow"
Knows who is speaking, and tells a guest it can’t share family info
Alarms for each family member that ring full screen on their own phone
Kids can’t delete an alarm a parent set
Chores with points and a family leaderboard
Who’s home, from the phones on the home Wi-Fi
Shared calendar with a heads-up before events, moved or cancelled by voice
Monthly budget with spending by category
Questions about family documents, answered with sources
Works with the internet off; phones join the hub over home Wi-Fi

The Problem

Family life runs on alarms, chores, the calendar and "who’s home?", and most assistants that help with it send everything to the cloud. Onai keeps the family’s voices and plans on one laptop at home and still does the work.

By the Numbers

76
API endpoints
23
AI tools
16
database models
4
developers

Under the Hood

Highlight 01
One laptop is the whole backend
The hub runs the API, Postgres and Ollama, and prints its address with a QR code for the phones on the home Wi-Fi. Ollama’s cloud models are switched off, and the models load at start-up so the first question doesn’t wait.
Highlight 02
The AI proposes, a person confirms
Every AI tool is either read-only or needs confirmation. Read-only tools such as who’s home run right away. Anything that changes data is checked against the speaker’s permissions, proposed, and run only after someone says yes.
Highlight 03
One poll instead of WebSockets
Each phone calls one endpoint every second. It returns new notices, ringing alarms, who’s home and a short version string per list, so a phone refetches only the list that changed. The same call is the heartbeat for who’s home.
Highlight 04
Alarms that keep ringing
A scheduler checks every 10 seconds. A due alarm rings on its owner’s phone and the hub says it out loud again every minute until it is dismissed. A repeating alarm then moves to its next time.
Highlight 05
Google Calendar without anyone’s password
Events are saved on the hub first, then copied to each person’s Google Calendar through a service account. To connect, you share your calendar and type a one-time code the hub writes into it, so no one can connect someone else’s calendar.
Highlight 06
Answers from family documents
PDFs and notes are split into chunks, embedded with EmbeddingGemma and searched in Postgres with pgvector. Answers stream in with their sources.

Information