Sui Foundation has introduced Sui Spheres, a proposed model for controlled blockchain execution environments aimed at institutional and enterprise workflows that require shared infrastructure without full public transparency. The initiative, announced in a May 14 blog post and promoted through Sui Network’s official X account, is positioned as a middle ground between public blockchains and fully private systems.
Sui Spheres Targets Institutional Workflows
Sui Network framed the launch around a familiar institutional concern: firms may want the benefits of blockchain-based coordination, but not the exposure, cost uncertainty, or user experience constraints that often come with public networks. “Institutions want shared infrastructure. They don’t want full transparency, unpredictable costs, or crypto-native UX. That’s been the blocker,” Sui Network wrote on X while introducing Sui Spheres.
The Sui Foundation described Spheres as “controlled execution environments for multi-party workflows,” designed for known participants that need role-based visibility, governed participation, predictable performance, and the option to connect with the broader Sui network. In the foundation’s formulation, the product is intended for use cases where multiple organizations need to coordinate through shared logic, but where not every participant should have access to the same information.
The foundation said the model is still early and is being developed with a small group of design partners across financial infrastructure, private markets, and broader multi-party systems. “This thinking is early and evolving. We’re working closely with a small set of design partners and learning in real time. But the direction is clear,” the Sui Foundation wrote in its announcement.
Controlled Visibility Meets Shared Infrastructure
The core design claim behind Sui Spheres is that selective visibility and restricted participation should not be treated as afterthoughts on a public blockchain. The foundation said Sui’s public network remains optimized for open participation, global decentralization, and shared state, while Spheres are intended for workflows where those same characteristics may conflict with institutional requirements around confidentiality, access control, and performance expectations.
Inside a Sphere, participants would be able to coordinate privately and see different parts of the same workflow depending on their permissions. “Inside a Sphere, coordination happens privately and efficiently. Different participants can see different parts of the same system depending on their role and permissions. Outside the Sphere, selected outcomes can be made visible or interoperable depending on what the use case requires,” the foundation wrote.
That structure is being pitched at workflows such as lending, collateral management, structured products, private-market infrastructure, platforms involving multiple service providers, and agent-based systems with restricted access to shared state. The foundation was careful to define the boundaries of the model, writing: “Spheres aren’t a fit for every use case. Single-tenant systems that don’t need to interact with other parties don’t require a shared environment, and fully open, permissionless workflows are already well-served by the public Sui network.”
AI Transparency Note: This article was prepared with the assistance of an AI system based on the sources listed and was reviewed, edited, and approved by a human editor before publication. All quotes, data points, and factual claims are intended to be grounded in the cited source material; however, errors cannot be ruled out entirely.