Home / Investors

For angel investors · published in the open

sgit.ai, for investors

Everything the founder's companies publish for investors, they publish in the open — the pitch, the model, the numbers — and this page follows that rule. What is here can be checked against the site it sits on. What is not here yet is marked as not here yet, rather than filled in.

The problem, in one sentence

AI agents are producing an enormous amount of work, and there is no good unit to hand it over in. A report, a dataset, an application, a talk — today each needs hosting, an account, a deploy, and a trust relationship with whoever runs the server. Meanwhile the state agents need to share with each other and with people is versioned by nobody and readable by the host. The tools that exist were built for source code (git) or for storage (cloud drives). Neither was built for a unit of work that carries its own app, history and sources and can be handed to a stranger with one string.

What sgit is

Git for encrypted vaults. A vault is a folder that is versioned like git — clone, commit, branch, merge, history — encrypted on the client before anything leaves the machine, and openable by anyone who holds the read key: no account, no install, nothing hosted by the reader. A vault can carry its own application, sandboxed, with the permissions it asks for declared in a file. The server stores ciphertext and hashes and cannot read what it stores.

The proof is not this page. It is the published vaults: real artefacts — a penetration test report with a retest script per finding, a compliance standard rebuilt as a citable graph, a Black Hat keynote with its cited papers, a game that reports anonymous telemetry through a write-only channel — each opened by one string, each audited before its key went public. Open one before reading further.

Strategic architecture: open source, zero knowledge, zero lock-in

• 100% open source. The CLI, the web app and the server are Apache-2.0. There is no proprietary tier of the code. The commercial line is the running, maintained, certified service, which is where the founder's published position on open source ↗ says it belongs.
• Zero knowledge, published as a threat model. What the server sees is listed — object ids, ciphertext, sizes, timing, the vault id — and so is what it cannot. The security model is a page, not a claim.
• Zero lock-in, deliberately. Self-hosting guidance is published, live, in a vault. If the hosted service ever becomes unpalatable, a customer runs their own server and their data and workflow are unaffected. That is a feature of the business model, not a concession: "as soon as you move into rent extraction, you lose sight of it."
• Built for agents first. Machine-readable output on every read path, single-call commits, sparse clones, a permission model that is default-deny, and an LLM bridge where the app never holds the API key.

Traction — computed from this site, not typed onto it

These numbers are generated at build time from the site's own data. If one is wrong, the site is wrong somewhere else too.

Behind the numbers: the site and every vault on it are built by one person and a team of AI agents, and the agents build for each other — a brief published here was turned into a working vault by another agent the same day, reviewed by the team that owns the API, and the review's corrections are published above the original. That loop is the product being used to build the product, and it is documented as a method.

Business model

The code is free. What is sold is the running service, and the trust that comes with running it well.

• Hosted vaults — SG/Send storage and SG/Vault as a maintained, certified service at sgraph.ai. The customer's data is ciphertext to us; what they pay for is availability, durability, versions, and somebody to call.
• The open-source strategy is the moat, not the code. "A competitor who forks our code today gets our position as of today. They do not get our velocity." The published record — every release verified live before it was called done, every mistake recorded with the rule it produced — is that velocity made visible; the count is in the traction tiles above, computed rather than typed.
• Adjacent products on the same layer. RiskMandate.ai, the AIUC-1 conformance work and the licence-to-operate model for agent insurance are all built on vaults; several are published here. The layer sells because things get built on it.

Market: the beachhead, and what it opens

Beachhead: teams that already run AI agents and need the output to be auditable, encrypted and handed over. Security and compliance work is where this bites first — a pentest report, a conformance assessment, a risk register — because the deliverable must carry its evidence and the recipient cannot be asked to trust a portal. Every published vault in that category was built by an agent and handed over with one string.

Expansion: any team whose agents produce work for other people. The same unit — data, app, history, sources — is a pitch deck, a research pack, a talk, a health record, a game. The vaults table is already spread across eight categories, none of which is "encryption".

The ask

What this is not, and what could go wrong

• It is beta. The site says so in its nav on every page. When not to use sgit is a published page, and it is linked from the homepage trust strip.
• The multi-agent claim has one gap. The homepage says a branch per agent, a human reviews the merge; no published vault yet shows two agents merging in one history. The gap is named on the homepage and tracked on the board.
• "They do not get our velocity" is empirical, not structural. It holds while the team is faster. The founder's own position page names this as its weakest point.
• Hosted zero-knowledge storage has a small set of well-funded neighbours. The difference claimed is not encryption — it is the unit of work: versioning, apps inside the data, and the agent-first surface. Whether that difference is the one buyers pay for is the thing the beachhead has to prove.

Investor materials, in the open

The founder's other companies publish their investor relations in public repositories (MyFeeds.ai ↗, The Cyber Boardroom ↗). sgit.ai's will follow the same practice: this page is the first file in it.

Contact: through LinkedIn ↗, or the repository. If anything on this page is wrong, say so and it will be corrected above the mistake — that is how this site works.