AruiQ
Request access

Every note is a neuron. Make your digital brain think like you.

A digital brain that works the way you do: organized your way, working from your notes, your priorities and your dates, on your Mac.

Runs on your machine. No account, no AruiQ server, no telemetry. Nothing leaves your Mac unless you choose it: only if you share a folder of notes with your team, and then it goes to the place your team already uses, never to us.

Request access See how it works

The Mac app is in private beta. There is no public download yet; ask for access and Rod replies himself.

The AruiQ Orchestrator app on a Mac, open on the board. A greeting reads Good morning, Sam, with one thing due today, two running and one waiting. Below it, projects in columns: to do, active, parked and done, with an Acme Platform Team board under the personal one.
The app on a Mac, on an invented board. Recorded on Orchestrator 0.68.0

Every note is a neuron

Your brain is good at thinking and bad at storing. Get the thought out of your head, and let the rest of it build up somewhere you can see.

  • The Strata method is the skeleton: domains, areas and projects, as folders you could have made yourself.
  • Your notes, files and folders are the neurons. Every one you keep is one more.
  • The links between them are the synapses. You write them as you work, and under a note it offers the others that share its telling words, showing you which words, for you to connect or wave away.
  • Aru and your agents are what make it act. That is the difference from a second brain: that one remembers, this one also works.

It is a way of thinking about your notes, not a claim about your mind.

Under a note, five others it shares telling words with, each one naming the words they share, with Connect, Dismiss, and Don't suggest this pair again beside it.
The links it notices, with the reason shown. Connecting is yours. Recorded on Orchestrator 0.85.0

Meet

It starts by asking. You name your right hand, or keep Aru, and it introduces itself and asks one small question at a time: what you do, what you are working on, who you work with, what is due soon, how you like to work. Tap an answer, write your own, skip it, or stop and pick it up later.

What you are working on becomes projects, and what is due soon gives them dates. The rest becomes a note about you, which you read before anything is written. Aru reads it when it plans, on your Mac; your agents never see it. It leaves out what you say about health or money.

Capture

Get a thought out in two seconds. Select text anywhere on your Mac and press the key you chose, and it is kept, from mail, a browser, a document. Capture never fails in a way that loses what you had.

Connect

Everything you keep lands in one place. Each capture is offered a home, a task in one of your projects, and the notes it already relates to. Accept and it is filed with those links in place, as one change you can undo; dismiss and it stays where it is. Nothing moves on its own.

The matching is plain word work on your Mac: no model, no network, and an encrypted note is never read for it. A capture whose words match no project is offered nothing rather than a guess. It does best when your projects are named in the language you write in.

Act

Ask Aru what needs you today and it answers from your own notes, your priorities and your dates. Say what should change and you get a plan to read before anything moves. Your agents work in the projects the notes belong to.

Six captures waiting in Intake. Three are offered a task in a named project with the notes they relate to, and Accept or Dismiss beside each. One is offered a project without confidence. Two are offered nothing: a personal reminder, and one written in Spanish where the projects are named in English.
It offers a home and what each one relates to. Where it is not sure, it says so; where nothing matches, it offers nothing. Recorded on Orchestrator 0.85.0

What “like you” means here

  • It is organized the way you organize. Your domains and areas are yours; nothing imposes a system on you.
  • It works from your notes, your priorities and your dates, not from a model's idea of what matters.
  • It proposes and you decide. Filing, plans and next steps all arrive as suggestions you accept or dismiss.
  • It stays on your Mac. Your notes are files in your own folders, and nothing about them is sent anywhere.

Made for one person, or a few

Freelancers, one-person companies and small teams, without the overhead a big company would need.

  • Set it up in minutes and keep working the way you already do: your files stay where they are, in folders you can open without this or any other app.
  • It runs on your own Mac, so there is no server to pay for and nobody's platform to be locked into. The AI that plans your changes runs on your Mac too, at no cost; hand a bigger job to an agent and it is billed to the account you already have with it.
  • No account to create, no seats to manage, no administrator. If you are one person, that is the whole setup.

The engine

Four decisions, made once, in your files rather than inside an app.

The Strata method

Every knowledge base needs a base.

Domains, areas, projects and resources, with an archive for what is finished. Your notes are organised the same way as your work, folder for folder, so every project has one place for its notes and its handoff (a short note of where the work stands). Nothing is reorganised for you: the structure is yours and it stays readable.

Domain
The widest boundary: a company, a client, your personal life.
Area
An ongoing responsibility inside a domain. It has no end date.
Project
Work that finishes, with a notes folder of its own.
Resource
Reference material, not work in flight.
Archive
Finished work moves to the archive and keeps its name.

