Skip to main content

Customer Deployment Recipes

TradeScript Agent Console projecting session grants that remain consistent across customer deployment topologies
Loopback, small-business, and enterprise deployments use the same customer-owned session and grant projection.

All three recipes use the same packages and six MCP tools. They differ only in the infrastructure and controls the customer supplies.

Individual local testing​

Use this path for one developer and one browser on the same computer.

  1. Install @tradescript/pro, @tradescript/react-widgets, and @tradescript/chart-mcp.
  2. Start npx tradescript-chart-mcp stdio from the MCP client.
  3. Attach the browser to the printed loopback WebSocket URL with the printed process token.
  4. Mount Agent Console with { kind: 'loopback' } and begin read-only.
  5. Mount a customer-owned paper broker only when testing simulated orders.
  6. Stop the process and detach the browser to revoke the session.

This path has no remote domain, customer database, model backend, or TradeScript runtime dependency. Do not expose the loopback bridge publicly.

Small hosted business​

Use this path for one customer domain and a bounded user population.

  1. Run the generic gateway container on the customer's HTTPS/WSS origin.
  2. Authenticate issue, revoke, rotation, and MCP requests through the customer's existing identity layer.
  3. Implement SelfHostedSessionStore in the customer's database or Redis.
  4. Start in single-replica mode, or provide a shared bridge router before enabling more replicas.
  5. Restrict allowedOrigins to the exact customer application origin.
  6. Send audit events and metrics to customer-owned observability and retention.
  7. Connect AgentChatWidget only to the customer's model backend; keep provider keys server-side.
  8. Certify paper-order lifecycles and revoke behavior before onboarding users.

Enterprise multi-tenant​

Use this path when tenants, principals, regions, or replicas must be isolated.

  1. Bind every session to authenticated tenantId and principalId facts.
  2. Supply a shared atomic SelfHostedSessionStore and shared SelfHostedBridgeRouter.
  3. Run multiple gateway replicas behind TLS and session affinity for Streamable HTTP MCP sessions.
  4. Authorize every issue, rotate, revoke, bridge, MCP connection, and MCP request against the bound tenant and principal.
  5. Partition audit, logs, retention, encryption keys, and incident access by the customer's governance rules.
  6. Test cross-replica routing, tenant-confusion attempts, hostile origins, expiry, token rotation, immediate revocation, shutdown, and regional failover.
  7. Pin the selected model campaign and publish the complete control matrix, traces, package hashes, and chat-provider HTTP-fetch evidence for each release. Package evidence must include all three .tgz artifacts; the QA API opens each packed manifest and verifies its claimed identity, version, required public entries, binary entries, and target files before hashing. Capture MCP, browser attachment, WebSocket, and fixture traffic separately before claiming whole-flow network egress.

TradeScript supplies the libraries and generic examples only. Product-boundary and financial wording still require the customer's legal and compliance review; this architecture does not guarantee a regulatory exemption.