Where your file lives

PrivateWire fetches public pages. What stays with you is the file, the prompts, the drafts, the spike log and the decisions.

The reading goes out. The thinking stays in. Everything below is that sentence, drawn.

The boundary, drawn

The boundary: what leaves, what stays A box, labelled your perimeter. Inside the box, five things: the file, the spike log, the desk, the drafts, the models. One arrow leaves the box, drawn in red, labelled public pages, fetched. One arrow comes back in, labelled the pages themselves. Beside the first box stands a second box with a dashed border, labelled ATAILA Cloud: shared hardware, your separate index. It holds the same five things, and it shows where they sit when you take the Cloud edition instead of your own hardware. your perimeter the file the spike log the desk the drafts the models ATAILA Cloud:shared hardware,your separate index the file the spike log the desk the drafts the models public pages, fetched the pages themselves

The red arrow is the only one that leaves. We drew it ourselves.

What stays

Why this is worth keeping. Which stories you answer, and which you decline, is your positioning. None of it appears on your website.

The stories you declined
A map of what you decided not to fight about.
The drafts you killed
The argument you know you cannot win yet.
The file
What your leadership actually thinks, in one place.
The timing
What you were researching in the weeks before a launch, a raise or a lawsuit.

The archive is not on this list. It is a captured copy of somebody else's page, kept under its own rules. The record

What leaves

Fetches of public pages: the article, what it cites, what your competitors published. The same pages a browser would load. That is a real outbound flow, and we draw it rather than hide it.

Nothing else leaves. Not the file, not the prompts, not the drafts, not the spike log. In neither edition does a hosted AI provider hold any of them.

Two editions, and where the file sits in each

ATAILA Enterprise operated — Your hardware, in your building, yours alone: one tenant on one machine. The file, the spike log, the drafts and the models sit on a server you can walk to, and the file never leaves your building. ATAILA installs it and operates it there. The right answer if you already own the machine.

ATAILA Cloud operated — ATAILA's operated EU platform. The hardware is shared with other workloads; your file is a separate index on it. You give up "the machine is physically mine". You keep one contract, one accountable party, an EU jurisdiction, and a file that lives in one place you can point at. Editions

Check it yourself

No third-party resource is referenced in this page's served HTML. No font service, no tag manager, no widget. Open your developer console and read the source; a page that argues your file should not leave your perimeter cannot itself fetch a typeface from another continent.

See it working.

A personal walkthrough on our own newsroom, with the boundary above shown as network traffic rather than as a diagram.

Request a demo See our own newsroom