Your work

  • Acme
    • Platform
      • Billing migration
      • Status page
      • Runbooks
      • Archive

Your notes

  • Acme
    • Platform
      • Billing migration
        • Handoff note
The same shape on both sides: the billing migration's work on the left, its notes and handoff on the right.

  • Plain files you own

    No special format, no database, no lock-in.

    • Every note is an ordinary text file that any editor opens.
    • Keep your notes in version history and every change can be looked at and undone.
    • If AruiQ disappeared tomorrow, you would still have a folder of text files.

  • On your computer

    Your notes and your work stay with you.

    • It makes no calls to AI models of its own. Your agents keep working with their own services exactly as they already do.
    • It holds no API keys and needs no account.

  • Works with the agents you use

    No model vendor will build a board that treats its competitors as equals.

    Claude Code, OpenAI Codex CLI, GitHub Copilot CLI, Antigravity CLI and Grok Build each keep their sessions their own way. The engine reads the sessions those tools create; it does not take them over. An agent you do not have simply does not appear.

    • Claude Code
    • OpenAI Codex CLI
    • GitHub Copilot CLI
    • Antigravity CLI
    • Grok Build

    Gemini CLI and Aider are shown while they are running, and no further: the engine reads no saved sessions for those two.

Built on the engine

Early private preview for macOS

AruiQ Orchestrator

One board for your AI agent sessions and your notes.

Orchestrator finds the AI agent sessions already on your computer, groups them by the project they belong to, and gives you one place to resume them, park them with a written handoff, and search your notes.

Request access

There is no public download. Access is granted by hand.

Your work stays yours. The board only puts it in order.

It starts nothing by itself and sends your work nowhere. It reads what your agents already save on this Mac, lays it out as one card per project, and helps you finish a piece of work properly instead of closing the window on it.

  • One card per project

    Sessions are grouped by the folder they ran in, whichever agent ran them, in To do, Active, Parked and Done.

  • Park with a written handoff

    Park asks the agent to write a handoff, checks that it was saved, and only then closes what the board opened. Resume picks the work up from that note.

  • Sessions you started stay yours

    A session you started yourself is never closed by the board. Park saves the handoff and tells you the session is still running, and where.

  • Current truth, not a snapshot

    Every time you look, it checks what is actually running and what each agent has saved, so what you see is how things are right now.

  • Say what should change

    Ask in your own words and the assistant writes a plan: what it would create, change or send to the Recycle Bin. You read it, untick what you do not want, then run it. One click undoes the lot.

  • Your own hours

    A timesheet fills itself in from what you did: your prompts, your notes, your captures, your messages to the team, the cards you moved. An agent working on its own adds nothing. Per day and per project, and you can take it away as a file.

The details panel of a parked project, open over the board: its state, the agent that ran it, the folder it lives in, when it was last active, how much context it used, and the handoff note the agent wrote, above a Resume button.
Everything on the board comes from a folder. The panel names it, beside the handoff written before anything closed. Recorded on Orchestrator 0.85.0
A project card's due date opened: a menu offering Today, Tomorrow, Next week, a date to choose, and Remove due date. On the cards around it, each due date is a small tag coloured by how close it is, from quiet for a week away to filled for tomorrow.
Due dates set from the card, coloured by how near they are. Recorded on Orchestrator 0.85.0
The timesheet for one week: projects down the left, grouped by domain and area and marked where they belong to the team, the days of the week across the top, hours in the cells, and a total for each day and for the week.
A week counted from what you did, not from a stopwatch you remembered to start. Recorded on Orchestrator 0.85.0

Set up in minutes

A few plain questions, a plan you read, and a board that already has your work in it.

It asks where your notes live, how you divide your work, and what you are working on right now. Then it shows you the whole thing it would create, for you to change before anything is written.

The guided setup asking how you divide your life, with work, personal, home, family, health, finances, studies, a side business and community to choose from, a box to add your own, and two kinds of work to start from instead.
It asks in plain words, and every answer becomes a folder you could have made yourself. Recorded on Orchestrator 0.84.0
  • It starts from how you divide your life: work, personal, home, family, health, finances, studies, a side business, your community. Add your own if none of those fit. Each one becomes a domain.
  • Or start from a kind of work, if one matches: consultant or sales, or property. Then it asks what you are working on right now, in ordinary sentences, and turns those into projects.
  • Nothing is created until you say so, and everything it makes is a folder and a file you can open yourself.
