Partnerships, argued in the open

Each page in this section makes the case for one specific partnership, or puts out one specific call for collaboration, between organisations we would like to work with and the companies behind this site, sgit.ai and RiskMandate.ai. The pages are built entirely from public material, theirs and ours, so there is nothing on them that either side would need to keep confidential, and they can be sent to anyone who knows somebody there. That is what they are for.

How each page is written

Start with what they are trying to do	In their own words where possible, and where we can put it better, put it better. A partnership page that cannot explain the other side's mission generously has not understood it.
Public material only	Their published strategy, programmes and criteria. Our published vaults, measurements and articles. Nothing from a conversation, a data room or a private brief. If a fact would need permission to publish, it is not on the page.
Evidence, not pitch	Every claim about what we can do points at a vault that can be opened with a read key, a measurement with its command printed, or a page that states its own limits. The fifty-four published vaults are the portfolio.
The fit, stated precisely	Which of their stated priorities we serve, which we do not, and what a first concrete piece of work would be. A partnership is a specific thing two parties do, not an alignment of values.
What is not public, marked	The things a partner would need to know that are not on either site are listed rather than hidden, in the same way the investors page leaves the ask visibly open until it is stated.

The cases

Organisation	Why them	The case
Authentitas authentitas.com	Its briefing paper argues that every repair of accountability has been a named person and a record that can be proved, and that almost no money has gone into proving the person behind the work. We have built the record; they prove the person. The licence to operate, the story vault and the agent contact file each have one line that is a name and nothing more.	Named person, provable record: sgit.ai and RiskMandate.ai with Authentitas →
UK Sovereign AI sovereignai.gov.uk	Britain's £500 million sovereign venture fund for AI companies, with trust, safety and assurance as one of its five frontiers and an R&D procurement scheme whose challenge areas include the safe adoption of AI agents. Almost everything published here is an answer to a question they have asked in public.	A proposed partnership between sgit.ai, RiskMandate.ai and UK Sovereign AI →
Password managers and identity providers an open call	Every sgit vault opens with one key, people now hold dozens, and agents are starting to create them by the hundred. Storing, sharing and taking back secrets in the browser is what these teams already do well, and we would rather use their answer than build our own.	Who holds the keys? A call for collaboration on vault key management →
The cloud platforms AWS, Azure, Google Cloud, IBM, Europe, and more	sgit needs mostly storage and a little compute, so it runs on every cloud. Our story is AWS for historical reasons and because our credits are AWS credits; Azure and Google Cloud work but are not yet documented. One page per cloud, on deploying vaults there and the services that can be built on them.	sgit runs on every cloud →
The AI providers OpenAI, Anthropic, Mistral, Google Gemini, OpenRouter, ElevenLabs	This site is built with their models, and vaults are where agent work can be handed over, where documents can call models without leaking keys, and what a connector for encrypted data looks like. One page per provider.	Models do the work, vaults hold it →

If you know somebody at one of these organisations, the page is written to be forwarded as it is. It says what they do, what we do, where the two meet, and what a first step would look like, and everything on it can be checked by the person receiving it. Who is asking, and how to reach them →

← About the author UK Sovereign AI →