Production Overview

This section starts after your chart integration works in development. It covers the additional controls that apply when you release that integration to users: the licensed SDK build, deployment authorization, production assets and network policy, release verification, and ongoing operations.

Outcome

You can identify the values required for a licensed production release and follow one path from authorization through rollback.

Before you start

• A working chart integration with its production datafeed, broker, and storage boundaries identified
• A TradeScript commercial agreement and deployment contact

Done when

Every production responsibility has an owner, and the release team knows which page to follow next.

Typical time

5 minutes

Production path

Follow the pages in that order for a first production release. For later releases, start at Upgrades and rollback.

What changes in production

Concern	Production requirement
Licensed build	Use the exact customer SDK artifact and version supplied for the deployment.
Browser origin	Run the customer build only on origins approved for that deployment.
Capabilities	Request only the modules, chart features, indicators, drawing tools, trading operations, workers, and limits included in the deployment policy.
Authorization	Keep the permanent credential on your backend and send only a time-limited deployment lease to the browser.
Assets and network	Serve matching styles and worker assets, and allow the required data, broker, storage, and worker origins through CORS and CSP.
Supply chain	Retain the bill of materials shipped with the build, and verify the delivered files against the digests it records.
Release evidence	Verify the deployed artifact, enabled integrations, failure states, and teardown before promotion.
Operations	Monitor structured SDK errors and retain enough redacted evidence to identify the first failing boundary.

The TradeScript deployment lease authorizes the SDK build and its licensed capabilities. It does not authenticate your users or replace your tenant, market-data, broker, storage, account, or risk controls.

Values supplied or confirmed during onboarding

Before implementation begins, your TradeScript deployment contact should provide or confirm:

• the customer package and exact SDK version;
• the customer build fingerprint used during lease exchange;
• the approved browser origins;
• the licensed capability policy;
• a credential ID and secret for your backend; and
• the TradeScript support or escalation channel for the deployment.

Keep those values in deployment configuration rather than copying them into individual chart implementations. If any value is missing or does not match the planned environment, resolve it before building the authorization endpoint.

Responsibility boundary

TradeScript	Your application team
Supplies the licensed customer build and its release identifiers	Pins and deploys the supplied build and matching assets
Ships a CycloneDX bill of materials with every build	Retains it per release and verifies the delivered files against it
Registers approved origins and capability policy	Confirms the exact development, staging, and production origins
Issues deployment leases after a valid credential exchange	Stores the credential, caches and renews leases, and delivers them to browsers
Enforces the signed deployment policy in the SDK	Enforces user, tenant, data, storage, broker, account, and risk authorization
Publishes release notes and deployment-specific actions	Verifies upgrades and preserves a tested rollback release

Next steps

Read License model before implementing authorization. It explains how the commercial license, customer build, deployment record, credential, and browser lease relate to each other.