Skip to content

Control what agents can see and use.

Context boundaries. Per-source permissions. Redaction policies. Retention controls. Regional residency.

Trust · Data · one tenant, one region
  1. Residency: Regional residency · tenant isolation · cryptographic boundaries.
  2. Scope: Context boundaries · Per-mission scope dictates what context an agent receives.
  3. Permit: Source permissions · Per-source allow/deny lists with policy-as-code.
  4. Redact: Redaction · PII / secrets redacted before context enters the prompt.
  5. Retain: Retention · Per-tenant retention windows with regional purge.
Uptime 99.98%
Latency 14.2ms
Nodes 128/128
trust · live Armed · 0 breaches
Data controls

Four levers per tenant.

Data passes four checks on its way to an agent. Each one is a setting your tenant owns.

  1. Context boundaries

    Per-mission scope dictates what context an agent receives.

    scope: per mission
  2. Source permissions

    Per-source allow/deny lists with policy-as-code.

    sources: allow / deny · policy-as-code
  3. Redaction

    PII / secrets redacted before context enters the prompt.

    redact: PII / secrets · before the prompt
  4. Retention

    Per-tenant retention windows with regional purge.

    retention: per tenant · regional purge

Trust posture, in five lines.

The same five lines run along every Engyn trust page. They are collected here so you can read them in one place.

The marked line is this page's subject: what an agent can reach stays inside your tenant's boundary.

trust · live
  • armed · 0 breaches ytd
  • soc 2 · iso 27001 · nist ai rmf · hipaa · gdpr
  • hardware-token gates · 412 audits / hour
  • tenant isolation · cryptographic boundaries
  • replayable decisions · tamper-evident ledger

Flip a lever. See what the agent gets.

A sample prompt context with all four levers on. Switch one off to see what it was keeping out of the agent's prompt.

your region · your tenant · prompt context Sample
  1. mission ticket reaches the agent
  2. design doc chunk reaches the agent
  3. chunk from another mission reaches the agent held back · Context boundaries
  4. records from a denied source reaches the agent held back · Source permissions
  5. customer email jane.doe@example.com reaches the agent masked · Redaction
  6. secret token tok_7f3a91c2 reaches the agent masked · Redaction
  7. record past its retention window reaches the agent purged in-region · Retention

2 rows reach the agent in full, 2 masked. 3 kept out.

Start a Software Factory pilot.

Connect one repository, one ticketing tool, and one mission. See evidence in days, not quarters.