Always Near

How Always Near works

From everyday conversations to a clearer picture.

Not constant hovering. Not a task list. Review possible conversational signals under your control; contact sharing and summaries are planned, not active.

Open your dashboard Read the guides

Example feed

Today at a glance

Sample data

Financial safety

Dad had a conversation about a request for banking details

AI interpretation, not confirmation. Always Near is not an emergency service.

Plans & appointments

Dad's Tuesday appointment sounds uncertain

AI interpretation, not confirmation. Always Near is not an emergency service.

Daily summary

A mostly routine day, with two moments to review.

AI-assisted examples. Signals are not verified facts. Always Near is not an emergency service.

Before Always Near

First, get started with Bee.

You can explore the Bee Pioneer wearable or install the Bee iPhone and Apple Watch app. If the Watch app does not appear automatically, follow Apple’s installation steps. Bee setup and purchases happen with Bee, not Always Near.

The manual Bee upload trial is limited to the designated owner. Saving an Always Near account alone does not start analysis.

Bee connection · pre-beta prototype

You choose what leaves your computer.

The controlled demo uses Bee Developer Mode and its official CLI through a local Windows tool, not an everyday consumer connection. Manual uploads are enabled only for the designated test owner while the real Bee-to-dashboard flow is verified. There is no public companion download yet; another account cannot activate uploads. Bee has developer API and MCP tools, but a supported public connection flow for ordinary users and hosted third-party services is not currently available.

Developer demo upload guide

The current manual connection

  1. Enable Bee Developer Mode, install Node.js and Bee's official CLI, and personally accept the current Always Near processing policies.
  2. Extract the supplied companion packages. Run “Connect Bee to Always Near.cmd”, approve Bee's own sign-in, then enter the one-use code from Bee connection in your dashboard.
  3. Enable approved uploads for that computer. Pairing alone stays pending and sends nothing.
  4. Run “Upload one approved Bee part.cmd”. Review the unfiltered text locally, type YES for one part, then UPLOAD to send it. Find the results on that conversation's date in Today.

This is manual, partial-history analysis - not continuous monitoring. Trusted-contact messages and generated daily/weekly summaries are not active. Unsigned packages may warn or be blocked; never disable Windows protections.

Bee currently does not support hosted third-party integrations. We plan an easier connection if Bee offers supported delegated API or MCP access; its existing developer MCP is not itself a hosted authorization flow. There is no announced delivery date. Read the guide for current access limits, troubleshooting and the integration references.

The journey

Four clear steps.

  1. 01

    You start with your Bee

    The wearer creates the one owner account for the Bee connection, reviews the data and AI policies, and chooses what may be analyzed.

  2. 02

    You set the boundaries

    Save attention categories and review the current data and AI policies. Conversation input is not filtered or redacted; any text you approve, including spoken secrets, is sent for AWS AI analysis.

  3. 03

    Pair, then approve an upload

    In the designated-owner trial, pair your Windows computer and enable manual uploads. Review the unfiltered conversation part, then explicitly approve sending it for AWS AI analysis.

  4. 04

    Review the conversation's day

    Open Today and select the recording's date to inspect structured results and observed processing status. Coverage is partial; AI can be wrong and no alerts is not an all-clear.

Trusted-contact sharing · planned

Two people. Two kinds of consent.

The planned care-circle experience separates the wearer's sharing permission from each contact's messaging choice. Invitations, contact logins and delivery are not active in the current trial. Neither person's consent can be given by the other.

The Bee wearerAn invited person
Owns the Bee account and approves analysis.
Creates a separate, limited contact login.
Chooses contacts, categories, cadence, and allowed sharing.
Confirms their email and opts into email updates themselves.
Can change or stop future sharing.
Can stop their own message channel independently.

A look inside

Organized to be easy to scan.

Example dashboard

Alerts, context, and summaries in one place.

Explore the actual dashboard layout with clearly labeled illustrative information.

Tour the example dashboard

Owner setup

Your choices come before connection.

The wearer signs in, records their baseline and preferences, names people they trust, and reviews one informed consent.

Go to owner setup

Important limits

A tool for awareness, never a replacement for care.

Always Near interprets audio-derived conversation information. It may misunderstand a conversation, overstate a concern, miss something important, or deliver an update late. A lack of alerts is not an all-clear.

It is not a medical device, medical advice, professional supervision, or an emergency service. Verify AI output. If someone needs immediate help, call 911 or the appropriate local emergency number.

Learn to read an alert