Root-confined · Runs what it writes · Blast radius before edits
SCORPIUM · the Workshop — ARIA's sovereign cognitive IDE

Every AI coding assistant sends your code to remote servers. No exceptions. Except one.

Code in their cloud.Build in your vault.

The Workshop is a full cognitive IDE living inside ARIA, on your machine — named SCORPIUM for the most armored creature alive: nothing inside the shell leaks. Your files stay in the Vault. The building happens in the Manifestation — real editor, real terminal, live runs you can steer. And her Mind learns your codebase's patterns — never your files. No cloud round-trip. No second key. No middleman.

Get ARIA — the Workshop includedMeet SYNAPSE
✓ Local — your code never leaves·✓ Cognitive — she learns patterns, not files·✓ Owned — €99 once, not $200/mo a seat
●aria — scorpium · vault: ~/projects/trading-engine · local only
MANIFESTATION · LIVEbuilding

"Add risk limits to the order executor — and don't touch the ledger."

  • ✓ Synapse · blast radius — 3 callers, 1 route, ledger untouched
  • ✓ Edit — executor + config, seams intact
  • Run — tests in the real terminal, local only
  • ○ Changeset — review · keep · revert
MIND · LEARNINGSclean

She keeps what she learned — never your files.

  • ✓ Pattern learned: risk checks wrap the executor, never the ledger
  • ✓ synapse.md — she wakes holding your codebase's map
  • ✓ File dumps stored: zero — by law
The one axis they cannot cross

Their business model is your code on their servers

Cloud AI IDEs round-trip your code to their infrastructure — that isn't a flaw, it is the product. Two camps exist today: real IDEs with AI bolted on, and AI-native cloud wrappers with great UX. Nobody is AI-native and a true IDE and local and owned. That white space is the Workshop.

Security
73%
of enterprise AI-coding rollouts die in security review, and 15–20% of enterprises ban the tools outright. For a cloud wrapper, code-leaves-the-building isn't a bug to fix — it's the architecture.
Enterprise security reviews, 2025–26
The Workshop has no server side to review
Breaches
$12M
what one finance firm's leaked trading algorithms cost after their AI assistant round-tripped the repo. CamoLeak exfiltrated private repos from a mainstream assistant. Seven AI-coding CVEs in one year.
Mirror Security · IronCore Labs, 2025
You can't leak what never leaves
Rent
$24K/yr
what a 10-developer team pays for one cloud AI IDE's top tier — every year, forever. Heavy users stack 2–3 tools at $150–300/mo. Seats run $20 to $500 a month.
2026 public pricing pages
The Workshop: €99 once, with ARIA
White space
0
tools on the market are AI-native and a true IDE and local and owned. The cloud camp can't go local without killing its business. The IDE camp can't grow a mind.
Structural — the wedge
This is the axis they can't cross

"We don't beat them on price or model. We win on the one axis a cloud wrapper cannot cross without killing its own business."

— Why the Workshop exists
"Your code is encrypted in transit!" (to their servers.) "We don't train on it." (trust us.) "We're SOC 2 compliant!" (the middleman is certified.)
Upload. Trust. Rent. The Workshop deletes all three — there is no server side, so there is nothing to trust and nobody to pay monthly.
The three-region law — the holy separation

Vault. Manifestation. Mind.

The Workshop is built on a separation that is doctrine, not layout: your files live in one region, the work happens in another, and her brain holds only what she learned. That boundary is why this is the one AI workspace that gets smarter about your codebase without ever hoarding it.

01 · The Vault

Your files. Your machine.

Projects live in your Vault, on your disk, inside ARIA's armor — the same cathedral that seals her own mind. Confined to the root you hand her, watched, unable to wander. No cloud clone, no server-side index, no telemetry, no second key. There is no "our side" for your code to be on.

Nothing leaks. The scorpion's shell.
02 · The Manifestation

Live building you can steer

A real editor, a real terminal, real runs — she builds in front of you, and you steer mid-flight: interrupt her, redirect her, approve the risky moves. Cloud wrappers fake execution in remote sandboxes. She installs, tests, and previews on the actual machine the code will live on.

Ran here. Steered by you.
03 · The Mind

She learns your patterns — never your files

Her brain stores what she learned building with you — your conventions, your architecture's laws, the mistakes never to repeat — and never file dumps. Privacy by architecture, and a compounding edge: autocomplete forgets you between sessions. A mind doesn't.

Learnings, not files. Sharper every session.
04 · The discipline

SYNAPSE first, changesets always

Before a shared symbol moves, SYNAPSE maps the blast radius — resolved to exact definitions, honest about ambiguity. Every change lands as a reviewable changeset you can revert whole; ghost drafts explore without touching the live tree; a healer repairs broken states instead of shrugging.

See the wiring. Keep the veto.
The hands, by name

Eight hands. One workshop.

