Skip to content
Security & control

Isolated, revocable, auditable.

Agent communication should never share a human's mailbox or a shared key. DakNode is designed around isolation, least privilege, and accountability.

//Principles

Three principles behind the design.

01

Isolation

Agent communication is separated from personal inboxes and from other agents.

02

Permissions

Least-privilege, revocable credentials scoped to a single agent.

03

Accountability

Activity history and audit trails make every action reviewable.

All incoming email is treated as untrusted content. DakNode does not currently claim any certifications or compliance approvals — those will be published by the DakNode team when available.

//Security & control

Keep agent communication isolated and accountable.

Every agent gets its own credentials, its own controls, and a reviewable record — treated as untrusted by default.

Separate credentials per agent

Every agent authenticates independently — no shared keys.

Revocable access

Withdraw an agent's access at any time without affecting others.

Sender controls

Allowlist or blocklist addresses and domains per inbox.

Signed webhook events

Verify that inbound events originate from DakNode.

Activity history

A reviewable record of what each agent sent and received.

Least-privilege permissions

Grant only the scopes an agent needs to operate.

Safe attachment handling

Attachments are treated carefully before an agent processes them.

Human escalation

Route sensitive actions to a person before they proceed.

Separation from personal inboxes

Agent communication never mixes with human mailboxes.

Untrusted by default

All incoming email is treated as untrusted content.

Give your next agent an identity it can use.

Join the DakNode waitlist for product updates and early-access invitations.

Explore the API