Security for the computers your people work on

Let your people use AI. Keep the data where it belongs.

Everything that leaves a company computer is checked on that computer first: what goes into ChatGPT or Copilot, what an AI agent like Claude Code reads, runs and sends, and what leaves by USB, upload, print or mail. Sensitive values are masked before they go, keys stay in the vault, and Trustwelt never reads the text. Six products, each sold on its own.

For your own computer or your family? Trustwelt for you and your family

Write a reply to PERSON_1 about his refund. His card is CARD_NUMBER_1, the account IBAN_1. He wants it by Friday.

Held on this computer · a name, a card number and an account number masked

Your organisation sees
one record
Service
ChatGPT
How it came in
Typed and sent
Found
Name 1 · Card 1 · IBAN 1
Decision
Masked, then sent
Policy
Organisation default, version 12
The text
Stays on the computer
  1. sessionClaude Code in ~/src/billingconfined · bubblewrap + Landlock
  2. Read~/.ssh/id_ed25519refused · folder rule
  3. Bashnpm testallowed · recorded
  4. modelclaude-sonnet-4-5 via Trustwelt2 values masked · key from the vault
  5. Bashgit push --forceasks you in Trustwelt Desktop
  6. sshdeploy@prod-1signed in the vault · key never handed over

Two decisions the product makes on the computer, redrawn from its real states on sample data.

Trustwelt AI Security

One product, two halves: what goes into AI, and what AI agents may do.

Both run on the computer itself. Both decide by policies you publish, in words your people read. Neither sends Trustwelt a text, a prompt or a key.

People and AI services

Checked before the site gets it. Masked, not read.

48 chat, translation, writing and transcription services known, each approved, restricted to a team or blocked. A paste, a drop, an upload or a typed message is held on the computer, read by validated detectors and Trustwelt's own names model, and the person sends the masked version or nothing. Policies are drafted, simulated, piloted, published and rolled back; a held text waits for your answer.

Tenant Admin › AI services › Policies: the version in force, the ordered policies with their people, services and the action per class of data.

AI agents and IDE assistants

A room, not the house. The keys stay in the vault.

Claude Code, Codex CLI, GitHub Copilot, Cursor, Gemini CLI run behind a gateway on the computer: every tool call put into a risk tier and decided by your rules, questions answered in Trustwelt Desktop, model calls checked by the same detectors and paid for with a key the agent never sees, connections routed and credentials put in per destination. Each computer reports which agents, MCP servers and keys in files it holds.

Tenant Admin › AI services › Sessions: agent sessions and one open with its timeline of decisions, refusals, a masked model call and a credential injected.

Start from the problem

What do you need to stop?

Each problem has its own product. Buy the one you need first and add the others when you want them.

Product tour

What it is like to run.

Every screen below is the real product on sample data. No secret is ever shown, in the product or here.

Set a computer up once. It stays set up.

On a computer your organisation manages, a person types their master password once. From then on the browsers are connected, the rules apply, sync is on, and the computer reports in every few minutes. There is no Quit and no Sign out for the person; only the organisation ends it.

  • A computer that stops reporting shows as such, and you are told by e-mail.
  • Locking the screen hides the window; filling, sync and protection carry on.
  • Only an administrator of the computer can stop protection, deliberately, and that shows in your console.
About managed computers about Set a computer up once. It stays set up.
Managed computers in Tenant Admin: each computer with its person, platform, whether it is reporting, whether its web filter is on, and when it last reported; one is not reporting and its filter is paused.

Decide what may go into AI services. Check it on the computer.

Approve, restrict or block each of the AI services Trustwelt knows, or a whole category. On a managed computer a paste, a drop, an upload or a typed message bound for an allowed service is held and checked before the page gets it; card numbers, identity numbers, secrets and names are masked, and the person sends the masked version or nothing.

  • Policies per person, group, service and channel, with an action per class of data; observe before you enforce.
  • A text your policy holds waits for your answer: approve for an hour, a day or a week, or refuse with a reason the person reads.
  • Coverage says which computers are checked, checked less or not seen, so nothing blocked is never mistaken for safe.
About what goes into AI services about Decide what may go into AI services. Check it on the computer.
Tenant Admin › AI services › Policies: the version in force, the ordered policies with their people, services and the action per class of data, and the organisation defaults.

Give AI agents a room, not the keys.