The setup's preview: every domain and area it would create, counted at the top, with nothing written yet.
The whole thing it would create, before it creates any of it. Recorded on Orchestrator 0.84.0

CRM Labs

Your own place for clients and deals, beside whatever your company already uses.

A contact list and a light pipeline that live in the same folders as the rest of your work, in plain files on your Mac. It is not a replacement for the system your client makes you use; it is the one that is yours.

The CRM's contact list: name, phone, email and what each person is looking for, with a meter counting the days since you last spoke against the rhythm you set, green, amber or red, and a button on each row to mark that you spoke today.
Who you have not spoken to in a while, without keeping that in your head. Recorded on Orchestrator 0.85.0
  • The contact meter says who you have not spoken to in a while: green while it is fresh, yellow when it is slipping, red when you have let it go, and set aside when you have chosen to leave it for now.
  • Bring a spreadsheet in and see exactly what it would create before it creates it.
  • A deal moves through six stages by default, from lead to won or lost, because a pipeline you do not keep up to date is worse than none. Rename them or add your own; won and lost stay at the end.
  • A template for property work: developments, properties, clients, brokers and deals, each in its own folder.
A spreadsheet brought into the CRM: which column fills each field, then a count of what would be added, updated and skipped, and every row with its reason, before anything is written.
A spreadsheet in, every row explained first, nothing written until you agree. Recorded on Orchestrator 0.85.0

There are no integrations with chat, email or calling, by design. A phone number becomes a link WhatsApp opens, an address opens your mail app, and nothing is sent on your behalf.

Labs means it is being built in the open: it may change shape, and it is off unless you turn it on.

Turn on what you need

The board is always there. The rest is yours to switch on and off.

  • Board

    Your projects, your notes and your sessions. Always on.

  • CRM

    Clients, contacts and deals, in the same folders. Optional, and in Labs.

  • Timesheet

    Your own hours, counted from what you did. Optional.

Change your mind whenever you like: turning one off leaves everything it wrote exactly where it is.

Tell it what should change

Say what you want in your own words. You get a plan to read, not a change to discover.

Ask for a project to move to another area, to be shared with your team or made personal, to go up or down a level, to be archived or brought back, to take a due date, a priority or an owner. Ask it to rename a project, an area or a task, to start a session, to capture a line, or to make something new. It answers with a plan, and the plan is the point: nothing happens until you run it.

The command bar with a question typed into it, and underneath, the offer to hand it to your right hand and the notes that match.
Say it in the search box. Anything that reads like a request is offered to the assistant. Recorded on Orchestrator 0.85.0
  • Every line of the plan says what it would do: created, changed with the value now and after, or sent to the Recycle Bin. Untick the lines you do not want, or say what to change in words, and the plan follows.
  • It asks rather than guesses. Two things that fit your words, a place that holds several, a date you did not write, a delete you did not ask for: each comes back as a question.
  • Deleting goes to the Recycle Bin and asks twice, as does anything belonging to a teammate or any plan over ten changes. One click undoes a whole plan and puts every file back as it was.
  • It runs on Apple's on-device model: free, private, and it needs no network. Hand a bigger request to one of your agents instead and the cost is shown before anything is sent.
The assistant's plan for that request: a count of nothing created, seven things changed and nothing sent to the Recycle Bin, then each change as its own line with a tick box, the project's move written as the old place and the new one, and the notes whose links follow it. Below, a box to refine the plan in words, and the buttons to run it or cancel.
The plan, before anything happens. Untick a line, refine it in words, then run it. Recorded on Orchestrator 0.85.0
The Create dialog on its Describe it tab, with the request "Plan the December holidays: budget, flights, hotel" typed in, and below it the tree it proposes: one project with its tasks, each with the place it would go, ready to be edited before anything is written.
A sentence in, a plan out. Nothing is written until you press Create. Recorded on Orchestrator 0.85.0

It needs a Mac with Apple silicon, macOS 27 and Apple Intelligence turned on for the free on-device mode. It proposes and you approve; a plan runs when you press Run plan and not before.

Your team, one project

A team board beside your own, in a git repository your team already controls.

Connect a shared notes tree and a second board appears next to your personal one. The work stays where it is; what moves is the project's notes, its handoffs and its chat. There is no AruiQ server in the middle: your team exchanges through its own git repository and nothing else.

The team board on its own: three project cards, each showing who owns it, one of them unassigned with Ana working on it with Codex and when she last touched it, another due in three days, and a control above them for whose work to show.
The team's board, beside your own or on its own. Recorded on Orchestrator 0.85.0
  • A chat for each project, beside the work rather than in another app.
  • One calendar for both boards, so a team date and your own sit together.
  • Who is working on what, with which agent, and when they last touched it.
