oneira
OverviewFeaturesCompareSpecsPreorder a Founding Unit · $80
Oneira guides/Connected workflows

Connected beta / deliberate workflows

A deliberate start for a connected workflow.

See how Oneira can begin a compatible owner-configured workflow while keeping external services, permissions, confirmation, and support boundaries clear.

Preorder a Founding Unit · $80 →See current features →

Product status

What is available now?

  • Connected beta

    Connected beta features require the Oneira app, internet access, a compatible service, and permissions you approve. They can change and may not work with every service.

What you need

Connected beta features need the Oneira app, internet access, a supported service, and permissions you approve. A separate account or fee may also be required.

The short answer

A compatible workflow remains a separate owner-configured service. It is not preinstalled, included with the hardware purchase, or granted unrestricted control.

Oneira carried outdoors with its exterior and OLED screen visible
Real working product / connected workflow explained
Agent hostConfigured separately
Physical inputOneira
ConnectionConfigured through the app
ControlNarrow owner-approved permissions

Oneira Dream Big+

A local AI powerhouse in a star.

Small enough to look playful. Built with a dual AI chip, OLED screen, and 1K camera, plus optional connected experiences you control.

Each $80 Founding Unit includes one Oneira device with a dual AI chip, OLED screen, and 1K camera, plus the selected color and included eye set. The 1K camera is included; its final production module and other non-material production details may change before fulfillment. Optional connected services, provider accounts, usage, and third-party fees are separate.

On-device

On-device reactions

Oneira's expressive reactions run on the device, so its face can respond without relying on a cloud request.

See the local core ↗
Working prototype

Dual AI chip, OLED screen, and 1K camera

The working prototype includes a dual ai chip, oled screen, and 1k camera. The 1K camera is included in the $80 Founding Unit; its final production module may change before fulfillment.

Inspect the hardware ↗
Connected beta

Optional connected services

Optional compatible connected services can extend Oneira when you choose. Setup, permissions, internet access, provider terms, and usage costs remain separate. Connected experiences work only with compatible services the owner deliberately configures. Oneira does not connect automatically to every service.

See compatible connections ↗
Connected beta

Compatible connected tools

Compatible connected tools are optional and owner-configured. Nothing is preconfigured, and universal compatibility is not promised.

See connected features ↗
Web beta

Dream Big+ photo generation

The 1K camera supports deliberate, owner-triggered experiences. Optional Dream creation can transform a photo when the owner chooses it.

Open Oneira Create ↗
Developer preview

Focused helpers

Optional helper experiences have narrow, visible limits. Broader research, coding, and workspace actions remain in development.

Understand the agent path ↗

A simple flow

How it works in three steps.

  1. 01
    Configure

    Set up one supported workflow for a clear task

    →
  2. 02
    Connect

    Review the destination, account, and permissions

    →
  3. 03
    Ask

    Use Oneira to begin a deliberate, reviewable request

What runs where

The agent is not hiding inside the star.

Hosting, service access, credentials, integrations, and support remain part of the owner's separate setup. Oneira can begin a compatible request only after the owner configures it.

This keeps the hardware understandable and prevents a pocket object from implying that it contains an unlimited autonomous computer. Compatibility, availability, provider terms, and app support can change.

Trust boundary

One owner. Narrow capabilities.

Identify the destination, minimize permission, and require confirmation before consequential actions. Do not share a sensitive connection across people who should not share authority.

A Oneira interaction should never be treated as blanket permission for a broad account or an unbounded toolset.

What to connect first

Start with a read-only task you can verify.

Begin with a narrow status, lookup, or summary workflow whose result can be checked. Avoid email sending, file mutation, purchases, shell access, or account changes until authentication, logs, confirmations, and recovery are proven.

Third-party services and integrations have their own risks. Oneira does not provide support or a security warranty for a separate workflow you operate.

Connected workflow / a deliberate front door, not hidden autonomy

A physical workflow interface should make the owner more deliberate, not less responsible.

Oneira can be a Connected beta starting point for a compatible workflow configured in the app. The core companion behavior remains local: its animated expression reacts to motion on-device. The external workflow is a separate service with its own account, permissions, availability, terms, and possible fees. It is not part of the hardware purchase and receives no unrestricted access by default.

The practical question is whether the physical interface improves judgment at the moment of request. Oneira can make a narrow task feel intentional, then let the app show the destination and permissions. Sight is a separate Connected beta visual request with a single owner-triggered frame. Everyone present must agree before a Sight capture. Translation and creator help are still in development.

Decision framework

Four checks before connecting an external workflow

  1. 01

    What exactly runs outside the device?

    Identify the external service, account, permissions, data destination, and support terms before you connect it. Oneira is the request and feedback surface, not proof that a third-party workflow is private, local, or included.

  2. 02

    Can the workflow begin safely with read-only work?

    Start with a status check, a lookup, or a summary that you can verify independently. That lets you test routing, authentication, display limits, and failure handling before you consider actions that send messages, alter files, operate a browser, purchase, publish, or reveal private information.

Questions, answered

The details that decide a purchase.

Does Oneira come with a connected workflow installed?+

No. External service setup, hosting, credentials, integrations, security, support, and possible fees remain separate.

Can Oneira control my computer?+

Not by default. Broad computer access would require a separately configured external workflow and carries significant security risk.

Can multiple people share one sensitive connection?+

Only people who should share the same authority should share a connection. Separate accounts and credentials when trust differs.

What is a safe first Oneira workflow?+

A read-only lookup or status request with a verifiable response is safer than a workflow that sends, purchases, deletes, or changes external data.

Keep exploring

Understand the product before you choose it.

Connected beta / optional toolsOptional tools, connected on purpose.→Oneira Connect / Connected betaConnect Oneira to optional services.→Architecture guide / device to agentWhat is a physical interface for AI agents?→

Oneira / current availability

Preorder a Founding Unit · $80

500 Drop 01 units remain across 5 currently available colors. Availability is confirmed when secure checkout begins.

Preorder a Founding Unit · $80 →
oneira

Dual AI chip. OLED screen. 1K camera.

ComparePrivacyPreorder termsSupport
The honest boundary

Oneira's focused helpers have narrow, visible limits. Broader research, coding, and approved-workspace actions remain in development.

  • 03

    Who has authority, and where is it visible?

    A configured connected tool should have only the permissions necessary for its task, and the owner should be able to identify the service before it runs. Require confirmation for consequential actions. Do not use one physical press as blanket permission for a broad account, a shared environment, or an unbounded toolset.

  • 04

    How will you notice failure or revoke access?

    Connected workflows can fail because of network interruptions, expired credentials, service changes, errors, or unavailable services. The app and workflow need an honest error state, reviewable activity, and a clear revocation option. A tool should never imply completion merely because a device animation finished.

    • Good fit

    Good fit if…

    • You already operate a narrowly scoped connected workflow and want a tangible way to start a known request.
    • You value app-visible routing, permissions, and confirmations more than an illusion of autonomous magic.
    • You can test with non-destructive tasks and maintain the host, credentials, and service configuration yourself.

    Choose differently

    Choose something else if…

    • Choose a computer-first agent interface if the work requires long prompts, rich logs, code review, or frequent intervention.
    • Choose a dedicated managed automation product if you need vendor-operated reliability and formal support for a business-critical workflow.
    • Do not connect an agent if you cannot isolate its permissions, review its activity, or revoke access promptly.