Perimeter
Local where it matters
- Open-weight models running on the machine
- Controlled workspaces and archives
- Online services enabled individually
- No invisible engines in the workflow
Operational sovereignty
Your AI should remain a capability, not become a dependency.
Choose what stays on the Mac, which services may receive data and who can connect. Permissions and links remain visible and revocable.
ModesLocal and hybrid
PackagesPortable
AccessProtected
Real control
Choose where data and capabilities live
Continuity comes from understandable architecture rather than generic promises about privacy.
Security
Permissions and approvals
- Approval levels for agents and Automata
- Credentials required after idle time
- Logs for sensitive operations
- Approved and revocable T-Chat Nearby access
Portability
Work can move
- Importable and exportable Business Bundles
- .tchat packages for updates and new installations
- Backups before maintenance operations
- Configurations rebuilt without lock-in
Continuity
Stay prepared when the cloud does not respond
A hybrid strategy preserves essential productivity and uses external services where they deliver a genuine advantage.
Shield Web
Companion can block every Internet connection. Local models, documents and tools keep working inside the business perimeter.
Protected sessions
Idle lock requests credentials again while authorised processes can continue.
Private-network access
T-Chat Nearby creates a temporary link, pairs a phone with a QR code and lets you revoke every device.
Distinct updates
Existing installations receive a conservative package; new users start from a neutral installation.
Transparency
The system declares which tools it uses and which operations were actually confirmed.
Protect operating capability
Build a Plan B that is already ready to work.
Let's assess data, dependencies and autonomy levels to design concrete continuity.