KERFFLOW SECURITY
KerfFlow separates public product content from the authenticated application. Operational data is accessed through secure sign-in, workspace membership, and role-aware application flows rather than exposed on the marketing origin.
SURFACE SEPARATION
kerfflow.com serves static product information. Sign-in and authenticated screens live at app.kerfflow.com, where application routes and API traffic share the intended secure session origin.
IDENTITY AND SESSION
The application uses protected sign-in and session flows. Public pages cannot act as an authenticated proxy or read organization data.
ORGANIZATION BOUNDARIES
Inventory, cutting jobs, accepted results, and work orders belong to organization-scoped workflows. Application authorization evaluates that context before exposing or changing operational resources.
FAQ
The public site is static and has no authentication or API client. Authenticated work is served from app.kerfflow.com.
No. Operational resources are behind authenticated, tenant-aware application access.
Use the official contact path associated with your KerfFlow account or deployment so the issue can be routed without sharing sensitive details publicly.
NEXT STEP
Create a workspace or sign in at the dedicated application origin.
