Project isolation
Workspace ownership is checked on the server for every read and write, and the acting account comes from your session rather than from the request. One workspace cannot reach another's projects.
SECURITY
Private by design. Evidence over assumptions.
Florgin treats generated code, product rules and build artifacts as customer data—not training material.
Private code
Private project code is processed only for requested generation, review and repair actions. It is not used to train models.
Controlled deployment
Production deployment is never triggered without an explicit user action. Integration credentials are held separately from project content and are never written into generated output.
Need a more specific answer?We are happy to talk through security, privacy or product architecture.
1florginai@gmail.com