Multi‑Tenant Policy

This Multi-tenant Policy is effective dated: June 01, 2024

Control Document: GEF-PP-031, Ver. 1.0

Purpose

To establish guidelines for segregating and managing multiple customer environments on the galaxefi platform while ensuring security, performance, and compliance.

Scope

Applies to all Galaxefi modules, tenants (freight forwarders, carriers, trade entities), internal staff, third-party integrators, and support teams.

Policy Details

  • Tenant Isolation: Each tenant’s data and configurations are securely siloed, with logical separation in databases, file storage, and application logic.
  • Data Access Controls: Tenant admin and user roles are scoped to their own data; no cross-tenant visibility is allowed.
  • Resource Quotas & Performance: CPU, storage, and API usage limits are enforced per tenant to prevent resource contention.
  • Compliance & Auditing: Tenant-specific logs are maintained and audited independently; data residency policies (e.g., GDPR, PDPB) are enforceable per customer.
  • Onboarding & Offboarding: New tenant environments are provisioned automatically via DevOps pipelines. On offboarding, data is archived and purged per the Data Retention Policy (GEF PP 008).
  • Support & Escalations: Support tickets and incidents are tracked separately per tenant; escalation paths align with the Support and Response Time Policy (GEF PP 018).

Policy Review and Updates

  • This policy will be reviewed annually and updated as necessary to ensure its effectiveness and alignment with industry best practices and regulatory requirements.
  • Changes to this policy will be communicated to all employees and stakeholders.

Quick Contact

By adhering to this Multi-Tenant Policy, galaxefi commits to ensuring the security, performance, and compliance of each tenant in separate environments. For questions or concerns about this Policy, please use the following form: