Nexus client-hub
The unified gateway for the Nexus ecosystem. Use the client-hub to manage multiple instances and bridge your identity across origins.
Audience: Power users, admins, and teams managing multiple Nexus environments.
Current Version
1.0
Documentation aligned to the current operational build of Chat, Automations, Contacts, and workflow runtime.
Scope
1
A standalone documentation page with a stable URL you can share directly.
Quick Start
How the system is meant to be used
Step 1
Read the platform overview first so you understand how Chat, apps, and runtime work together.
Step 2
Start your first conversation in Chat with a real business outcome, not just a general prompt.
Step 3
Let Nexus turn that intent into a durable record, workflow, or next-step artifact.
Step 4
Connect the systems required for context, communication, and execution as setup requires.
Step 5
Move into the relevant app surface to review, manage, approve, and operate the resulting work.
Operating Principle
Chat compiles. Apps operate. Runtime executes.
Nexus is not a chatbot that happens to call tools. It is a structured operating system where conversational intent is translated into durable records, validated state, and auditable actions.
This docs site is the product-level reference for how that model works today and how the current 1.0 surfaces fit together.
Audience
Power users, admins, and teams managing multiple Nexus environments.
Nexus client-hub
The unified gateway for the Nexus ecosystem. Use the client-hub to manage multiple instances and bridge your identity across origins.
Philosophy
Your workspace should be everywhere you are. The Nexus client-hub is the central web gateway that makes your sovereign "silos" feel like a single, unified experience.
Technically Managed By
- Unified Identity: Redirects automatically to the correct instance using Marcoby Identity.
- Identity Bridge: Mediates OAuth sessions between the Hub and private instances.
- Multi-instance routing: One login, many workspaces.
How Users Should Use and Manage It
- 1Access the client-hub via identity.marcoby.com.
- 2Log in to your Marcoby account to see all your active instances.
- 3Switch between environments seamlessly without re-authenticating.
How It Fits in Nexus
- The client-hub is the "Operating System" browser for your Nexus instances.
- It is the primary way users interact with the platform on a daily basis.
- It bridges the gap between web-based silos and a unified user experience.
What Matters
- Unified Gateway for all instances.
- Single Sign-On: Access all silos with one login.
- Cross-origin session relay via identity-connect-bridge.
Reference Notes
Next Step
Use the docs as the product contract.
As new apps and runtime behaviors ship, extend this documentation hub first so users and internal teams have one clear reference for how Nexus is supposed to work.