A team project's details panel with its chat open: messages from three people through the morning, about a failover drill and a rollback step, and a box to write to everyone on the project.
Each project's chat sits with the project, not in another app. Recorded on Orchestrator 0.85.0
The calendar for September, with a filter set to show both boards. Entries sit on several days, the team's marked with a dot, and today is outlined.
One calendar for both boards, filtered to either when you want it. Recorded on Orchestrator 0.85.0
What it does not do
  • It is not live co-editing. Several people writing the same note at the same moment is not what this is for.
  • Changes arrive about once a minute, not instantly, and only while you have sync turned on.
  • It needs a git repository your team already controls. AruiQ does not host one for you.

Nothing leaves unless you choose it: Privacy

A map of your work, not just your notes

The same folders, drawn as a graph, so you can see the shape of what you have.

Domains, areas and projects are the structure; each note sits by the project or area it belongs to, and a line is a link between two notes. It reads the same files the board does, so nothing new is stored and nothing is sent anywhere.

  • What is active, and what went quiet months ago.
  • What an agent touched, and which one.
  • What is broken or orphaned: notes with no links, links that point nowhere, areas with nothing active.
The Map page: the work drawn as a graph, with domains, areas and projects labelled around a circle and thin lines between the notes that link to each other. A filter bar above it offers activity, the personal and team boards, health and agents. Below, a count of the nodes and links shown.
Your work as a graph: the structure, the notes and the links between them. Recorded on Orchestrator 0.85.0
The same map with the health filter on. Beside the graph, a panel lists notes with no links in or out, and the broken links, with a count for each. In the graph, the affected notes are ringed.
Health lists what is orphaned or broken, beside the graph that shows where it sits. Recorded on Orchestrator 0.85.0

Aru, your right hand, thinking on your Mac

Ask what to do next and this Mac's own model answers, for nothing.

Apple's on-device model reads the board and proposes the next move for each card that needs one. It asks one small question per card, offering only the moves that card allows, and whatever it is unsure of comes back as a question for you. Every plan says who planned it and what it cost: zero on this Mac.

  • It costs nothing and asks nothing of the network, so it still works on a plane.
  • It proposes, you approve. Nothing runs until you say so.
  • It needs a Mac with Apple silicon, macOS 27 and Apple Intelligence turned on. Where it cannot run, the board says so in one sentence and offers an agent instead.

Aru is the one that notices: it reads the board and suggests what to do next. When you already know what you want changed, that is the assistant.

Your right hand open on the board with a plan from this Mac's own model: a line saying it was planned by Apple's on-device model at $0.00, when it was proposed, that nothing has run, and a list of proposals, each one to park or start a project with the reason for it, and Accept, Skip and Chat about this beside each.
A plan that cost nothing, waiting for you to accept or skip each step. Recorded on Orchestrator 0.85.0

Every agent, the same rules

  • Every agent gets the same card, the same Resume and Park, and the same handoff file.
  • Switch agent parks a session that is reaching its limit and opens another agent on the same project, starting from the handoff.
  • Down the side, each agent shows how much of its current limit it has used, so a limit is something you see coming rather than something you run into. An agent that does not report its usage says so, rather than showing you a guess.
The Agents section at the foot of the sidebar: Claude Code at 62 per cent of its limit with the time it resets, Codex at 38 per cent with its own, and Copilot reading unknown with an empty bar.
Two agents reporting, one that does not. The one that does not says so. Recorded on Orchestrator 0.85.0

It does not replace your notes app

Orchestrator does not replace Obsidian, or whatever you write your notes in, and it does not move your notes. Same files, same folders, same editor.

It reads and writes the same files, and has no format or database of its own. Running both at once is the normal case.

  • Your notes app

    Where you write: daily notes, documents, analysis.

  • The board

    Shows what your notes app cannot: which agent sessions exist, in which project, whether each one is running or parked, and how to pick one up again.

The note editor and search on the board are a convenience for when you are already there, not a replacement for your editor.

The Strata method comes inside Orchestrator, with nothing extra to install. Not using it? Orchestrator can also treat each of your existing project folders as a project.

Early private preview

Orchestrator is an early private preview, for macOS only. There is no public download. Access goes by hand, and the preview exists to find what still breaks.

To ask for it, send your name, your Mac, and what you would use it for. A person reads every request. Replies can take a while, and not every request gets access straight away.

Request access

If the button does not open your mail app, write to contact@aruiq.com.