Claude Code, Codex CLI, GitHub Copilot, Cursor and Gemini CLI call Trustwelt's gateway before each step. A read of the SSH folder is refused, a test run is allowed and counted, a force-push asks the person in Trustwelt Desktop, a model call is checked and paid for with a key from the vault, a server is reached with a key the vault signed. Each session is on record, without a prompt or a command's arguments.

  • Rules by tool, command and risk tier, first match first; folder guardrails no rule can loosen.
  • Model calls only to your providers and models, through a gateway on the computer; tokens and cost per person, group and model.
  • Started through Trustwelt, the agent writes one folder, reads the toolchains, and connects only through the gateway.
About the agent gateway about Give AI agents a room, not the keys.
Tenant Admin › AI services › Sessions: a table of agent sessions and one open in the right-hand panel with its timeline of decisions, refusals, a masked model call and a credential injected.

Decide which sites work computers may open.

Write the rules in plain words: a site and everything under it, pages under a path, or any address that contains a word you name. Block, warn or allow, and try an address to see what they decide; a rule is in force as soon as you save it. On a managed computer the rules hold in every browser and every application, and a blocked site shows your organisation's own page.

  • A second browser, another application or a private window does not go around the rules.
  • A site with an expired, forged or untrusted certificate is stopped the same way, with the reason.
  • Blocks are on record with the rule and the computer; allowed browsing is not recorded unless you switch a full log on.
About web protection about Decide which sites work computers may open.
Web protection in Tenant Admin: whether protection is on and which version is in force, the tabs for rules, allow list, activity, requests, categories, block page and browsers, and the rules to block a gambling site, a file-sharing site and adult sites by pattern, warnings for a social site and live video, and an always-allowed intranet, each with whom it applies to.

Share the use of a company login. Never the login.

Tenant Admin lists company logins by site and username, never by password. Grant their use to a person or a team. On their computer, Trustwelt Desktop fills the login on the right site under a one-time permission; the person never sees or copies the password, and every use is in your audit.

  • Leavers are out of every grant the moment they leave a group or the organisation.
  • Company cards are paid with but never read; every payment is recorded with its amount.
  • SSH keys for company servers are used by people and allowed agents through the vault, which signs with them and never hands them over.
About company logins about Share the use of a company login. Never the login.
Organisation logins in Trustwelt Desktop: Salesforce and LinkedIn ready to use, AWS production visible only; passwords are never shown or stored here.

Run your organisation from one console.

People and roles, admin areas delegated to HR, IT or finance, the access matrix that sets the most each role may do, and the usage audit. Send invitations through your own mail server.

  • Roles: owner, security admin, policy admin, auditor, support operator, member; plus admin areas with delegated authority.
  • The access matrix: the most each role may do per kind of login, from viewing to managing.
  • Every privileged change, and every refused attempt at one, in a record nobody can quietly edit.
About Tenant Admin about Run your organisation from one console.
The Tenant Admin access matrix: rows for each role, columns for each kind of login, and in each cell which of View, Request, Use, Share and Manage is allowed.

Let finance hold the company cards.

A custodian scope gives a set of logins or cards to the people responsible for them. Seal it, and every other admin sees only its name and a count. Changing its custodians needs a second custodian to agree.

  • Custodians add logins and cards and share their use with a team, from the Portal.
  • Members only ever get the use of an item, never its password or number.
  • The keys of a scope reach only the computers of its custodians and members.
About custodian scopes about Let finance hold the company cards.
Custodian scopes in Tenant Admin: Finance cards, sealed, with two custodians and a pending change; Marketing accounts, open, with one custodian.

Your people's own passwords stay their own.

The same app keeps each person's own logins, one-time codes, notes and cards in one encrypted file on their computer, opened with their master password. The organisation sees counts of personal activity at most: never a site, never an item.

  • Argon2id and XChaCha20-Poly1305, with the whole file authenticated, titles and addresses included.
  • The browser extension fills logins, codes and cards on the page the person is on, and nowhere else.
  • Import from KeePass, Bitwarden, 1Password, LastPass, Chrome, Firefox, Safari and more, then clean up where it came from.
About Trustwelt Desktop about Your people's own passwords stay their own.
The Trustwelt Desktop window: a list of logins on the left and the GitHub login open on the right, its password hidden and a one-time code counting down.

How much there is

