Private beta · macOS

Hire the model. Own the work. The AI workbench for sensitive files. The whole AI workbench on one machine.

Agenaxy is a local-first AI agent workbench: automate real work — documents, datasets, recurring workflows — while keeping your data safe on your machine. Hand confidential files to an agent inside a vault on your machine — local models, trusted connections only — and get the finished work back. Most agent platforms upload your work to the cloud — your files, your context, your history end up on someone else's servers. Agenaxy goes the other way: the model comes to your machine, and the work stays yours.

Request beta invite

Your files stay on your machine

Agenaxy works on your files right where they live — no copies on anyone's server. No one else can read them, not even us.

Your originals stay untouched

Every run works on a copy of your files. Whatever the agent does, the files you started with stay exactly as they were.

You control what the cloud sees

Pick a cloud model for a task and it gets that one task's context — never your history, never the rest of your machine.

Vault Mode

Lock your work to trusted connections only — a model on this machine, or one on your own servers.

NDA-Atlas.pdf

Find every clause that limits our right to publish benchmarks.

Prepared context, Read file, Reasoned +14 steps · 13s

Prepared context

Read file·NDA-Atlas.pdf

AIindexed by clause in your local workspace

3 s

Reasoned

6 s

Checked result

4 s

Three clauses limit publication of benchmark results: §4.2 bars disclosure of performance data; §7.1 requires prior written consent; §9 survives termination.

orders.csv

Build the weekly report, same format as last week — group complaints by issue.

Prepared context, Ran command, Reasoned +14 steps · 17s

Prepared context

Ran command·python -c <inline>

AIprofile and clean orders.csv, refunds.csv, reviews.csv

exit 0

3 s

Reasoned

6 s

Checked result

8 s

Weekly report generated — complaints grouped by issue, saved to weekly-report.html.

Ask the agent to work on these sealed files…Ask the agent anything…

AutonomyManualTrusted

Local model

Sealed · trusted connections only

Runs locally · stays on this device

One toggle, two modes — Standard for everyday work with any model · Vault when the work can't leave. Click the tabs to preview.

You probably need Agenaxy when the work matters more than the chat.

Five moments you might recognize.

01You've started a chat by deleting names and dates. Here, your data stays intact on your machine — you choose, task by task, what any cloud model sees.

02You're using AI for work, and you need a record you can explain.

03Your company has rules about what can go into AI tools — and you've signed them.

04You need to know what an agent did, not just what it said.

05Your context is worth more than the latest model.

How a run works

Three moves. Each leaves a durable record.

STEP 1

Delegate

Describe the files, rules, and outcome — the agent draws up a plan.

STEP 2

Run with control

The agent works on a copy of your files — your originals are never modified. You can steer or cancel any step.

STEP 3

Get the artifact + action record

Outputs land in your folder; a structured record of what happened — plans, tool calls, files touched — stays attached to the session.

Two directions

In the cloud, or on your machine.

Same convenience, opposite data flow. That's the whole difference.

The platform way

Every device is a door into a hosted workspace. Convenient — and the work settles there, not with you.

The Agenaxy way

The model is hired into your machine, task by task.

Inside Vault Mode

What Vault Mode blocks.

Turn on Vault Mode for sensitive work that must stay on machines you control. Unapproved network access is blocked at the operating-system level.

Tools that send data out are blocked.Web search, uploads, and remote connectors are disabled. Other tools cannot connect to destinations outside the allowlist.

Only approved models can connect.Use a model running on this machine or on a server you control. All other model connections are blocked.

Enforced by the operating system.Scripts and commands run in an OS sandbox that denies network access — an OS-level restriction, not merely an app setting.

Blocked connections fail visibly.If a step requires a connection outside the allowlist, it stops and tells you why.

Vault chats carry a mint Vault badge, and the composer shows Sealed · trusted connections only.

Read the full Vault Mode guide →

Real handoffs

The files you can't hand to a cloud tool.

Three people, one problem: the data that matters most is exactly the data you can't paste into a third-party AI. Here it stays home — and the work still gets done.

E-commerce ops

Monday, done by nine

Order exports are full of customer phone numbers and addresses — nothing you can paste into a chatbot. So the weekly report has always been a morning of copy-paste.

Drop the order, refund, and complaint exports into a chat: "Build the weekly report, same format as last week, group complaints by issue." Built with a local model — customer data never leaves this machine. One sentence, done.

orders.csvrefunds.csvreviews.csv→weekly-report.md

Local model · $0.00

Independent creator

Your archive, working for you

Your ideas and source material are your most valuable creative assets. They should stay private until they're ready. Once you put them into a cloud chatbot, they end up on an AI provider's servers — where they may even be used to train its models.

Point the agent at your materials folder: "Organize this into a topic library and draft three openings for the next video." Tagged library plus three openings — every file stays in your folder, ready to edit.

material/ (23 files)→topic-library.mdopenings×3

Stays on this machine

Lawyer

The NDA you can't upload

Client contracts can't go into a chatbot. A third party is a third party — and client confidentiality is the job.

In a Vault chat, drop in NDA-Atlas.pdf: "Find every clause that limits our right to publish benchmarks." A local model reads it in your workspace — 4 steps, 13 seconds. Three clauses found: §4.2, §7.1, §9.

NDA-Atlas.pdf→clause-summary.md

Vault · sealedLocal model

Every run leaves: a document you can edit · a table you can check · a record you can inspect.

Keep the receipts.

A record you can inspect

Every run keeps a structured action record — plans, tool calls, file reads and writes — attached to the session, so you can explain what happened.

Logged per run. Reviewable any time.

A vault you own

Your whole working site — files, memory, rules, chats, artifacts — lives on this machine at full fidelity, and never in an Agenaxy cloud account. Vault Mode locks your work to trusted connections only; pair it with a local model and nothing needs to leave at all.

Raw at rest on your disk. Sealed by the OS, not by a promise.

Models you choose

Pick the model per task — a leading cloud model, an open model, or one you run yourself. Open models now cost a fraction of the big-name rates (as of July 2026).

Per-task routing. Your workspace doesn't move when your model does.

Your AI workspace. Not theirs. Your files never had to leave. Runs here. Stays here.

We're opening a small private beta.

Tell us one workflow you'd hand off.

Request beta invite

Everything is optional. Leave your email if you want an invite.

Don't paste confidential content into this form — just describe the workflow.

Would this help your work?