Trust Pack · v1
Every hop. Capability-level.
How STEADYWRK moves data — from ingress, through edge + application, to persistence + egress — without publishing a vendor clone map. Named subprocessors for procurement live on the subprocessors list for the vendor backing each node.
1. Inbound
Every request originates here
End user
browser, mobile, email CTA
AI agent
MCP client, OpenAPI consumer
Webhook
payment, identity, scheduling, messaging partners
2. Edge
Filtering and limits before the application
Edge DNS/TLS
DNS, TLS termination, geo routing
Edge protection
automated-abuse filtering
Request limits
fair-use limits per client
3. Application
App runtime — auth + business logic
App runtime
application servers
Access control
authentication for private tools
API guard
schema validation, claims-based RBAC
4. Data
Persistence + payout rails
Primary database
OLTP, AES-256 at rest, regional residency
Ephemeral store
short-lived cache
Payout processor
300+ payment rails, US 1099 + global payouts
5. Egress
Observability + operator comms
Error telemetry
error tracking with release tags, PII scrubbing
Product analytics
usage analytics, retention-bounded
Transactional email
DKIM + SPF signed operator mail
Mermaid source — paste into any renderer.
Agents + auditors can consume the machine-readable flow below directly. Solid arrows are request flow; dashed arrows are observability emissions.
flowchart TB
subgraph Inbound
U[End user · browser/mobile]
A[AI agent · MCP/OpenAPI]
W[Webhook · partners]
end
subgraph Edge
CF[Edge DNS + TLS]
AJ[Edge protection]
UR1[Request limits]
end
subgraph Application
RW[App runtime]
CM[Access control]
AG[API guard · schema + claims RBAC]
end
subgraph Data
NE[Primary database]
UR2[Ephemeral store]
DO[Payout processor]
end
subgraph Egress
SE[Error telemetry]
PH[Product analytics]
RS[Transactional email]
end
U --> CF
A --> CF
W --> CF
CF --> AJ --> UR1 --> RW
RW --> CM --> AG
AG --> NE
AG --> UR2
AG --> DO
RW -.error.-> SE
RW -.event.-> PH
RW -.email.-> RS