Companion Hub personas
The people on this page are fictional. They are invented to show how Companion Hub is set up and used. They are not real users.
Companion Hub is the appliance runtime and dashboard. It runs on a box at home or in an office. It runs apps, such as Companion Memory, and it signs people in through CI Account, the account and sign-in service that Companion Hub uses.
Each section describes one person. It covers their setup, what they want, what Companion Hub does for them today, and what is not yet built. The status labels mean the same thing as on the Companion Memory personas page:
- Works today: the capability is on by default.
- Behind a setting: the capability is in the code, but it is off until an owner or operator turns it on.
- Not yet: the capability is not built, or it is built but not connected to the product.
- Planned: the design is documented, and the code does not exist yet.
Maya, the household operator
Maya runs the Hub in her home. Her family uses it, and she is its operator. The first person to sign in to a new Hub becomes its operator. On a Hub paired to a CI Account organization, only members of that organization can sign in with CI Account. In her family, Maya is the person who sorts out problems.
Setup. One Hub on her home network. Each family member signs in with their own CI Account. The Hub runs Companion Memory, which holds the household’s photos and calendars.
What she wants. Maya wants each person to sign in to their own account. She wants to share photos with relatives and to revoke that access later. She wants to approve agent actions before they run, and to know that backups run.
How Companion Hub helps today.
- Works today: each person signs in with their own CI Account.
- Works today: household profiles.
- Works today: agent actions that reach outside the box are queued for her approval.
- Works today: app backups run on the Hub.
- Works today: the memory export. Each person exports their own account, and the file moves that account’s memory to another box. Sharing settings do not move with it.
- Behind a setting: web push reminders in a browser. Push needs keys set on the box.
What is not yet built.
- Not yet: approval cards in the Hub dashboard. Approvals happen in Companion Memory today.
- Not yet: removing copies that a relative’s box already holds after access is revoked.
- Not yet: push notifications in the Hub phone app.
- Planned: a care circle for an older relative. It would send a digest and end on a set date.
Scenarios. Plan a dinner or film with a group. Share an album with grandparents. Keep a care circle informed. Recover after losing a device. Move the archive to a new box.
Rafael, the self-hoster
Rafael runs his own Hub on hardware he controls. He reaches the Hub from outside his home network through a Cloudflare tunnel that he manages. He edits addresses, keys, and endpoints himself. He is comfortable with compose files.
Setup. His own hardware on a private network, a Cloudflare tunnel, and CI Account for sign-in. He runs some apps that he builds himself.
What he wants. Rafael wants public access to his Hub that still requires sign-in. He wants the apps behind the tunnel to check who is signed in. He wants to choose when updates land. He wants to move the box with a complete export.
How Companion Hub helps today.
- Behind a setting: public access through a Cloudflare tunnel. You turn it on after you pair the Hub with CI Account.
- Works today: apps that hold the shared secret can check who is signed in.
- Works today: apps that you build with your own compose file. The Hub checks the apps you install against a list of refused settings, such as privileged mode and host networking.
- Works today: agent keys that carry only the scopes you give them. New keys default to write access.
- Works today: you can turn off automatic updates and pin a version.
- Works today: app backups and the memory export.
What is not yet built.
- Not yet: an update window, or a way to skip one version. The Hub checks for updates once a day.
- Not yet: a check on the receiving box that an export is complete before an import starts.
- Not yet: telling the peers that used a key when you rotate it. You can rotate a key by hand. After you rotate the pool identity key, each peer must pair again.
- Planned: per-app limits on what an agent key can do.
Scenarios. Recover after losing a device. Move the archive to a new box.
Lena, the studio owner
Lena runs a small design studio. She has several staff accounts on the office Hub, and she has a second Hub at home. The two boxes form a Hub Pool. In a Hub Pool, the Hubs can exchange signed requests with each other. Lena sets client meetings in the calendar, and she sends client invitations as files.
Setup. An office Hub and a home Hub in one Hub Pool, over a private network. Each staff member signs in with CI Account.
What she wants. Lena wants both boxes to stay paired. She wants each staff member to sign in to their own account. She wants clients to see only what she agrees to share. She wants to remove a leaver, and to keep or archive that person’s history as she chooses. She wants agents to spend only inside a limit that she sets.
How Companion Hub helps today.
- Works today: pair a second Hub with a PIN and an operator approval.
- Works today: the Hubs in a pool exchange signed requests when both boxes have keys.
- Works today: each staff member gets an account when they first sign in with their CI Account.
- Works today: each staff member signs in with their own CI Account.
- Works today: remove a staff account and its grants.
- Works today: a paid app is checked for an entitlement before it installs.
- Works today: you review each answer before it is sent. Actions that reach outside the box are queued for approval.
What is not yet built.
- Not yet: agent purchases, and a spending limit for purchases.
- Not yet: removing a leaver’s copies from the other box.
- Not yet: replies to client invitations.
- Not yet: separate matters or clients. Search and grants apply to the whole account.
Scenarios. Prepare a client meeting. A member leaves a group. Buy tickets inside a spending cap. Check a claimed identity before you answer.
Kenji, the traveller on a phone
Kenji owns a home box, and he uses it from his phone while he travels. He reads each action in full before he approves it. He does not approve anything he has not read.
Setup. His home Hub, reached from his phone over a private network. He signs in with CI Account. He uses Companion Memory on the Hub.
What he wants. Kenji wants to reach his home box from his phone while he is away. He wants to approve queued actions on the road, and to receive reminders on time. He wants an agent to book inside a limit, but only after he approves the booking.
How Companion Hub helps today.
- Behind a setting: the Hub dashboard in a phone browser, over Tailscale, once Tailscale is set up on the Hub and on the phone.
- Works today: approve or decline queued actions in Companion Memory.
- Works today: reminders are recorded as due on the Hub. You see them on a phone only when push is set up.
- Behind a setting: web push reminders in a browser. Push needs keys set on the box.
What is not yet built.
- Not yet: the same approval card in the Hub dashboard.
- Not yet: holding a question in Companion Memory while the box is off.
- Not yet: reminders inside the app.
- Not yet: agent bookings, and a spending limit for them.
Scenarios. Use the Hub away from home. Plan a dinner or film with a group. Buy tickets inside a spending cap. Recover after losing a device.
Omar, the support-seeking user
Omar has his own account on a Hub that his relative set up and runs as the operator. When something stops working, Omar asks his relative for help. He reads out his settings, or he tests them, so the relative can see what is wrong.
Setup. His relative’s Hub, with Omar’s own CI Account. He uses a device at home on the same network.
What he wants. Omar wants to decide what each supporter can see. He wants each request explained in plain words. He wants to know what was shared, to revoke a supporter quickly, and to receive appointment reminders on time.
How Companion Hub helps today.
- Works today: approve or decline a request, with the answer shown on screen first.
- Works today: Disclosure History lists what was shared. He can review it with his relative.
- Works today: revoke a supporter’s grant when he decides.
- Works today: appointment reminders are recorded as due on the Hub. You see them only when push is set up.
- Behind a setting: push delivery of reminders.
What is not yet built.
- Not yet: reminders inside the app.
- Not yet: removing copies that a supporter’s box already holds after access is revoked.
- Planned: a caregiver role that acts for another adult, with that adult’s consent.
Scenarios. Keep a care circle informed. Check a claimed identity before you answer.