Connect your accounts, let the assistant triage and draft, and approve anything important before it happens.
All your accounts · Drafts before sends · Your accounts, your rules
Email, calendar, messages, calls, social updates, and places show up together, so you can deal with the day instead of bouncing between apps.
The assistant can triage threads, draft replies, prep your day, and keep track of loose ends. You choose which jobs it gets and which actions need sign-off.
Choose what the assistant can see, what it can prepare, and which actions need your approval before anything happens.
It keeps the boring parts moving: inbox triage, calendar planning, reminders, and the context you always end up searching for.
Mail syncs as it arrives. The assistant can look at the thread, your calendar, and the history you allow before it drafts a reply.
Your calendar sits next to your mail, so planning does not start from a blank screen. Ask for a slot, and myvaos can check the relevant messages before drafting the invite.
Messages, calls, places, and events belong in the same timeline. myvaos turns them into a daily record you can search later.
Timeline sources are next on the roadmap (see the FAQ).
Most assistants only see the app you are in. myvaos sees the connected parts of your life together: mail, calendar events, calls, messages, and places.
Flight details, old invoices, the last time you met someone. The useful answer is usually spread across more than one account.
See how it works →Mail sync, calendar sync, briefing jobs, diary drafts, and trigger rules run on schedules. Set the rules once, then change them when your life changes.
See how it works →You control what the AI sees and how it interacts with each service. Give it read-only access for one workflow, or let it draft actions that wait for your sign-off.
The point is to offload the work you do not want to do, without handing over the parts that should still be yours.
The control model →Connect sources, mirror the data, decide what the assistant can use.
Drivers mirror each service into your database. Every row keeps its source and external ID, so re-syncs can run repeatedly without duplicating data.
Solid pills are live today; dashed ones are next on the roadmap.
A shared schema across sources: people and their identities, threads and messages, events, calls, places, visits, and the timeline that ties them together.
An AI layer reads the parts of the hub you allow. It can triage mail, draft replies, plan your day, and write diary entries, with permissions set per workflow.
Choose sources, set permissions, review actions.
Connect only the accounts you want myvaos to use. Leave the rest out.
Give each workflow the access it needs: read, draft, queue, or act.
Replies, invites, and messages can wait for approval before anything goes out.
Turn sources and workflows on or off as your needs change.
Connect the accounts that matter and let myvaos start clearing the queue.
Open myvaos