Provide an alternative deployment option that uses a standard PostgreSQL setup instead of the current Supabase stack, while preserving existing functionality (auth, RLS, storage, etc.).
The goal is to make Kurrier simpler to self-host in environments where operators prefer a minimal, vanilla Postgres-based architecture. As part of this transition, we will strengthen authentication by moving to password-hash + JWT-based sessions and adding proper OIDC/SAML support. This also introduces a clearer workspace model across roles and RLS policies to enhance security, privacy and isolation across deployments.
Provide an alternative deployment option that uses a standard PostgreSQL setup instead of the current Supabase stack, while preserving existing functionality (auth, RLS, storage, etc.).
The goal is to make Kurrier simpler to self-host in environments where operators prefer a minimal, vanilla Postgres-based architecture. As part of this transition, we will strengthen authentication by moving to password-hash + JWT-based sessions and adding proper OIDC/SAML support. This also introduces a clearer workspace model across roles and RLS policies to enhance security, privacy and isolation across deployments.