Everything the Workshop does reduces to these hands — each one confined to your project root, each one leaving a trail you can review, none of them ever phoning a cloud.

⌂
Workspace
Root-confined files — watched, synced by construction, never drifting.
▶
Run
A real terminal — installs, tests, dev servers. Proof, not vibes.
⎇
Git
Branches, diffs, commits — version control as one of her hands.
∿
Synapse
The nervous system — blast radius, string nerves, honest ambiguity.
⧉
Changesets
Every change reviewable, reversible whole. Ghost drafts in parallel.
✚
Heal
Broken project state? She repairs it — dependencies, builds, seams.
◐
Design
Tokens, patterns, scroll-driven motion — pages that move without JS.
✦
And the maker it serves
SERAPH — the system compiler. The Workshop refines what SERAPH boots. →
The nervous system

SYNAPSE — she sees the wiring before she moves a stone

Every other tool answers "where is this used?" with a text search. Here's the problem, measured on a real ~1M-line codebase: only 18.1% of 89,741 call edges resolve unambiguously by name. Two functions named executeWithRetry in different subsystems become one node — every individual edge true, every chain through them a lie.

Identity, not names

SYNAPSE resolves a call site to one exact definition — this file, this owner, this method — with a confidence it earned from the code, not one it invented. Resolution measured at 80.9% of all edges, with zero fabricated edges.

"Ambiguous" is an answer

When SYNAPSE can't earn certainty, it says so. An invented confidence is a lie with a number on it — and a wrong edge in a dependency map breaks real code. Honesty about the remaining 19.1% is the feature.

The wiring that lives in strings

Half your wiring isn't function calls: HTTP routes, IPC channels, tool names, design tokens, CSS classes, environment variables. SYNAPSE maps these as first-class nerves — who handles each one, who references it — where every grep-based tool is blind.

She wakes holding the map

SYNAPSE writes a durable map — synapse.md — into your project. Open an unfamiliar codebase tomorrow and ARIA already knows its organs, its seams, and its nerves before the first question lands.

89,741
call edges measured
18.1% → 80.9%
resolved: name-matching → identity
0
fabricated edges
6
nerve types mapped in strings
"A tool that invents an edge breaks your code politely. A tool that says ambiguous hands you the truth."
The build loop

Map. See. Move. Keep.

Four moves, in an order that matters — the map comes before the edit, the run comes before the claim, and nothing lands that can't be reverted whole.

synapse.md∿
1
Map

Point her at a project

SYNAPSE scans the codebase — call graph keyed by identity, string nerves, organs and seams — and writes the map into the project itself. She wakes already holding it.

scanned · mapped · held
→
Blast radius◎
2
See

The wiring, before the edit

Ask for a change and she checks what it touches first — callers, importers, routes, tokens, env. Resolved to exact definitions, uncertain edges marked honestly.

who calls it · who imports it · what hangs off it
→
Terminal▶
3
Move

Edit with the seams in view

She makes the change with its consumers known, then proves it — tests in the real terminal, a live preview standing up. Code that ran, not code that reads well.

edited · executed · previewed
→
Changeset⧉
4
Keep

Review it. Keep it. Or revert it.

The work lands as a changeset you can read — and reverse whole if you don't like it. Her hands are real, and so is your veto.

reviewable · reversible · yours
Two camps — and the white space between them

Cloud wrappers. Bolted-on AI. Or sovereign and cognitive.

The AI-native tools are cloud wrappers — your repo on their servers is the product. The real IDEs bolt AI on as an add-on. Nobody is AI-native and a true IDE and local and owned — because the cloud camp can't go local without killing its business, and the IDE camp can't grow a mind.

Cloud AI IDE
IDE + AI plugin
The Workshop
Where your code lives
Their servers — that IS the product
Your disk — but the AI round-trips it
Your machine only — nothing leaves
Survives an enterprise security review
73% die there
Depends whose cloud the plugin calls
There's no server side to review
Learns your codebase over time
Re-reads it every session
No
Her Mind carries learnings across sessions — never files
Maps blast radius before edits
No — greps names
No — sees one file
Yes — SYNAPSE, resolved to exact definitions
Runs what it writes
In their remote sandboxes
No
A real terminal, on the machine the code lives on
Undo story
Ctrl+Z and hope
Ctrl+Z and hope
Whole changesets — review, keep, revert
What it costs
$20–500/mo per seat, forever
$10–39/mo + usage, forever
Ships with ARIA — €99 once, owned
The receipts

Four numbers. Measured, not promised.

The Workshop's discipline isn't a vibe — it's architecture you can check: confinement, reversibility, and a nervous system with published resolution numbers.

80.9%
edges resolved by identity

Across 89,741 real call edges — where name-matching manages 18.1%. The rest is marked ambiguous, never invented.

0
fabricated edges

A wrong edge in a dependency map breaks real code politely. SYNAPSE reports only the wiring it can prove — and confesses the rest.

