Enterprise: policy, SIEM, residency, updates and WhatsApp (1.3)
For a company running Kin Browser on many machines: one policy file for all of them, the signed audit log streamed to its SIEM, data kept in the region it must stay in, updates only to versions it approved, and approvals on WhatsApp.
These build on Teams: people and roles, single sign-on, the vault,
retention. Most are set on the team's cloud machine (the hub, for example
agent.example.com) and followed by every other machine.
Policy as code
One file, kept in the team's git repository and reviewed like code:
# kin-policy.yaml
version: 7 # raise it for every change; an older version is refused
name: Acme Sdn Bhd
lock: true # the Grid shows these settings but cannot change them
sites:
block: [rival.example, gambling.example]
collection: # what agents may collect
robots: true
emails: personal # keep | personal | all (remove personal addresses, or all)
phones: true # remove phone numbers
ids: true # remove MyKad / passport numbers
perSiteMinute: 20
audit: true
approvals:
newSites: true # ask before a new website
riskyActions: true # ask before pay / delete / send / submit
limits: { steps: 400, minutes: 60, sites: 25 }
retention: { recordings: 30, audit: 730, artifacts: 14 }
ai: # goal-driven tasks
model: claude-opus-5-5
maxUsd: 2
maxTokens: 1000000
load:
hosts: [staging.acme.my] # load-lite may put many browsers on these
residency:
regions: [MY] # countries (MY, SG, EU…) or AWS regions
enforce: true
updates:
channel: https://agent.acme.my/api/v1/updates/release.jsonkin-browser policy check kin-policy.yaml # valid?
kin-browser policy apply kin-policy.yaml # this machine
kin-browser policy show # what this machine runsEvery machine. On the hub:
kin-browser policy publish kin-policy.yaml
kin-browser clients add laptop-ana # a key for each machine
kin-browser policy status # which machine runs which versionOn each machine, once:
kin-browser policy subscribe https://agent.acme.my --key kbc_…A subscribed machine asks the hub every 10 minutes and applies a newer
version. A running Kin Browser reloads the changed settings within half a
minute, with no restart. Each machine reports the version it runs, so
policy status on the hub shows ✓ or ✗ per machine.
SIEM export
The audit log is a hash chain: every line has its own hash, the previous line's hash, and a signature made with the machine's key. Stream it to your SIEM:
kin-browser siem set splunk --url https://splunk.acme.my:8088 [--index kin] # HTTP Event Collector
kin-browser siem set datadog --site datadoghq.eu # logs intake
kin-browser siem set elastic --url https://acme.es.ap-southeast-1.aws.found.io [--index kin-browser-audit]
kin-browser siem set webhook --url https://collector.acme.my/kin # any JSON endpoint
kin-browser siem status · siem now · siem offThe token is asked for and kept encrypted. Lines go every 30 seconds while
Kin Browser runs, in batches. A failure is retried next time from the same
line, so nothing is sent twice or skipped. Export starts from now; add
--from-start to send the whole log. Each line keeps its h, prev and s
fields, so the SIEM can check that nothing was changed or left out
(kin-browser audit verify does the same on the machine).
Data residency
Kin Browser keeps everything on the machine it runs on: recordings and their
pictures, the vault, the audit log, tasks, reports, downloads, saved sign-ins.
So the machine's region is the data's region. A cloud machine in
ap-southeast-5 keeps it in Malaysia.
What can leave is what a person sends out: the SIEM stream, the team library,
workspace uploads, pages a goal-driven task shows to Claude. With
residency.enforce, a destination whose region is known and outside the
policy is refused. A SIEM in datadoghq.eu under regions: [MY] does not
start. Destinations whose name does not say where they are pass, and the
report says so.
kin-browser residency report [--out residency.txt]Data residency — 2026-10-19 08:00 UTC
Policy: MY (enforced)
This machine: AWS i-0ba0e2362751b0676 in ap-southeast-5
✓ Recordings and their pictures
/home/ubuntu/.kin-browser — MY (ap-southeast-5)
…
✓ SIEM stream of the audit log
acme.es.ap-southeast-5.aws.found.io — MY (ap-southeast-5)
? Claude (tasks, write-test, portal packs)
api.anthropic.com — region unknownThe command exits 1 when anything is outside the policy, so it can run in a compliance job.
Your own update channel
Machines update only to a version someone at the company approved. On the hub:
kin-browser channel approve 1.3.0 # takes kinbrowser.com's release as it is: files and SHA-256 sums
kin-browser channel status
kin-browser channel rollback 1.2.0 # point the channel back at an earlier approved versionThe hub serves /api/v1/updates/release.json. Machines follow it when the
policy has updates.channel (above), or with KIN_RELEASE_URL on that
machine. kin-browser update, the Grid's update banner and Update now all
read it. They still download from kinbrowser.com and refuse any file whose
SHA-256 is not the one the release lists.
WhatsApp approvals and digests
Approvers get a WhatsApp message when an agent needs a person, with Allow
and Deny buttons. They can also type pending, approve <id> or
reject <id> why. Each morning they can get a digest of what the watches
found. This uses the WhatsApp Business Platform (Cloud API) on your own Meta
app and business number.
In Meta's developer site, create an app with WhatsApp. Note the phone number ID, a system user's permanent token with
whatsapp_business_messaging, and the app secret.On the hub:
kin-browser whatsapp set --phone-number-id 1234567890 --approvers 60123456789,60198765432 --digest 08:00It asks for the token and app secret (kept encrypted) and prints a verify token.
In the Meta app, set the webhook to
https://<hub>/api/v1/whatsappwith that verify token, and subscribe to messages.Each approver sends the business number a "hi" first. WhatsApp only lets a business message someone freely within 24 hours of their last message. Outside that window, an approved template is used:
--template kin_approval:en, with one body variable and two quick-reply buttons.kin-browser whatsapp test.
Only numbers on the approvers list are listened to. Every message must carry Meta's signature made with the app secret. Each decision goes in the audit log with the approver's number.
New in 1.4
SCIM provisioning
The company's directory (Okta, Microsoft Entra ID, or any SCIM 2.0 client) adds, changes and removes the people who may use the console. On the hub:
kin-browser scim token [--default-role viewer]In the directory, add a SCIM app with base URL https://<hub>/scim/v2 and
that token. Users are people: userName is their email. Assign people to the
groups Kin Browser viewers, approvers and admins to set their
role. Deactivating or removing a user in the directory removes them here and
ends their sessions at once.
Customer-managed keys (AWS KMS)
kin-browser kms enable --key arn:aws:kms:ap-southeast-5:123456789012:key/…
kin-browser kms statusThe machine key seals the vault, saved sign-ins, connected systems' tokens
and every kept secret. It is now held only wrapped by your KMS key, and the
plain copy is deleted. Each start asks KMS to unwrap it, and the unwrapped
key is kept in memory for 15 minutes at a time. If you disable the key or
take the machine's access away, those secrets cannot be opened, here or from
a copy of the disk. The machine needs kms:Encrypt and kms:Decrypt on the
key: an instance role on a cloud machine, or AWS credentials. Recordings and
reports are plain files under the data folder. Keep them on an encrypted disk
(EBS encryption with the same key does it on AWS).
Budgets and chargeback
kin-browser budgets set sales 50 # US$ a month for Kin Browser's own model
kin-browser budgets assign <api-client-id> sales
kin-browser budgets report [--month 2026-10] [--csv chargeback.csv]Every goal-driven task, written test and portal pack counts against a team,
named by --team or by its API client. A team that has spent its month is
refused, and a task that starts is capped at what is left. The report gives
each team's spend and tasks, with the people who spent it, ready for
chargeback.
Four-eyes approvals
# kin-policy.yaml
approvals:
newSites: true
riskyActions: true
fourEyes:
sites: [maybank2u.com.my, cimbclicks.com.my]
actions: [pay, delete]For these sites, and for these kinds of action anywhere, two different people must say yes. One person's yes is counted and shown ("needs a second person") until someone else agrees, and any no declines. People are told apart by their sign-in on the console, their Slack or Teams user, or their WhatsApp number.
Signed recipes and plugins
kin-browser sign keygen --out team-signing.key # once; keep the private key secret
kin-browser sign recipe check-invoice --key team-signing.key
kin-browser sign plugin ./my-plugin --key team-signing.key
kin-browser sign check recipe check-invoice# kin-policy.yaml
signing:
required: true
keys: [MCowBQYDK2VwAyEA…] # the public key keygen printedWith required, a recipe or plugin runs only if one of the listed keys
signed it, and nothing changed since. That covers a step edited, a file
added, or a recipe arriving from the marketplace or a team library. A recipe
an agent saves or repairs is unsigned until a person reviews and signs it.
Signatures are Ed25519.
New in 1.5
Data loss prevention
dlp:
patterns: [mykad, card, passport, bank-account]
custom: ['\bACME-\d{6}\b'] # your own identifiers
confidential: [Project Falcon, Q4 forecast]
allowSites: [myinvois.hasil.gov.my, payroll.acme.my]Before an agent types, chooses, fills a form or uploads a file, its text is
checked. That covers MyKad numbers (with a real date and state code), card
numbers (Luhn-checked), passport and bank account numbers, your own patterns,
and terms marked confidential. Outside allowSites, a match is refused,
nothing is typed or uploaded, and the attempt goes in the audit log.
Compliance recording
recording:
sites: [maybank2u.com.my, mytax.hasil.gov.my]
keepDays: 2555
everySeconds: 3On these sites, every agent step is kept as a picture, plus one every few
seconds while the agent stays. Each picture is encrypted with the machine key,
so with KMS on, with yours. Recordings are
kept for keepDays. For an audit:
kin-browser compliance-recordings
kin-browser compliance-recordings export 2026-10-20/ana-p1 --out audit-packThe export opens the pictures and adds a page to step through them, with who did what, where and when.
Approval workflows
kin-browser approvers hours 60123456789 mon-fri 09:00-18:00
kin-browser approvers delegate 60123456789 60198765432 --until 2026-11-15
kin-browser approvers escalate --after 30 --to 60111111111
kin-browser approvers # who is asked right nowApprovers are told only in their hours; when nobody is on duty, everyone is. While someone is away, their delegate is asked and the delegate's answer counts. Anything still waiting after N minutes goes to the escalation list, once, with how to answer.
A private marketplace
# on the hub
kin-browser marketplace publish recipe check-invoice --version 1.2
kin-browser marketplace publish plugin ./crm-sync
# on each machine
kin-browser marketplace use https://agent.acme.my --key kbc_…
kin-browser marketplace list · marketplace install recipe-check-invoiceThe company's own catalogue of recipes and plugins lives on its hub. Machines install from there instead of kinbrowser.com, each file checked by its SHA-256. When the policy requires signatures, only signed items are published, and they are checked again when they run.
Air-gapped mode
airgap:
enabled: true
allow: [intranet.acme.my, myinvois.hasil.gov.my, agent.acme.my]
model: { provider: bedrock, region: ap-southeast-1, model: claude-opus-5-5 }Agents, and Kin Browser itself (update checks, SIEM, memory sync), reach only
the listed hosts. Every navigation and request outside them is refused. The
model can run in the company's own cloud account: Amazon Bedrock
(provider: bedrock), Google Vertex AI (vertex, with projectId), or
behind its own gateway that speaks the Claude API (gateway, baseUrl).
Updates come in by hand:
kin-browser update --file KinBrowser-1.5.0-linux-x64.deb --release release.jsonThe file must be the one the release lists, by SHA-256, or nothing is installed.