sfp pro server had the following requirements that shaped the need for using Supabase as foundational system
Handle authentication and authorization seamlessly for both users and applications
Provide real-time state management to replace our previous Git-based approach
Work equally well in both cloud and self-hosted environments
Scale independently for each organization's needs
Ensure complete data isolation between organizations
Authentication in sfp pro server is built entirely on Supabase Auth, which provides several key advantages:
First, it offers built-in support for multiple authentication methods while maintaining a consistent security model. When users log in through OAuth providers (in FLXBL-managed instances) or through an organization's own authentication system (in self-hosted instances), Supabase Auth handles all the complexity of token management and session control.
Second, it provides a JWT-based authentication system that seamlessly integrates with both interactive users and automated systems. This means whether a request comes from a developer using the CLI, a CI/CD pipeline, or the Codev desktop application, the authentication flow remains consistent and secure.
Each organization in sfp pro server receives its own dedicated Supabase instance. This architectural decision provides several benefits:
This isolation ensures that:
Each organization's data remains completely separate
Performance and scaling can be managed independently
Security boundaries are enforced at the infrastructure level
Organizations maintain control over their data governance
One of the most significant improvements Supabase brings to sfp pro server is in state management. Previously, we stored state information in Git repositories, which led to several challenges:
State updates required Git operations
Real-time visibility was limited
Concurrent updates were difficult to manage
Performance was constrained by Git operations
Supabase's real-time capabilities transformed this approach:
This real-time capability enables:
Immediate visibility into operation status
Live updates without polling
Efficient resource state tracking
Consistent state management across all components
The ability to self-host Supabase instances was crucial for organizations that need to maintain their systems within their own infrastructure. Supabase's open-source nature and comprehensive deployment tooling make this possible while maintaining feature parity with cloud deployments.
When an organization chooses to self-host sfp pro server, they get:
Complete control over their Supabase instance
The ability to integrate with internal systems
Custom backup and retention policies
Direct access to their data and logs