Prerequisites
- A Nexus account - we are currently in closed beta. Request access at nexus.westyx.dev
- A project and at least one service created in the console
- An API key for that service (
wxs_...for backend services,wxp_...for frontend)
Backend services use secret keys (backend services only) and can access secrets, configs, and flags.
Frontend services use public keys (browser/frontend, safe to expose) and can access configs and flags only - secrets are never sent to the browser.
The examples below use Node.js, Python, and React. Full reference for all 8 SDKs is in the SDK docs.
0. Verify connectivity (optional)
Before installing an SDK, confirm your endpoint and API key work with a plaincurl:
HTTP 401 means the key is wrong; an HTTP 404 means the slug in the URL is wrong.
You can also tail the live SSE stream:
event:resync arrive within a second. Press Ctrl+C to stop.
The
Host header is set automatically by curl to match the URL - no override needed.1. Install the SDK
2. Initialize the client
Your service endpoint is shown in the Nexus console on the service detail page.3. Read values
4. Enable live updates (recommended)
Value changes pushed from the console propagate to connected SDK clients within milliseconds.Next steps
Secrets
Learn about secret versioning, file-type secrets, and audit trail.
Feature Flags
Set up A/B rollout and targeting rules.
Workload Identity
Eliminate static API keys with WIF on Kubernetes, AWS, GCP, or Azure.
SDK reference
Full reference for all 8 SDKs.