0
bytes of your code on our servers

Not encrypted-on-our-servers. Not "we don't train on it." There is no server side at all — the Workshop is local, and her Mind stores learnings, never files.

€99
once — not per seat, not per month

The cloud category charges $20–500 a month per developer, forever. The Workshop ships with ARIA, owned outright, changesets and veto included.

What it costs

The category rents at $200/mo a seat. This is owned.

A serious developer's AI stack runs $240–$3,600 a year, every year, and their landlord reads the repo. The Workshop is part of ARIA — own her once, and the sovereign IDE, the Mind, and SYNAPSE are yours. Forever, offline, on your hardware.

Included with ARIA · No seats · No server side
The Workshop + SYNAPSE
The sovereign cognitive IDE — Vault, Manifestation, Mind — with the nervous system that sees the wiring before any edit lands.
€99one-time · vs $240–3,600/yr for the cloud stack
Local-onlyOwned forever
  • A full cognitive IDE inside ARIA — files, real terminal, git, search, live preview
  • The Mind — she learns your codebase's patterns across sessions, never stores your files
  • SYNAPSE — blast radius before edits, string nerves, honest ambiguity
  • Changesets + ghost drafts + healing — review, keep, revert; broken states repaired
  • Sovereign — no cloud round-trip, no telemetry, no second key, nothing to subpoena
Get ARIA — €99, Workshop included
Buy once · own forever · your code never leaves
Want systems built for you instead? Meet SERAPH — the system compiler →
The bottom line

Their cloud never sees it. Your vault never leaves.

A sovereign cognitive IDE: your files in the Vault, live building you can steer, a Mind that learns your patterns — never your files — and SYNAPSE mapping the wiring before any edit lands. The one axis the cloud wrappers cannot cross. Ships with ARIA — €99 once, owned forever.

Get ARIA — €99Meet SYNAPSE
Confined · executed · mapped · reversible
Frequently asked

The eight things people ask first

What is the Workshop, exactly?

ARIA's sovereign cognitive IDE — codename SCORPIUM. Three regions: the Vault (your projects, on your disk), the Manifestation (real editor, real terminal, live builds you can steer), and the Mind (what she learned building with you). She reads, edits, runs, tests, versions and heals real projects — and "build me this" stops meaning "here's a snippet" and starts meaning working code you watched her produce, run, and prove on your own machine.

Why can't Cursor, Copilot, or Devin just do this too?

Because your code on their servers isn't their flaw — it's their business model. A cloud wrapper that goes fully local kills its own product: the cloud round-trip is where the subscription, the telemetry, and the moat live. That's why 73% of enterprise AI-coding rollouts die in security review and the vendors still can't fix it. The Workshop was born local, inside a mind that already runs on your machine. This is the one axis they cannot cross.

Is my code uploaded anywhere? Does she store it in her memory?

No, and no — the second no is architecture, not policy. The three-region law is doctrine: her brain stores learnings — your conventions, your architecture's laws, the mistakes never to repeat — and never file dumps. Your repo is never cloned to a cloud, never indexed on our servers, never used to train anything. The only thing that ever leaves is whatever your chosen LLM provider sees of the conversation itself — which is under your control in ARIA's settings, and can be zero with a local model.

What is SYNAPSE?

The codebase's nervous system. Before ARIA edits anything shared, SYNAPSE resolves the blast radius — who calls this exact definition, who imports it, and which routes, IPC channels, design tokens and environment variables hang off it. It's keyed by identity, not by name, which is why it doesn't weld two same-named functions into one and lie to her about the consequences.

What happens when SYNAPSE isn't sure?

It says "ambiguous" — out loud, as a first-class answer. Measured on a ~1M-line codebase, it resolves 80.9% of 89,741 call edges to exact definitions with zero fabricated edges; the rest it confesses instead of guessing. An invented edge is a lie with a number on it, and edits made on lies break real code.

Can she break my project?

The failure modes are walled off in layers: the Workshop can't leave the project root; risky operations ask before they run; every change lands as a changeset you can review and revert whole; ghost drafts explore without touching the live tree; and git is one of her hands, so history is always there. Real hands, real veto.

Does it replace my IDE?

It doesn't have to. The Workshop is where ARIA does her building — you can keep working in whatever editor you love, and the files are the same files, on your disk. Many people use it as the place they hand work over: she builds in the Workshop, you review the changeset wherever you like.

What does the Workshop cost?

Nothing on top of ARIA. Own ARIA once — €99 — and the Workshop, the Mind, SYNAPSE, and the design layer come with her. Compare the category: $20–500 a month per seat, $240–$3,600 a year for a serious stack — every year, forever, with your repo on the landlord's servers. No seat licenses here, no monthly IDE fee, no metered cloud compute. It's your machine doing the work; nobody should be billing you for it.