Skip to main content
Private preview

One governed agent for your team

A Raava-run agent behind a web chat and a private, key-protected API, on our Sydney server.

Internal to Raava for now.

Built on Hermes by Nous Research, open-source (MIT).

Works todayThe gateway checks a key and has no public address; the web chat has its own sign-in.

BuiltThe agent behind the chat; a live answer is not shown here.

A tour of Nexus

Illustration: the web chat signs in and reaches Nexus directly; a request from a Raava tool reaches the gateway, its key is checked, and an example answer returns with one log line. A live answer is not shown here.
  1. The web chat has its own sign-in

    Your team reaches Nexus through a web chat behind a sign-in.

    Works today
  2. A Raava tool calls the gateway

    Other Raava tools reach Nexus through a gateway API.

  3. The key is checked

    The gateway needs a key and has no public address.

  4. The answer returns, with one log line

    Nexus answers and the gateway logs one line. This reply is an example, not a live answer.

One agent, two ways in

Works today

An internal port, no public address

Its gateway API listens on an internal port and has no public ingress.

Works today

A web chat with its own sign-in

Your team asks in a web chat that sits behind a sign-in.

Works today

Read-only in production

Its diagnostic commands in production are read-only.

How it works

  1. Ask in the chat

    Works today

    Your team reaches one Raava-run agent through a web chat.

  2. Reached by other Raava tools

    Works today

    Other Raava tools call the same agent through a gateway API, using a key on an internal connection.

  3. On Raava's own server in Sydney

    Works today

    Nexus runs on Raava's Lightsail server in Sydney.

Who it is for

Raava's team

Asks Nexus questions through the web chat.

One agent, behind a sign-in.

Raava's own tools

Call Nexus through the gateway.

Every call needs a key.

Not your fit if you want a public chatbot on your website. Nexus sits behind a sign-in and a key.

Details

Runs on
Raava's server in Sydney
Access
A web chat sign-in; the gateway needs a key and has no public address
Built on
An open-source agent; the credit on this page names it
Private preview
  • Internal to Raava for now.
Ask how we use it

Questions

Internal to Raava for now.

No. It sits behind a sign-in and a key, with no public address.

Through a gateway API that checks a key.

Raava runs it, built on an open-source agent. The credit line on this page names it.

Nexus stays inside Raava. Start with a free audit.

Nexus is in private preview, in use inside Raava. The free audit is 45 minutes with Demi, then a written follow-up that usually names three to five opportunities.