01
Tenant Data Isolation
Every customer organization operates in an isolated workspace. All queries, license checks, and support records are bound to the authenticated organization identity.
AVAILABLE
Security & Trust
Trust through boundaries, access control and governance.
SMRITISYS and SMRITI Retail OS are intentionally separated so public discovery, customer relationships, and operational retail execution each have a clear responsibility, governing model and accountability path.
Organization context
Role-based access
Audit accountability
Clear Operating Separation
How the Architecture Protects Your Data
We maintain a clear division between relationship management and store operations. The public website explains, the Control Plane manages, and SMRITI Retail OS runs the business.
1
SMRITISYS Control Plane
Discover + Manage
Handles identity, license entitlements, support requests, and release cataloging with authenticated customer sessions and organization-level filtering.
- ✓ PBKDF2 password hashing & server-side session invalidation
- ✓ Request-only customer workflows (no direct license mutation)
- ✓ License events and administrative audit logs
2
SMRITI Retail OS
Run Your Business
Is the separate operational application for store POS, inventory, purchasing, sales and daily retail work. Availability depends on edition, deployment stage and implementation scope.
- ✓ Separate operational product boundary
- ✓ Deployment-dependent operating workflows
- ✓ Retail operations kept distinct from the Control Plane
Security Architecture
Core Security & Trust Principles
Engineered from day one for enterprise governance and resilience.
02
Role-Based Access Control
Granular permission catalog enforces separation between customer viewers, store operators, internal support staff, and system administrators.
AVAILABLE
03
Cryptographic Identity
Password storage utilizes PBKDF2-SHA256 with 120,000 iterations. Sessions are server-side managed with instant revocation upon logout or password modification.
AVAILABLE
04
Auditable Events
License state changes, entitlement adjustments, and administrative events are stored in append-only tables protected by database-level update prevention triggers.
AVAILABLE
05
Governed License Mutations
Customers cannot modify license counts, editions, or validity directly. Change actions create verifiable request records requiring administrative approval.
AVAILABLE
06
Deployment Independence
Deployment, infrastructure and data ownership depend on the selected operating model and implementation scope.
DEPLOYMENT DEPENDENT
Honest Governance
Capability Availability Framework
Every capability across SMRITISYS and SMRITI Retail OS is clearly classified by operational readiness.
AVAILABLE
Fully implemented, tested, and actively deployable.
IN ACTIVE ROLLOUT
Progressively introduced as deployment evidence is established.
DEPLOYMENT DEPENDENT
Configured based on store topology, hardware, and network environment.
EMERGING
In validation with early deployment pilots.
PLANNED
On our public architectural roadmap for future release cycles.
DEPLOYMENT DEPENDENT
Enterprise controls depend on deployment and implementation scope.
Discuss your security & deployment requirements.
Our team can walk through your infrastructure topology, data isolation needs, and compliance roadmap.