Departments
IT & Operations
Multi-tenant SaaS deployment, device visibility, and role separation.
IT manages Mobile App Login accounts, company profile branding, and platform isolation across companies.
- Web admin vs Mobile App Login credentials
- Company profile name, logo, and contact for reports
- Docker / cloud SaaS-ready architecture
IT & Operations
IT and operations make Axix Visitor safe to run as multi-tenant SaaS with clear credentials. They separate web admin accounts from Mobile App Login field users. Company profile branding feeds logos into PDF reports for professional exports. The stack spans Django REST, React, Flutter, Windows EXE, PostgreSQL, Redis, Docker Compose, and Nginx. Tenant isolation guarantees company data does not mix across customers. IT success is invisible when enrollment and gate just work.
Credential separation
Web admin credentials unlock configuration, doors, and reporting surfaces. Mobile App Login accounts are narrower field credentials for enrollment on phones. Separating them limits damage if a field device is lost or shared. Password rotation and offboarding should cover both account types. Shared logins are the fastest way to lose audit clarity. Credential separation is basic hygiene that the product is designed around.
Company profile
IT or facilities sets company name, logo, and contact for branded PDFs. Correct branding makes audit packets look intentional and trustworthy. Profile updates after rebrands avoid shipping outdated logos for months. Support teams also use profile context when diagnosing tenant issues. Company profile is a small form with outsized external credibility. Configure it before the first customer-facing report export.
Stack overview
Django REST is the API backbone for every client channel. React serves Web Admin while Flutter serves the mobile visitor app. Windows EXE kiosks handle Face and QR with camera hardware at the door. PostgreSQL stores data; Redis supports jobs such as overdue checks. Docker Compose and Nginx shape typical production packaging and edge routing. Stack overview helps IT size servers and plan monitoring.
Isolation guarantee
Tenant scope ensures one customer cannot see another customer’s visitors. Isolation applies to enrollment, gate events, emails, and exports alike. SaaS buyers should validate this boundary during security review. Misconfiguration risk is reduced when roles and credentials stay separated. Isolation guarantee is the platform claim every other feature relies on. IT owns proving it in architecture discussions.
IT ownership on Axix Visitor
IT keeps tenants, devices, and channels healthy for everyone else.
Tenant isolation checks
Validate company scoping before production enrollments begin.
Kiosk connectivity
Windows gate EXE must reach the API reliably across site networks.
Mobile login provisioning
Field accounts should map to the right employees without over-permissioning.
IT runbooks worth writing
Document the failures reception will call about.
Face index after bulk enroll
Know how FAISS updates behave when many visitors are imported at once.
Door offline triage
Steps from Door Access red status to network check to vendor escalation.
Report job failures
PDF/CSV generation issues often sit in background jobs — include Redis health checks.
IT success metrics
Measure platform health, not just ticket volume.
Gate uptime by location
Track how often kiosks or doors go offline during business hours.
Failed recognition rate
Rising face failures may signal camera, lighting, or enrollment photo quality issues.
Next step
See this flow in a live demo
Transform your front desk with secure visitor management.
Register guests, check them in with face or QR, alert hosts by email, and export complete visitor reports.