How Aperyx is actually built
Not a single monolith wearing different skins — five real applications, one system of record, and a multi-tenant data model that keeps every company’s data hard-isolated from every other.
Five applications, one platform
Each one exists because it’s the right tool for a specific job, not because of accidental sprawl.
Aperyx Core
Backend · System of Record
The system of record. A multi-tenant REST API that owns every model, every integration credential, and every background job. The dashboard, mobile app, and kiosk console are all just clients of this one backend — none of them hold business data of their own.
Aperyx Dashboard
Staff Dashboard & Public Site
The staff dashboard used by Company Admins, Property Managers, Security, and Service Techs to run day-to-day operations — plus Aperyx’s own public site, including the page you’re reading now.
Aperyx Mobile
Tenant Mobile App
The tenant-facing app: leases, invoices, payments, maintenance requests, identity verification, and guest access — self-service from a phone, with no staff involvement needed for the everyday things.
Aperyx Vision
Live Camera & AI Alerts Service
A standalone service dedicated to live camera streaming and real-time AI-detection alerts. Kept separate from the core backend deliberately — proxying live video and holding open a persistent alert feed is a poor fit for a request/response web service.
Aperyx Hardware
Kiosk Console
A dedicated console for wall-mounted monitors and guard-desk screens, pinned to a single company per physical device — built to run unattended for hours, not as another tab in someone’s browser.
One database, hard boundaries between companies
Every tenant-scoped model carries a company reference, and the query layer filters to the current company automatically — a query written without explicit filtering still can’t leak another company’s data by accident.
Aperyx Dashboard and Aperyx Mobile never talk to a database directly — every read and write goes through Aperyx Core, which resolves the requesting user’s company before any query runs.
Camera devices stay owned by Aperyx Core’s own RBAC and credential storage; Aperyx Vision only ever proxies a stream or alert once Aperyx Core has already authorized it.
Roles & permissions
Six fixed roles are baked into the API itself — access is enforced server-side, not just hidden in the interface.
Company Admin
Full company oversight — access log review, staff, finance, and integrations.
Property Manager
Day-to-day operations across their assigned properties — leasing, invoicing, maintenance, visitor access.
Security
Cameras, alerts, and visitor access — granting and revoking guest passes at the gate.
Service Tech
Maintenance requests and inspections, scoped to the properties they work on.
Tenant
Self-service from the mobile app — their own lease, invoices, requests, and guests only.
Super Admin
Platform-level oversight across every company, for Aperyx’s own operations team.
Custom roles, layered on top
A Company Admin can define additional roles from a fixed capability registry (properties, leasing, invoicing, maintenance, hardware, owners, staff — each with view/manage granularity) and grant them to specific staff. These widen access on top of the six base roles; they never replace or weaken them.
Core modules
The business capabilities the backend is actually organized around.
Properties & Units
Property and unit records, bulk import, document storage scoped to staff vs. tenant visibility.
Leasing
Lease lifecycle — creation, e-signature, renewal, amendment, and termination — each change reconciling future invoices automatically.
Invoicing & Payments
Rent and utility billing, partial payments, late fees, and opt-in recurring auto-pay against a saved card.
Maintenance & Inspections
Work-order lifecycle with technician assignment, plus scheduled property inspections with document capture.
Owner Relations
Ownership records, distributions, and statements — kept separate from day-to-day operational access.
Budgeting, Expenses & Reporting
Property and company budgets, CapEx planning, debt-service coverage, and portfolio reporting.
Procurement
Purchase requisitions with multi-step approval, purchase orders, vendor management, and vendor invoice payment.
Staff, Roles & Access
Six fixed roles plus an additive custom-role system a Company Admin can define from a fixed capability registry.
Work that shouldn’t block a request
Anything that could be slow or unreliable — sending a notification, pushing to a third-party gate system, charging a saved card — runs as a background job rather than making a person wait for it.
- Rent invoices generated and sent on schedule, then marked overdue with late fees applied automatically
- Recurring auto-pay charges each lease’s saved payment authorization against the invoice currently due
- EvTrack visitor-access events polled every few minutes, so arrivals/departures at real gate hardware stay in sync
- Expired one-time PINs and lapsed subscriptions cleaned up on a recurring schedule
Connected to the tools already in use
Payments
Paystack, PayFast, and other regional gateways for rent and utility collection, with one set as the company default.
Visitor Access
EvTrack’s Web Services API for real gate hardware — access granted from the dashboard or a tenant’s phone shows up at the actual gate.
Cameras
Hikvision devices, streamed live through Aperyx Vision with real-time AI-detection alerts.
ERP & Calendar
Oracle ERP property data sync, plus Microsoft and Google calendar integration.
Communications
Transactional email and SMS providers for invoices, OTPs, and notifications.
Identity Verification
Digital KYC for tenants and staff, with a company-admin review queue for documents and risk signals.
An AI assistant with the same permission boundaries as everyone else
Aperyx Assist answers questions and takes action across leasing, invoicing, maintenance, and staff — but every action it can take is drawn from a fixed tool registry, gated by the same role-based permissions as the rest of the platform. A user can’t get Assist to do something their own role couldn’t already do directly.
Execute immediately — looking up an invoice, logging a maintenance request, resending an email.
Require explicit confirmation first — anything that moves money or changes billing/subscription state.
Runs on managed, isolated infrastructure
A managed database for data, a dedicated queue for background jobs, containerized deployment with automated backups and continuous error monitoring. Full detail on access control, encryption, and identity verification lives on the Security page.
Containerized deployment
Managed database
Automated backups
Encrypted credentials
See the full feature set, or the API
This page covers how it’s built. Platform Capabilities covers what it does.