Your context stays yours.

The engine works in your environment

On your computer, company server or rented server under your control. This is where your files, rules and workflow context live. The engine can work without the app open; its host machine must remain available.

The app is not your working-data store

Pair the app with the engine. Working content is end-to-end encrypted between them and decrypted on the client device. Account, subscription and contact data are separate from working content.

You choose the model

When using an external model, required inputs go directly from your environment to its provider. End-to-end encryption of the control channel does not mean the AI provider cannot see those inputs. The same applies to tools you authorize to use data.

A local model removes the need to send inputs to an external model provider. Suitability depends on the model, hardware and task; connected external tools do not automatically become local.

You control permissions and oversight

Together with your partner, choose which accounts the workflow may access, what it can do independently and when approval is required. Drafting and sending a reply are separate steps. Sensitive actions can stay under review.

Running your own environment also means managing access, updates, backups and the devices that display content. Public code allows implementation review; it is not a security certification by itself.

Data in this calculator

Calculations run in your browser. Shared advanced-calculator links contain the entered assumptions. When you request a PDF, we save your email and calculation link in our contact system; this is not a newsletter subscription. Your email is not included in the shared link or PDF.