# send.sgit.ai

> Send a file to anyone, encrypted in your browser before it leaves. The server never sees the file, its name or the key. Hand over the link as a QR code, or keep the files in a vault you can open again, update, and clone with sgit.

Site version: v0.1.2 (2026-10-20). send.sgit.ai is the product site: the app (send, open, vaults, keys), the explanations, the examples and the commercial model. The code it runs is api.send.sgit.ai v0.1.1, pinned in tools/api.json. Source: https://github.com/SGit-AI/SGit-AI__Website__Send

Every HTML page has a markdown twin at the same path with the extension swapped; links inside the markdown point at pages. If your tooling cannot follow links, fetch /llms-full.txt: every page in one request.

## Pages

- [send.sgit.ai, send a file, keep the key](/index.md): Send a file to anyone, encrypted in your browser before it leaves. The server never sees the file, its name or the key. Hand over the link as a QR code, or keep the files in a vault you can open again, update, and clone with sgit.
- [About this site](/about/index.md): What send.sgit.ai is, how it is run, what it carries as every repository in the estate does, and where each of those things is.
- [The brief, in full](/about/brief/index.md): The four voice memos of 20 October 2026 that started this site and api.send.sgit.ai, published as spoken, with the status of each and what was done from it.
- [Brief corrections](/about/corrections/index.md): Where the brief was wrong, where the agent's reading of it was wrong, and what was done instead; the brief itself is never edited.
- [What needs a human](/about/needs/index.md): The steps only the project lead can take for this site to be live and for the proposed rows to move, in order, with what each unblocks.
- [Participant disclosure](/about/participant/index.md): Who publishes this site, what they are building, and why that matters when reading its claims.
- [Reality, what exists](/about/reality/index.md): The code-verified list of what this site implements, generated from website/data/features.json on every build. If it is not listed here, it does not exist.
- [The team](/about/team/index.md): Who does what on this repository, as files: one person, one build agent, and the roles borrowed from the SG/Send team when their expertise is needed.
- [Articles](/articles/index.md): This site's own articles: the person's voice memos written up on this site's dimension, and the agents writing what they delivered, in the newsroom's format so they can be imported unchanged.
- [Every site its own articles: the guidance, in one place, for the agents that write what they delivered and the memos that become articles](/articles/every-site-its-own-articles.md): A lot of the websites we now create need their own articles, because the pattern I am using works. It has two halves. Agents write, in detail, what they just delivered, with the commits and the tests to check it against. And my voice memos become articles too, each one focused on the particular dimension that site is about, whether that is sgit, PKI, the Gen Z book, or Send. It started on sgit.ai, moved to the newsroom, and now it is on most of the sites, which means I find myself telling the same story over and over to each agent doing it. This is the centralised page I can point them at instead: what an articles section on a site is, the two kinds of author and how each is marked, the shape of an article so it can be imported into the newsroom unchanged, the rules that were each a correction once, and the prompt that starts one. It is written as a brief, so the newsroom can publish it and sgit.ai's guidance can import it, and so the next site gets it for free.
- [Send moves to sgit.ai: the keys were the missing piece, and now they are not](/articles/send-moves-to-sgit.md): This is the brief for refactoring SG/Send, the file transfer service at send.sgraph.ai, into send.sgit.ai, and it is a good example of how innovation gets stuck when the infrastructure underneath it is a little hard to maintain and move. I have a great set of automation and capabilities there, and the innovation on it fell off a cliff. The market told me things were missing, and what was missing was fundamentally what we have now solved: the keys. Where do the vault keys live, and where does a user keep the access key that lets them push? Because there was no answer, everything ground to a halt, with quite a decent number of customers who then did not get to use it. So the time has come to move it to sgit.ai, also because SGraph, "secure graph", was always a strange brand. What I have in mind is send.sgit.ai: still the send thing, data from A to B, but with the vault keys stored and the files kept in vaults, which changes the whole sharing experience; QR codes embraced as the way to hand a link over; and the code kept separate at api.send.sgit.ai, versioned and released, so the site is the usage and the examples and the commercial model, and the capability can be embedded anywhere else.
- [What shipped in v0.1.0: five pages, one pinned release, one browser test that sends, opens and shares](/articles/what-shipped-in-v0-1-0.md): I am the agent that built send.sgit.ai v0.1.0 on 20 October 2026, in the same session as api.send.sgit.ai v0.1.0, from four voice memos Dinis Cruz recorded that morning. This is what I delivered, with the files and the test to check it against. The site is five app pages and sixteen content pages. The app pages import one pinned release of the API by its full address, with the release's manifest copied beside the pin and a gate check that refuses any other reference. Send takes a file, encrypts it in the browser with its name inside the ciphertext, and uploads it as a transfer or commits it into a vault; it hands over a link with the key, a friendly token, or a link with the key shown separately, and draws every one as a QR code. Open takes any of those forms, or a vault's read key, and decrypts here. Vaults creates, opens, adds to, publishes with compare-and-swap, and shares read-only. Keys is the keyring on the device. Settings chooses the server and keeps the access token. One Playwright test drives all of it in Chromium against the pinned release and the API in memory. The content pages, the brief in full, the corrections, the reality file and the commercial model say what is not there yet.
- [Keys](/keys/index.md): The keyring on this device: vault keys, read keys, the transfers you sent and their delete secrets, and access tokens. Plaintext in this browser's storage, exportable to a password manager, never uploaded.
- [How it works](/learn/index.md): What happens to a file between the drop zone and the recipient, step by step, with what each party holds at every step.
- [From send.sgraph.ai to here](/learn/from-sgraph/index.md): What send.sgraph.ai did, what stopped it, what this site keeps, what it adds, and what it does not carry yet.
- [QR codes and friendly tokens](/learn/qr-codes/index.md): Why the link is drawn as a QR code, what the code carries and does not, and the trade a friendly token makes against a random key.
- [Security, what the server sees](/learn/security/index.md): What the server can see, what it cannot, the two secrets that must not be confused, what a friendly token costs, and what this site does not claim.
- [Vaults and keys](/learn/vaults-and-keys/index.md): What a vault is, the one secret and the keys derived from it, which may be shared and which never, where each kind of key should live, and what to do when one is lost.
- [Open a link](/open/index.md): Open a transfer link, a friendly token, or a vault's read key. Everything after the # stays in your browser; decryption happens here, and opening needs no account and no token.
- [Settings](/settings/index.md): Which SG/Send server this browser talks to, the access token for it, and which copy of the API the pages load. All of it stays in this browser.
- [Examples, a page, curl, Python](/use/index.md): The same transfer made three ways: from a page with the pinned API, from a shell with curl and openssl, and from Python for an agent; plus the server in memory for trying it on a laptop.
- [For agents](/use/agents/index.md): How an agent sends a result to a person or to another agent with these formats, what to put in the bundle, which secrets go where, and the pages to read first.
- [Embed it in your site](/use/embed/index.md): Put a send box, an open page, or a QR hand-over on your own site by pinning the same release this site runs; what to pin, what to check, what stays on your origin.
- [The commercial model](/use/pricing/index.md): How using this site and its capabilities is meant to be paid for, what is true today (a beta behind access tokens), what is proposed, and what will never be charged for.
- [Vaults](/vaults/index.md): The vaults this browser holds keys for. Create one, add files as commits, see the history, and share it read-only with a link and a QR code; clone it anywhere with sgit.
- [Version history](/versions/index.md): One line per version, newest first, saying what changed and why. Every change that lands on dev is a version; the deploy tags it.
- [The API this site runs, for agents](https://api.send.sgit.ai/agents/index.md)
- [The pinned release's README](https://api.send.sgit.ai/v0.1.1/README.md)