Connected Applications
Applications built on Simezu's shared identity and authorization model
Simezu provides a single identity, permission, and session layer across multiple applications. Each connected application inherits the same user model, authorization decisions, and session state, while maintaining its own application-specific data and business logic.
Current Applications
Simezu Core
The central platform that manages identity, authorization, and session state for all connected applications.
- Central user and group management
- Permission evaluation and authorization decisions
- Cross-application session management
- Payment profile and ownership context
Simezu Core is the foundation layer. All other applications query Simezu for identity, permissions, and context rather than maintaining their own authentication systems.
Wemazu
Deployment and project management that uses Simezu for authentication and authorization while managing its own workflows.
- Cross-application session sharing
- Centralized permission evaluation
- Projects and deployments
- Application-specific business logic
Wemazu illustrates how applications maintain their own data and workflows while relying on Simezu for all identity and authorization. Users authenticate once and access Wemazu with the same session and permissions they have elsewhere.
Simuze
Music discovery and network built on Simezu's identity, session, and permission model.
- Single sign-on using Simezu sessions
- Permission-based access control from Simezu
- Shared user and group context
- Centralized user context
Simuze shows how applications delegate identity and authorization to Simezu. The application focuses on music discovery and community while all authentication and permission decisions come from Simezu.
How Applications Benefit from Simezu
All connected applications share the same identity model. When a user logs in, they authenticate to Simezu, not to individual applications. Their session, permissions, and group memberships are consistent across all applications.
- Applications receive identity and permission information from Simezu, not from their own systems
- Authorization decisions are made centrally, ensuring consistency across applications
- Sessions are shared, so users don't need to log in separately to each application
- Group memberships and ownership relationships are consistent across the ecosystem
Future Applications
New applications can be added to the Simezu ecosystem without affecting existing applications. Each application has its own namespace for groups, roles, and permissions, while sharing the same user identity space.
Inherited Model
New applications automatically inherit Simezu's identity, permission, and session model without additional configuration.
Isolated Data
Each application maintains its own application-specific data and business logic, isolated from other applications.
Shared Context
Applications can query Simezu for user context, permissions, and ownership relationships relevant to their domain.
Consistent Authorization
All applications receive the same authorization decisions from Simezu, ensuring consistent access control across the ecosystem.
Application Responsibilities
Applications built on Simezu are responsible for:
- Enforcement: Respecting and enforcing authorization decisions provided by Simezu
- Data Storage: Managing application-specific data and business logic
- User Interfaces: Building and rendering application-specific user interfaces
- Workflows: Implementing application-specific workflows and business processes
Applications are not responsible for authenticating users, making authorization decisions, managing user credentials, or maintaining permission state—these are all handled by Simezu.