Jarvis, where your people already are
Reach Jarvis on Slack, Teams, WhatsApp, Telegram, a phone or email, and run your home and workflows through it, each on your own account with limits you set. Webhooks work both ways.
Jarvis answers where people already talk to each other. Each connection is yours: made on your own Slack workspace, Microsoft or Google account, Twilio number or WhatsApp Business number, with your own keys, and owned by someone in your organization rather than by a gateway everybody shares.

Fifteen connections, one place
- Chat: Slack and Microsoft Teams (direct messages and mentions in channels), WhatsApp, Telegram and Discord.
- Phone: a number people can text and call, on your own Twilio account.
- Your day: Microsoft 365 and Google Workspace for the calendar, mail and meeting transcripts, and any mailbox over IMAP.
- Meetings: Zoom transcripts, and a note-taker that joins a live call.
- Home and automation: Home Assistant, openHAB, Hubitat and n8n.
Calendar and mail come with Standard, the chat apps and home automation with Pro, and the note-taker, the phone number and Zoom with Business.
Every connection has a reach you choose

Setting one up takes the steps on its own card: create the app in the provider, paste the token, and Jarvis gives you the address to send events to. Then you decide what a message through it may make Jarvis do:
- Public: answers only, for a support channel or a number on your website.
- Team: notes, meetings and who owes what, for your colleagues.
- Owner: everything the voice room has, for you alone.
Limit it further to a list of people, give it a greeting of its own, and anything that would change something still asks first. A connection made by one person stays theirs; the team's shared work is what a team connection reaches, never anyone's private notes.
Your home and your workflows

Connect Home Assistant, openHAB or Hubitat and Jarvis knows what every light, sensor and lock is doing, and runs your automations, rules, scripts and scenes. Connect n8n and it lists your workflows, switches them on or off, and runs one through its webhook trigger. Ask "what is still on downstairs?", "run the movie night scene" or "run the weekly report workflow", or let a mission do it at ten every night.

Each one runs on your own address and token, private to you unless you share it with your workspace. Reading never asks. Anything that does something asks first, on a card that names the device or workflow and what it is doing right now; locks, alarms and garage doors always ask, even in a mission you pre-approved, and restarting or wiping Home Assistant is never Jarvis's to do.

Home Assistant Cloud, myopenhab.org and Hubitat's cloud address connect without opening anything at home to the internet. Using SmartThings, Homey or Zigbee2MQTT? Home Assistant brings them in. Zapier, Make, IFTTT and Node-RED start from a webhook, so they connect as one: Jarvis posts to them when you say so, and they can hand it a job.
Webhooks, both ways

Offer Jarvis any of your webhooks and you can say "post this to the team channel" or "file it as a ticket"; it shows you the call and asks before it sends. A webhook can also fire on its own when a mission finishes, fails or is waiting for you, when Jarvis makes a proposal, or when meeting notes are ready, with the title, the status, a link and a summary in the message.

And the other way round: give a form, a monitoring alert or another app a URL and a secret, and what it posts becomes a job for Jarvis. It answers the request, or starts a mission on it, and the answer goes back through the webhook you choose. What arrives is treated as data to work on, never as instructions, so a message that says "ignore your rules" changes nothing.
An agent for an organization, not a gateway for one person
Open-source assistants such as OpenClaw reach many of the same apps, and they are capable agents for one person on one machine. OpenClaw's own documentation says its gateway is not a hostile multi-tenant security boundary. Jarvis was built the other way round: every connection belongs to an organization with its own members, roles, plan and keys, each one carries the reach you gave it, and what it costs is billed to the account that made it.