Skip to main content

What is Nexus?

Nexus is a multi-tenant Ops OS that replaces the patchwork of SaaS tools SMEs typically juggle. Instead of switching between a helpdesk, a CRM, a warehouse management system, a shipping dashboard, and a phone system, teams log into one platform and operate from a single pane of glass.

Core capabilities

CapabilityDescription
Omnichannel InboxReceive and reply to WhatsApp, Facebook Messenger, Instagram DMs, and email from a unified inbox. Every conversation is threaded and linked to a contact record.
CRMManage contacts, companies, lifecycle stages, labels, and customer-360 views. Track touchpoints across every channel.
Order ManagementCreate, edit, and track orders. Link orders to contacts and Shopify stores. Manage fulfillment status end-to-end.
FulfillmentGenerate pick lists, assign pickers, complete picks, pack items, and hand off to shipping — all within Nexus.
Inventory & WarehousingTrack inventory items across warehouses and bin locations. Record stock movements, run cycle counts, and manage purchase orders.
ShippingCreate AWBs (airway bills), integrate with courier APIs (Bosta, etc.), print shipping labels, and track shipments in real time.
VoIP / PBXClick-to-call, real-time call monitoring, CDR sync, and call analytics via Issabel PBX integration.
AI Customer-Service AnalyticsAutomatic conversation annotation, sentiment tagging, risk flags, and CS performance dashboards powered by AI.
AutomationWorkflow triggers, abandoned-cart recovery, scheduled tasks, and integration-driven automation via n8n.

Architecture

Nexus follows a three-tier architecture:

  1. Frontend — React 18 + TypeScript SPA built with Vite, styled with Tailwind CSS and shadcn/ui components.
  2. Backend — Supabase (PostgreSQL with Row-Level Security, 117+ Edge Functions running on Deno, Supabase Auth, Supabase Storage, Realtime subscriptions).
  3. External services — WhatsApp Business API, Meta Graph API, Shopify Admin API, courier APIs, Issabel PBX, n8n workflow engine.

Multi-tenancy

Every piece of data in Nexus is scoped to an organization. PostgreSQL Row-Level Security (RLS) policies enforce tenant isolation at the database layer. Users belong to one or more organizations with role-based permissions (owner, admin, member).

Security posture

  • JWT-based authentication via Supabase Auth.
  • All API endpoints require a valid bearer token.
  • Write endpoints explicitly require authentication (marked in the API reference).
  • Data encrypted in transit (TLS) and at rest (Supabase-managed encryption).
  • No PII is exposed in public documentation; all examples use synthetic data.