Let’s figure it out.

Embla is the dedicated Ubuntu computer being developed as a home for the Emberbuddy AI agent. The first branded engineering sample has arrived.

No. The sample has passed preliminary system checks, but full hardware, software, compliance, support, and commercial validation remain open.

Account creation remains limited to approved email addresses. Existing users can sign in with Google or email and password.

Yes. Once your Embla is signed in with your Emberbuddy account, sign in here with the same account and open My Embla: the same chats, files, schedules and connections as on its own screen, in any browser or in the desktop app for Windows, Mac and Linux. Both keep themselves up to date.

No. Your Emberbuddy plan includes the AI model your agent thinks with, with limits so it can't run away. While Emberbuddy is in development, payments aren't switched on: plans switch instantly and nothing is charged. If you already pay OpenRouter, you can use your own key instead.

Yes. Open My Embla on your phone and turn on notifications in Settings › Notifications (on iPhone, add it to your Home Screen first). You get a notification when your agent needs you, when a routine has something to report, and when mail arrives for your Embla.

Your account and security settings, a short list of your Emblas (name, web address, app version and when it was last seen), your plan and how much model use it has had this month, and the devices you turned notifications on for. With your Emberbuddy plan, your agent's requests to the AI model pass through emberbuddy.com on their way to the model service; they aren't kept. Mail sent to your Embla's own address waits at emberbuddy.com only while your Embla is offline. Chats and files stay on your Embla.

Local-first storage remains the product direction, but a cloud model receives the context needed for a task. The new architecture and its exact data flows are still being designed and must be documented before release.

That boundary is part of the rebuild. The intended design uses a non-administrator Linux user, explicit elevation, scoped integrations, and clear approval points for sensitive actions.