Trust Pack · v1

Every hop. Named.

The exact path every byte of STEADYWRK data takes — from ingress, through edge + application, to persistence + egress. Pair with 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

Clerk, Stripe, CMMS partners, Cal, Discord, WhatsApp

2. Edge

Hostile-block + bot shield + fingerprint

Cloudflare

DNS, TLS termination, geo routing

Arcjet

bot shield, WAF, rate pre-filter

Upstash Redis

sliding-window rate limits per identity

3. Application

Next.js 16 on Railway — auth + business logic

Railway

Next.js 16 runtime, auto-deploy from main

Clerk middleware

/dashboard + /portal protection, session JWTs

api-guard

schema validation, claims-based RBAC

4. Data

Persistence + payout rails

Neon Postgres

primary OLTP, AWS us-east-2, AES-256 at rest

Upstash Redis

rate-limit counters, short-lived cache

Payout processor

300+ payment rails, US 1099 + global payouts

5. Egress

Observability + operator comms

Sentry

error tracking with release tags, PII scrubbing

PostHog

product analytics, 13-month retention

Resend

transactional email, DKIM + SPF

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 · Clerk/Stripe/CMMS/Cal/Discord/WhatsApp]
  end
  subgraph Edge
    CF[Cloudflare · DNS + TLS]
    AJ[Arcjet · bot shield + WAF]
    UR1[Upstash Redis · rate limit]
  end
  subgraph Application
    RW[Railway · Next.js 16 runtime]
    CM[Clerk middleware]
    AG[api-guard · schema + claims RBAC]
  end
  subgraph Data
    NE[Neon Postgres · AWS us-east-2]
    UR2[Upstash Redis · cache]
    DO[Payout processor · 300+ rails]
  end
  subgraph Egress
    SE[Sentry · error + release]
    PH[PostHog · analytics]
    RS[Resend · 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

Security pack Subprocessors

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 · Clerk/Stripe/CMMS/Cal/Discord/WhatsApp] end subgraph Edge CF[Cloudflare · DNS + TLS] AJ[Arcjet · bot shield + WAF] UR1[Upstash Redis · rate limit] end subgraph Application RW[Railway · Next.js 16 runtime] CM[Clerk middleware] AG[api-guard · schema + claims RBAC] end subgraph Data NE[Neon Postgres · AWS us-east-2] UR2[Upstash Redis · cache] DO[Payout processor · 300+ rails] end subgraph Egress SE[Sentry · error + release] PH[PostHog · analytics] RS[Resend · 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