Tresor now runs across five providers in total, with broader overlap on several of the most used models. That gives the platform more room to recover when one upstream slows down, rate-limits, or has a bad day.

The benefit is simple: more overlap means better fallback. Instead of a popular model depending on a single route, Tresor can now keep more requests moving through alternative routes while maintaining the transparency you are used to.

More ways through

• Broader model overlap - More of the popular models now exist on more than one provider, which reduces single-route risk.

• Stronger fallback behavior - When one upstream has trouble, Tresor has more chances to route around the issue before your app feels it.

• Better availability in practice - This wider provider layer helps improve the consistency you see in day-to-day use, not just in theory.

Built for production workloads

This matters most for products and agents that need steady behavior under real traffic. With five providers in the pool, Tresor is better positioned to absorb isolated provider problems while keeping the same private, attested execution model.

Privacy: Expanding fallback does not change the zero-access design. Your requests stay inside the same sealed, confidential path.

If you rely on Tresor for live features or long-running agents, this is the kind of infrastructure change that quietly pays off every day.