Six products, each with its own modules, each module on its own page.

  • Trustwelt AI Security11 modules · 48 AI services · 5 agents governed · one gateway on the computer

    What goes into AI services, and what AI agents may read, run and send: decided and checked on the computer.

  • Trustwelt Vault5 modules · company logins, cards and servers · custodian scopes · usage audit

    Company logins and cards used by people, never shown to them.

  • Trustwelt Web Protection6 modules · rules in plain words · ready-made categories · every browser and program

    Which sites your computers may open, in plain rules, in every browser and application.

  • Trustwelt DLP3 modules · USB, uploads, printing, archives · about forty detectors · OCR on the computer

    What leaves a managed computer is seen, checked and recorded.

  • Trustwelt Secure MailGW4 modules · Microsoft 365, Google Workspace, your own server · hold, release, stamp

    Every message your organisation sends is checked on the way out.

  • Trustwelt Endpoint5 modules · device control · browser security · host firewall · one health score

    The computer itself: devices, browsers, firewall and health, decided by you.

What is recorded, and what never is

Every product says what it keeps, and what it never does.

This is the posture, not a footnote: written down for each product, so your people, your auditors and you know where the line is.

What each product records and never does
ProductRecordedNever
Trustwelt AI SecurityThe service or agent, the kinds of data found and how many, what happened, and the policy or rule that decided.The text, the file, the prompt or a key: the check runs on the computer, and the vault keeps the key.
Trustwelt VaultWhich company login or card was used, by whom, when, from which computer, on which site.A company password or card number on a person's screen, in a log or in an export.
Trustwelt Web ProtectionBlocks and warnings: the site, the rule, the computer, the person and when.What a person typed into a page or saw on it.
Trustwelt DLPA file that left: its name, size, fingerprint, where it went, and the kind and number of findings.The text that matched: a finding is a kind and a count.
Trustwelt Secure MailGWA message a rule matched: sender, recipients, subject, what was found and the decision.The text of a delivered message stored at Trustwelt.
Trustwelt EndpointEach control on each computer: verified, applied or configured, with the reason.A remote shell or a script run on the computer.

Who it is for

For organisations, and for you and your family.

For organisations

  • Small business: start with the product for your first problem; nothing for your people to manage.
  • Enterprise: delegated administration, AI agents in engineering governed, evidence under your own logo, a signed SIEM stream.
  • Regulated organisations: sealed custody, exports with their own fingerprint, data classes on one page.

For you and your family

  • Trustwelt Desktop: your passwords in one encrypted file on your computer, free.
  • Standard: your vault on every computer you own, and your own site rules.
  • Family: up to five people, children's computers kept protected; the organiser sees only what was blocked.

Security architecture

Security you can check.

  • Unknown ≠ trustedMissing evidence never counts as compliant.
  • MFA ≠ device trustA second factor proves the person, not the laptop.
  • No secret in an agent's reachKeys are put into a request by the gateway on the computer and wiped; an agent never holds one.
  • The model detects, the policy decidesDetectors and the names model say what they found; the published policy says what happens. No score, no threshold.
  • No remote shellControl actions are typed, signed and allowlisted.
  • One tenant, one boundaryTenant scope comes from the server, never from the request.

Every rule above is enforced by the product itself, and an Enterprise customer can review the source code of the vault that holds your passwords under agreement.

Secrets stay on the computer. Only ciphertext crosses.On the computer, the master password and the Secret Key go through Argon2id to derive the vault key, which encrypts the vault with XChaCha20-Poly1305. Across the boundary, only sealed envelopes travel to the Trustwelt cloud, which stores ciphertext, identifiers, versions and audit records, and never a key.Your computerMaster password + Secret Key128-bit key in the system key storeArgon2id512 MiB · about one secondVault keynever written to disk, never sentXChaCha20-Poly1305logins, codes, cards, notes · titles includedONLY CIPHERTEXT CROSSES9f3a·c1e07b·4d52d8·b9Trustwelt cloudSealed envelopeswrapped again at rest, AES-256-GCMIdentifiers, versions, sizesnever a title, a site or a secretIdentity, policy, device trustwhat the platform decides withAudit recordsappend-only, SHA-256 chained
The cloud stores what it cannot read: envelopes, identifiers, versions and sizes.
  • Argon2idyour vault key, derived on your computer
  • XChaCha20-Poly1305your vault, your sync envelopes, the browser channel
  • X25519 · Ed25519sharing with your family or team, your devices' identity, the keys the vault signs for agents
  • SHA-256 chainan audit your organisation can trust, that nobody can edit

Start with one product.

Tell us the problem you want to solve first. We show you the product on your own case, and an organisation account is free.