Original keys stay back
Each assistant uses its own client credential. It does not receive the service’s original credentials.
Orbi360 / control that stays with you
Your AI tools.
Your rules.
Connect your services in one place. Decide what each assistant may receive. Keep a record of what was released.
Connect once
The gateway keeps the original credentials. Each assistant gets its own access, not the original key.
Allow what is needed
Set access for each person and client, down to the permitted records and fields.
Inspect the release
Use receipts to see which request was allowed, held or refused.
Orbi360+ / more relevant context
Give the assistant
what matters.
Plus adds a model inside the gateway. It picks relevant material from what is already allowed, or holds the request when it cannot decide.
The assistant you are talking to does the task. Plus only helps choose the context. Software still enforces the permission.
Understand the separationThe permitted set
Project overview
Working preferences
Unrelated guidance
Selected for the brief
Project overview
Working preferences
Working preferences
Illustrative Plus cannot widen permissions or approve its own memory.
The gateway / a smaller, explicit release
The right context.
Within the permission.
Orbi360 checks what that person, through that client, may receive. Plus can pick relevant records or hold the request. Software enforces what is released.
Local demo · no connected services
In this example, Orbi and Claude may receive titles and bodies. ChatGPT and Notion receive titles only. These are example permissions, not limits imposed by those products, and not a claim that each one is compatible.
orbi360 +
permitted candidates
released records
Inspect the example receipt
- Caller
- Decision
- Fields
- Content in ledger
- No file bodies
Plus narrows, not expands
The model you configure chooses from records that are already allowed. A small model that stays inside the gateway is a direction being explored, not a promise of the current setup.
Pause has a clear scope
Pause stops the next check at the gateway. It cannot pull back data already sent, or stop a computer action that runs on its own.
Memory / continuity you can inspect
Keep the preference.
Change the assistant.
Memory you have approved can be offered to clients you allow. A new suggestion waits for an owner to review it. It does not quietly become the truth.
Specified A stored preference is not the same as the context of one task. SparkPath’s proposed learning of procedures is a separate piece of work, and it is not built yet.
Illustrative memory records
“Keep briefs concise.
Approved preference
“Keep briefs concise.
Include supporting sources.”
Orbi · allowed
Claude · allowed
Other clients · not allowed
Candidate / awaiting owner review
“Use a one-page decision summary for project reviews.”
Not offered as approved memory.Actual development UI
Controls you can inspect.
Services, people, memory and receipts. Open a view for the decision it helps you make.
Make it useful
Use it with Orbi. Or your existing assistant.
Confirm the client, the sources and the limits before connecting.