> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nextoriahub.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Overview

> Understand the architecture, data model, and design principles behind Nextoria Hub.

## Architecture

Nextoria Hub is a **single-tenant SaaS** platform with optional self-hosting. Every agency gets an isolated workspace with its own data, permissions, and branding. Workspaces are organized as follows:

```
Workspace
├── Team Members (internal)
│   ├── Roles: Admin, Developer, Designer, Marketer
│   └── Sub-workspaces per role (filtered views)
├── Projects
│   ├── Tasks & Kanban Boards
│   ├── Milestones & Budgets
│   ├── File Attachments
│   └── Client Approvals
├── Client Portal
│   ├── Per-project views (read-only)
│   ├── Invoice history
│   └── Deliverable downloads
├── Finance
│   ├── Invoices (Stripe)
│   ├── Expense tracking
│   └── Revenue analytics
└── Communication
    ├── Team channels (Stream Chat)
    └── DMs & @mentions
```

## Core Modules

<CardGroup cols={2}>
  <Card title="Project Management" icon="kanban" href="/features/project-management">
    Kanban, milestones, time tracking, budget visibility.
  </Card>

  <Card title="Client Portal" icon="users" href="/features/client-portal">
    Dedicated workspace for clients with zero access to internal tools.
  </Card>

  <Card title="Team Communication" icon="message-square" href="/features/team-communication">
    Real-time chat with channels, DMs, and file sharing.
  </Card>

  <Card title="Invoicing & Billing" icon="receipt" href="/features/invoicing-billing">
    Branded invoices, Stripe payments, revenue analytics.
  </Card>

  <Card title="File Management" icon="folder-open" href="/features/file-management">
    Cloud file explorer with Google Drive sync.
  </Card>

  <Card title="Analytics" icon="bar-chart" href="/features/analytics">
    Revenue, project health, and team performance dashboards.
  </Card>
</CardGroup>

## Permission Model

Nextoria Hub enforces permissions at **three layers**:

1. **API layer** — every endpoint validates the requesting user's role before returning data
2. **Middleware layer** — route guards prevent unauthorized navigation at the server level
3. **UI layer** — components render only the actions available to the current role

This means clients can never accidentally see internal communications or pricing, even if they manipulate the URL.

## Tech Stack

Nextoria Hub is built with modern, battle-tested technologies:

| Layer          | Technology                                  |
| -------------- | ------------------------------------------- |
| Frontend       | React 18, TypeScript, Tailwind CSS          |
| UI Components  | shadcn/ui + Radix UI primitives             |
| Animations     | Framer Motion                               |
| Real-time Chat | Stream Chat SDK                             |
| Payments       | Stripe                                      |
| File Storage   | S3 / Cloudflare R2                          |
| Auth           | SAML / SSO (Scale), email+OAuth (all plans) |

<Info>
  Looking to self-host? See [Self-Hosted Deployment](/deployment/self-hosted)
  for full infrastructure requirements.
</Info>