Shared workspace data with clear ownership boundaries.
Namensi combines server-side authorization, database-backed workspace integrity, bounded public access, and separated payment processing.
Workspace boundaries
Shared product records use workspace ownership and server-side authorization. Same-workspace relationships are enforced at application and database layers where appropriate.
Authentication
Account access uses server-validated sessions. Users should protect email access, use a unique password, sign out from shared devices, and report unexpected activity.
Server enforcement
Inputs are validated against shared schemas. Membership, workspace ownership, and paid entitlements are checked on server mutations—not only hidden in the interface.
Public access controls
Public catalog search is bounded, query-gated, validated, and rate-limited. Production ingress must supply trusted request-address handling.
Payment separation
Polar processes Plus checkout. Namensi stores product, customer, transaction, and entitlement references, but not payment-card numbers.
Operational readiness
Production requires owned backup and restore procedures, restricted operator access, environment validation, migration checks, and monitoring of security-relevant failures.
Security claims
Namensi does not currently claim an external security certification or independent penetration-test attestation.
Report a vulnerability
Email change-me-before-public-launch@example.invalid with subject “Namensi security report,” affected URL, reproduction steps, and impact. Do not access other users’ data or disrupt service.