Platform
Your model. Your cloud. Provable.
Foundry turns your approved data into a model you own, with the evidence your risk committee needs to sign it off.
How it fits together
We ship software into your environment. Your data, weights, and logs stay there.
Deployment
Three ways to run it
Same platform and same evidence pack. You choose where it runs.
Multi-tenant SaaS
We host it. Fastest to start, lowest cost. Best for pilots and lower-risk workloads.
Single-tenant
Your own isolated instance, managed by us. Dedicated compute and storage, no shared services.
Your cloud or on-prem
Runs inside your AWS, Azure, or GCP account, or fully on-premise and air-gapped if your regime demands it. Your keys, your network, your audit trail.
| Multi-tenant SaaS | Single-tenant | Your cloud or on-prem | |
|---|---|---|---|
| Data lives in | Tensyl cloud | Your dedicated instance | Your account or datacenter |
| Encryption keys | Tensyl-managed | Customer-managed | Customer-managed |
| You own the weights | Yes | Yes | Yes |
| Evidence pack | Same | Same | Same |
| Typical fit | Pilot | Regulated production | Strict residency / air-gapped |
Table 1. Deployment options. Source: Tensyl, Sep 2026.
Continuity by design
You own it, even without us.
You keep the weights, the evals that encode how your firm judges a good answer, the data lineage, and the full evidence pack. Those evals are proprietary logic you would never hand to a closed API, and here they stay yours. If Tensyl ever goes away, your model keeps running in your own cloud and your committee keeps its documentation. No lock-in, and no custodian but you.
Control
Automated pipeline. Human decisions.
Foundry does
Ingestion, lineage, evaluation runs, evidence assembly, deployment, monitoring, rollback.
You decide
What data may be used, what counts as a failure, and what ships to production.
Request a briefing
See it on your own use case.
Request a short technical briefing. We’ll walk through Foundry on one of your use cases and what “accepted” would mean for your committee.