Your senior people can’t be in every review.

Put their decisions in a private workspace. Colleagues connect their own AI to consult those models before asking for a review.

To anyone uninvited, the address looks like one that was never used.
  • Invited addresses onlyexact emails you type, never a whole domain
  • Off the public marketplacenot listed, not in the sitemap or search
  • Access ends when you remove someonemembership is re-read on every request

What changes for the team

Consult a colleague’s past decisions

Your AI can apply your lead’s published decisions to the question in front of you.

The author’s practice

Sharing a model does not make it company policy.

Limits are part of the model

Your AI receives the stated limits and can flag questions outside them.

The expert can be offline

Your AI uses the published model. The author does not join the conversation.

How it works

01

Start a workspace

You own it. Nothing is shared until you invite someone.

02

Invite by work address

Exact addresses, up to fifty at a time, never a whole domain. You send the invite yourself.

03

Your experts publish to the shelf

They build it with their own AI and choose your workspace when they publish.

04

Colleagues connect their own AI

Each member adds their own connection to Claude, Cursor, or ChatGPT.

Who can read it

Enforced on every request, not only on the page.

  • A stranger gets the answer a wrong address gets, so nothing confirms the model exists.
  • Each connection is issued to one member. It opens that workspace only, until the member is removed or it expires 365 days after issue. Treat it like a password; what their AI already read stays in their history.
  • avva never receives your source material. We store only the finished model; the situation a member’s AI sends is used for that answer and not stored.
When the author leavesThe model stays, and who decides what happens to it

A model outlives the person who published it. It stays on your shelf and keeps answering when they move teams or leave; removing them does not take it down. Its author can unpublish it or move it to private, but cannot make it public without the workspace owner’s approval, given per model on the workspace page.

If it leaves your shelf, the workspace owner is emailed. There is no ownership transfer yet. Full detail is in the Privacy Center.

Two roles: owner and member

Owner

Invites and removes members, sees usage, and decides whether a model may go public.

Member

Uses any model on the shelf. Sees neither the member list nor usage.

Before you start

  • Contracts. avva has no legal entity and cannot sign a data-processing agreement. Who runs avva
  • Security. Connections use HTTPS. Access keys are hashed. The support tool logs reads of model contents.
  • Access controls. No single sign-on, directory sync, groups, per-model permissions or audit export.
  • Model ownership. The author can remove their model from the shelf; the workspace owner cannot.
  • Account deletion. If the owner deletes their account, the longest-standing member who has signed in takes over. With no such member, the workspace is deleted.

Security questions? Email support@avva.chat.

What it costs

Free during beta. Each member’s key allows 1,000 requests a day, per model.