Local Certificates for Studio
How to keep a local Provider connection compatible with the HTTPS Studio web app without exposing internal service details.
Why Certificates Matter
Studio runs over HTTPS, so browsers require any local Provider connection used by Studio to be served over HTTPS as well. Without a trusted local certificate the browser can block requests as mixed content or mark the connection as unsafe.
Recommended Setup
Use the certificate process documented by the Provider repository you are running. In local development this is usually a developer certificate trusted by your machine; in hosted environments it should be a normal certificate issued for the Provider domain.
The certificate files and environment variable names are implementation details of the Provider deployment. Keep those details in the Provider repository or in private runbooks, not in public website content.
What To Verify
- The Provider URL you register in Studio uses
https://. - The certificate is trusted by the browser where Studio is opened.
- The Provider health endpoint is reachable before you connect trading workflows.
- No private key, token, exchange secret, or local-only path is copied into Studio notes.
For exact local commands, use the current trading.apps/docs/ai/local-provider-stack-runbook.md and the Provider deployment configuration in the owning repository.