Core Platform Concepts
Understand the foundational primitives powering GN-Apex: multi-tenancy, workspace engines, identity separation, and cryptographic access boundaries.
“Keep customer profiles, billing streams, and developer credentials strictly partitioned per project.”
Organizations & Tenancy
An Organization is the root billing and administrative entity. It owns pooled Resource Vaults (SMS, WhatsApp, and AI credits), Billing Wallets, custom storage providers (BYOS), and team membership rosters.
Project Nodes & Edge Routing
A Project Node represents an individual web app, mobile backend, or digital portal. Each project receives:
- A provisioned edge subdomain (
[subdomain].gnapex.com). - A dedicated Next.js cache bucket on Cloudflare R2 (
[subdomain]-cache-r2). - An isolated Cloudflare D1 database for tag-based ISR cache invalidation.
- Independent CMS schemas, assets, and analytics streams.
Workspace Operational Modes
Projects operate under specific workspace modes that unlock tailored data schemas and automated services:
General Workspace
Corporate frontends, blogs, and SaaS platforms with dynamic page builders and forms.
Education Engine
Schools and universities: student admissions, NECTA CSV results ingestion, attendance, and PDF report cards.
Non-Profit & NGO
Charities and trusts: fundraising campaigns with A/B testing, donor CRM, grants, and tax certificates.
E-Commerce & Retail
Online storefronts: product variants, stock logs, TRA VFD fiscal receipts, and cart recovery.
SiteUsers vs. Platform Members
GN-Apex maintains a strict security boundary between internal dashboard operators and public end-users:
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| OrganizationMember | Dashboard Staff | Required | Operators (Owners, Admins, Editors) managing settings, answering inbox threads, or reviewing finances. |
| SiteUser | End-User Identity | Required | Public project visitors (students, donors, customers) authenticated via client-facing apps without dashboard access. |
API Key Hierarchy & Scopes
Every project node generates cryptographic keys enforcing least-privilege security boundaries:
nx_pk_live_*(Public Key): Read-only key safe for client-side JavaScript. Grantscontent:readandanalytics:writescopes.nx_sk_live_*(Secret Key): Full-privilege key strictly reserved for server environments, CLI deployments, and automated background syncs.