Access & deployment

Try it on your work.
Scope the rest with us.

Install locally with a 15-day evaluation and no card. Create an account for ongoing individual access. For a team or private environment, send the requirements first and receive a deployment path built around the way you work.

Use first. Decide with evidence.

Install the runtime, open the local dashboard, and verify memory, routing, and proof on your own repository before discussing a rollout.

Choose a path
01 / VERIFY
Try locally
15-day evaluation · no card

For seeing Nexus Prime work on a real repository before you create an account or speak with us.

  • Install from the public npm package
  • Run memory and routing locally
  • Inspect the dashboard at localhost
  • Keep source and memory on your machine
Install locally
# Node 20+ · macOS, Linux, Windows npm install -g nexus-prime
For daily use
02 / CONTINUE
Create an account
Individual workflow

For one developer who wants persistent local memory, leaner context, and activation steps attached to an account.

  • Account-linked local license
  • Persistent memory across sessions
  • Context routing before model spend
  • Reviewable changes and proof trail
Create account
# Activate the key shown after signup nexus-prime license activate <key>
03 / SCOPE
Plan a rollout
Team · VPC · on-prem

For engineering organizations that need shared policy, private deployment, integrations, or a supported rollout.

  • Architecture and environment review
  • Governance and audit requirements
  • Model-gateway and tool integrations
  • Rollout, support, and success scope
Email requirements
A useful first email

Tell us enough to
give a useful answer.

We will reply with product fit, a recommended deployment shape, and a scoped commercial proposal. If Nexus Prime is not a fit, we will say so.

Open requirements email No generic demo form.
Write directly to the product team.
  1. 01
    Team and workflow.
    How many developers, which coding agents, and how work moves between them.
  2. 02
    Environment.
    Developer laptops, VPC, on-prem, operating systems, and model gateway.
  3. 03
    Trust requirements.
    Security, data residency, audit, approvals, and compliance expectations.
  4. 04
    Rollout shape.
    Integrations, support level, success criteria, and desired timing.
FAQ

Frequently asked
questions.

Why is there no fixed team price on this page?

A useful quote depends on users, deployment environment, governance, integrations, and support. We would rather scope the actual rollout than publish a flat number that is wrong for most teams.

What can I do before contacting anyone?

Install the package and use the 15-day local evaluation. No card is required. Run nexus-prime start to inspect memory, routing, and runtime proof in your own environment.

What happens after I create an account?

Your account shows a local license key and activation steps. Individual access starts there. Team and private deployment requirements are scoped separately by email.

Does Nexus Prime proxy my model traffic?

No. Memory, routing, and the dashboard run locally. You keep using the Anthropic, OpenAI, local, or private model gateway you already approved.

Can Nexus Prime run in a private environment?

The product is local-first by default. VPC, on-prem, data-residency, and supported rollout needs belong in the requirements email so the deployment can be reviewed properly.

What should I put in the email?

Team size, coding agents and editors, local or private environment, security requirements, integrations, support needs, and rollout timing. Email adarsh@nexus-prime.cfd.