Security

Security is foundational to NexaCore ERP, not an add-on. As a multi-tenant platform trusted with finance, HR, and operational data across many organisations, we design every layer — from the database schema to the API — to keep each customer’s data private, available, and intact.

This page summarises the controls and practices we use. It is informational and complements our Terms of Service and Privacy Policy.

NexaCore uses a schema-per-tenant architecture. Each customer company operates in its own isolated PostgreSQL schema — the schema boundary is the company boundary. This provides strong separation of data between tenants at the database level, not merely a filter in application code.

• Every tenant has a dedicated schema with its own tables, users, and configuration.
• Cross-tenant data access is structurally prevented by the isolation model.
• Tenant provisioning and de-provisioning are automated, and schema removal fully removes a tenant’s data.

Data is encrypted in transit using TLS for all connections to the Service. Data at rest is protected using industry-standard encryption provided by our infrastructure. Authentication tokens and secrets are stored using one-way hashing or encryption as appropriate.

Access to data is governed by granular, role-based access control (RBAC). Permissions are declared in a central catalog and enforced consistently across every authenticated endpoint.

• Fine-grained permissions follow a module.resource.action model and are gated at the API layer.
• Administrators assign roles to control exactly what each user can see and do.
• Multi-factor authentication (MFA) is supported to strengthen sign-in.
• Session and login activity are available for review, and sessions can be revoked.

The Service runs on hardened, cloud-native infrastructure. We apply network segmentation, restrict administrative access, keep systems patched, and use caching and async task queues that are isolated from public access. Internal services communicate over private networks wherever possible.

We maintain logging and monitoring to detect anomalies and support investigations. Security-relevant actions are recorded with an audit trail, helping both our team and administrators understand who did what and when.

We perform regular backups and design for recoverability. Backup artifacts are stored securely and access to them is restricted. Our deployment process uses automated, zero-downtime migrations to reduce the risk of disruption during updates.

Security is built into our engineering process:

• Code review and automated checks run in continuous integration before changes ship.
• Architectural guardrails enforce critical invariants — for example, tenant isolation and permission coverage are validated automatically.
• Dependencies are monitored and updated to address known vulnerabilities.

We monitor for vulnerabilities across our application and dependencies, prioritise remediation by severity, and apply fixes promptly. Material security issues are addressed as a priority and, where required, affected customers are notified.

Our security program is designed to support our obligations under applicable data-protection laws. We process personal data in line with our Privacy Policy, support data-subject rights, and enter into data-processing agreements with customers and sub-processors where required.

Security is a partnership. We secure the platform and infrastructure; you help protect your workspace by managing user access carefully, enabling MFA, using strong unique passwords, and promptly removing access for departing team members.

We welcome responsible disclosure. If you believe you have found a security vulnerability, please contact us through our contact page with details and steps to reproduce. We ask that you give us reasonable time to investigate and remediate before any public disclosure, and that testing does not disrupt the Service or access data that is not yours.