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

# What is Westyx Nexus

<div style={{ display: 'flex', alignItems: 'center', gap: '2rem', marginBottom: '1rem' }}>
  <img src="https://mintcdn.com/westyx/SZvVVOurEPriggFG/nexus-logo.webp?fit=max&auto=format&n=SZvVVOurEPriggFG&q=85&s=6ffbf78ce14ec5ee73fe3b569f8953a9" alt="Westyx Nexus" style={{ width: '100px', height: '100px', borderRadius: '18px', flexShrink: 0 }} width="1024" height="1024" data-path="nexus-logo.webp" />

  <div style={{ fontSize: '1rem', opacity: 0.7, lineHeight: 1.6 }}>
    One place for every secret, config, and feature flag across all your clients and environments.
    Built for agencies and product teams that run more than one project - with a full audit trail and live push built in.
  </div>
</div>

## The problem it solves

Every project needs credentials, configuration, and feature toggles. Multiplied across clients and environments, this becomes dozens of `.env` files, shared passwords, and no audit trail.

Nexus replaces all of it with one platform:

* **Secrets** - AES-256-GCM encrypted, versioned, never logged
* **Configs** - typed, per-environment, with template refs (`{{secret:KEY}}`, `{{flag:KEY}}`)
* **Feature flags** - boolean + scheduling + A/B rollout with targeting rules

## Core features

<CardGroup cols={3}>
  <Card title="Secrets" icon="lock" href="/features/secrets">
    AES-256-GCM encrypted. Versioned, audited, never exposed in logs.
  </Card>

  <Card title="Configs" icon="sliders" href="/features/configs">
    Typed, per-environment values. Reference secrets and flags by key.
  </Card>

  <Card title="Feature Flags" icon="toggle-on" href="/features/feature-flags">
    Boolean flags with scheduling, A/B rollout, and targeting rules.
  </Card>
</CardGroup>

## Key concepts

* **Tenant** - your top-level organisation (one per company or agency)
* **Project** - one app or product within a tenant, with its own tier
* **Service** - a single backend or frontend deployment, with its own API key
* **Environment** - `develop`, `staging`, `production` (availability depends on tier)
* **Umbrella service** - a shared config parent that child services inherit from

<CardGroup cols={2}>
  <Card title="Architecture overview" icon="sitemap" href="/concepts/architecture">
    Understand the Tenant → Project → Service hierarchy.
  </Card>

  <Card title="5-minute quickstart" icon="rocket" href="/quickstart">
    Integrate Nexus into your first service in minutes.
  </Card>

  <Card title="SDK overview" icon="code" href="/sdks/overview">
    Go, Node.js, Python, .NET, Spring Boot, Angular, React, Vue.
  </Card>
</CardGroup>