Why BYOK, and why now?

Nexus is built for people who want the benefits of a multi-model assistant without being boxed into one provider or one pricing plan. But until now, many users have been limited by:

• Wanting to use an existing provider contract (personal or enterprise)

• Needing higher or more predictable rate limits

• Wanting to test new models as soon as their provider grants access

• Wanting clearer boundaries around billing and usage

• Preferring not to route usage through a shared pool

BYOK puts you in control. You keep your provider relationship, and Nexus becomes the place where you orchestrate prompts, tools, agents, and workflows.

What you’ll be able to do with BYOK in Nexus

Once BYOK is enabled for your workspace, you’ll be able to:

Use your own provider account

• Your usage is billed through your provider account (not pooled through a shared key).

• Your rate limits and access tiers apply.

Choose the models that match your needs

• Pick models per task: brainstorming, coding, long-context research, summarization, etc.

• Switch providers without changing how your team uses Nexus.

Keep cost and governance in your hands

• Ideal for teams with budget controls, departmental billing, or enterprise provider agreements.

Rotate and revoke keys on your schedule

• Update keys any time without downtime.

• Revoke instantly if needed.

Note: The exact list of supported providers at launch will be announced as we roll out BYOK. If you want, you can include a simple line like: “At launch we support: [Provider A], [Provider B], [Provider C].”

How it will work (high level)

BYOK is designed to be simple and safe:

1. Add a key in Nexus settings
   You’ll paste your provider key in a secure settings page.

2. Nexus verifies and stores it securely
   Keys are handled as sensitive secrets: masked in the UI, not displayed in full after entry, and designed for easy rotation.

3. Select how keys apply

   • Personal key (per-user) for individual usage

   • Workspace key (shared) for teams
     (Exact options depend on your workspace configuration.)

4. Use Nexus like you already do
   Chat, agents, automations, and workflows will run through the configured keys—with clear visibility into which provider/model is being used.

Security and privacy: what we’re building for

API keys are powerful credentials, so BYOK needs to be handled like production infrastructure. Our approach is guided by a few principles:

• Least privilege: only systems that must use a key can access it.

• Masked access: keys are not readable in full after saving.

• Rotation-first design: updating keys should be fast and low-risk.

• Clear ownership: you can remove or replace keys any time.

If you want to include specifics (like encryption-at-rest, secret managers, audit logs, etc.), add them only if they reflect your actual implementation. Otherwise, phrasing like “designed to” / “built to” keeps the post accurate.

Who BYOK is for

BYOK is especially useful if you’re:

• A developer who already pays for an AI provider and wants to use Nexus as the UX layer

• A startup experimenting across multiple providers without changing tools every week

• A team with an enterprise contract that needs usage to remain under existing procurement and governance

• Anyone who wants model flexibility without giving up cost control

Rollout plan

BYOK will roll out in phases:

• Early Access: a limited group of workspaces (helps us validate security, usability, and provider edge-cases)

• Public Beta: broader access with improved settings, key rotation UX, and more providers

• General Availability: BYOK becomes a standard Nexus capability

If you want a CTA here, keep it tight:

Want early access? Join the waitlist inside Nexus or reach out to the team at [contact method].

FAQ

Will Nexus still offer a “hosted key” option?
In many products, teams want both: a quick-start hosted option and BYOK for control. If that’s your plan, mention it. If not, omit.

Can I use multiple keys (different providers) in one workspace?
If supported, call it out—this is a major value add for multi-model workflows. If unsure, say: “We’re working toward supporting multiple provider keys per workspace.”

What happens if my key hits a rate limit or runs out of quota?
Nexus will surface provider errors clearly so you can take action (rotate key, upgrade tier, switch model/provider).

Can I remove my key?
Yes—BYOK should always be reversible.