Specify what
it may read.
Choose the folders, files and systems it may read, team by team. It answers from what you approve, and a team only sees what its role allows.
CHOSEN SOURCES / BY TEAMYOUR CONTROL
Defined access.
A person approves.
You choose the sources and access roles. A person approves anything sent or spent. Every question and answer is logged on your system.
- ACCESS
- By role
- APPROVAL
- A named person
- AUDIT LOG
- Your questions and answers
DEFINED ACCESS
EVERY ANSWER LOGGED
01 / ACCESS & APPROVAL
Access by role.
Approval by a person.
Set with you in Scope, built in Deploy and tested before your team relies on them.
Specify what
Review before
it goes out.
It drafts. A person approves before anything is sent or spent: an email, a filing, an order, a payment. It cannot approve its own work.
DRAFT FIRST / A PERSON APPROVESSign-in you
already manage.
Single sign-on through your company accounts, with access by role. When someone leaves and their company login is closed, their access closes with it.
SINGLE SIGN-ON / ACCESS BY ROLESee every question
and every answer.
The audit log records every question and every answer, with who asked and when. It lives on your system, not ours.
AUDIT LOG / ON YOUR SYSTEM02 / BACKUPS AND TESTS
Restore tested.
Access tested.
Deploy sets both up before launch. Care keeps them working.
Encrypted. Restore steps recorded.
Backups are encrypted and kept where you decide, with the keys in your name. The restore steps are written into the runbook, and Care checks that they still work.
Tried on your own documents.
Before launch we test for leaks and prompt injection on your real documents: whether one role can see what another should not, and whether instructions hidden in a file can steer it. Launch waits until the agreed tests pass.
03 / OPERATING TERMS
Rented AI
runs on their terms.
A vendor can gate, change or reprice access. A system you own answers to you.
A hosted service controls its own access terms. Local work runs within the capacity of hardware you choose. Discovery includes hardware, power and Care in the cost comparison.
Care tests newer open models on your tasks and replaces the current model when they perform better. In a mix, an outside service handles only the work you allow.
See where it runs04 / CHAIN OF CUSTODY
If you stop,
it stays yours.
Stop after any stage, or cancel Care in any month. Here is what you keep.
KEYS AND ACCOUNTS
Already in your name.
The hardware, the cloud account, every key and every login were yours from day one. There is nothing to transfer and no one to ask.
CONFIGS AND RUNBOOK
Written to hand over.
Every config, the runbook and the handover notes from Deploy, written so your own team or another provider can run it.
YOUR TRAINED MODEL
Trained on your work. Kept.
A Custom Model trained on your work is yours, with its before and after scores. Your documents and the audit log stay on your system.