It remembers what you told it yesterday.

Nodus is the chief of staff you do not have. Private beta — we set it up with you.

Get a demo

Where this actually is

Shipped
A desktop application and a web platform.
Access
Private beta. We provision an environment with you rather than pointing you at a signup form.
Runtime
Local-first.

That is the whole status. We are not going to tell you what is coming, because a roadmap is not a thing you can hold us to.

The first twenty minutes

Four steps. Here are all four of them.

  1. Setup

    You answer a short set of questions about how you work. Nothing is connected yet.

  2. The founder path

    You pick the path built for someone running a company rather than building software. It changes what gets asked and what gets surfaced.

  3. The briefing

    The first thing it produces is a briefing on your day — not a blank prompt box.

  4. The first ask

    You ask it something. The next time you open it, it still knows the answer to the last thing.

What it does on a Tuesday

Written as things that happen to a person, not as feature names.

  • It hands you the day before you ask for it. You open it and the briefing is already there: what is on the calendar, what moved, what you said you would do.
  • It keeps the thread. You do not re-explain your company, your product, or last week's decision every time you start a session.
  • It names the one thing. Out of everything competing for the morning, it commits to a single most-important task and holds you to it.
  • It prepares you for the room. Before a meeting, it assembles who is in it, what was last said, and what is unresolved.
  • It carries the decision, not just the chat. What was decided and why survives the conversation it was decided in.

Why it's built this way

Nodus is built for the person who runs the day. The orchestration is the point: the assistant is the layer that holds a working week together across the sessions it is made of. Operator-first is a design constraint here, not a market segment.

For teams

Nodus is built for one operator. Team accounts are not available.

Need this built into your team's environment? That is a Gradient Install engagement. Gradient →

For enterprise

Nodus is local-first. Enterprise governance — single sign-on, audit logs, data-loss prevention, third-party certification — is not available.

Need this built into your team's environment? That is a Gradient Install engagement. Gradient →

Four fair questions

How do I get access?
Get a demo, or write to us. There is no signup page, because there is no self-serve environment to sign up to — a human provisions it with you. Get a demo Contact
Where does my data go?
Into an environment we set up with you. What is stored, what is not, and how to revoke access is written out in full on the privacy page. Privacy
What happens if I stop using it?
You take your data out and the environment is deleted. Nothing about the beta is a lock-in.
Is this the same Nodus as the payments company?
No. Nodus is a product of Dana. Not affiliated with Nodus Technologies (payment processing).

There is no signup page, and that is not a trick.

Access is provisioned by a person. The faster way into that conversation is a demo.

Get a demo

We read every request — three business days, either way.