Security

trac deployments run inside your organisation’s network. All inbound traffic is routed through a single front-facing gateway — the metadata store, storage, and the compute service used to run jobs are never exposed directly. Data is encrypted in transit (TLS) and at rest (using the underlying storage and database service’s native encryption), and sensitive configuration — credentials, tokens, keys — is held in an external secret store rather than in plain text.

Model code is treated as less trusted than the rest of the platform. The trac runtime mediates every read and write, so models can’t access storage directly or make arbitrary network calls, and job execution is isolated by tenant.

Network	Single front-facing gateway; internal services and job execution are not directly reachable
Encryption	TLS in transit; native storage and database encryption at rest
Secrets	Held in an external secret store, never in plain text
Data segregation	Physically separated by tenant, with separate service credentials per tenant
Model code	Contained by the trac runtime and isolated by tenant; see Access management for controlling who can load and run models