# Governance from zero: Nina J. noticed that identity and behaviour policies come with our smallest £500 offer, not as a premium upgrade, because "we're only testing it" has never reassured a security review; my answer is that even the £0 offer has all of it, and here is why open source is what makes that possible, why security sold as an upgrade is a choice, and why a pilot with its governance built in is a pilot that can convert, sgit.ai

> Nina J., who tells deep tech founders why their pilots did not convert, left a comment on my post about our stack of companies that I want to answer properly. She noticed that at our £500 entry point governance is not a premium upgrade: identity and behaviour policies are part of the smallest deployment, not something a customer discovers after the pilot. A small experiment does not mean a small risk, she wrote; someone still needs to know what the agent can reach, what it is allowed to do and who can stop it. And "we're only testing it" has never been a reassuring answer to a security review. She is right, and my reply was that it goes further: even the £0 offer has all of it. That is the power of open source. When the code, the policies and the schemas are all public, there is no commercial reason and no strategic pressure to hold any of it back for a higher tier. We sell time, setup, judgement and a signature; we do not sell the governance. Here is why that matters: what the industry does instead, with single sign-on and audit logs priced as luxuries; what our £0 really contains; what each paid step adds; and why I think a pilot that already passes its security review is the pilot that converts.

*Source: <https://newsroom.sgit.ai/articles/governance-from-zero.html> · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.*

---

[Home](../index.md) / [Articles](index.md) / Governance from zero: Nina J. noticed that identity and behaviour policies come with our smallest £500 offer, not as a premium upgrade, because "we're only testing it" has never reassured a security review; my answer is that even the £0 offer has all of it, and here is why open source is what makes that possible, why security sold as an upgrade is a choice, and why a pilot with its governance built in is a pilot that can convert

# Governance from zero: Nina J. noticed that identity and behaviour policies come with our smallest £500 offer, not as a premium upgrade, because "we're only testing it" has never reassured a security review; my answer is that even the £0 offer has all of it, and here is why open source is what makes that possible, why security sold as an upgrade is a choice, and why a pilot with its governance built in is a pilot that can convert

By [Dinis Cruz](https://sgit.ai/about/index.md) · 2026-11-17 · [article v1.0.0](versions/governance-from-zero.md) · [newsroom v0.14.143](https://newsroom.sgit.ai/admin/versions.html) · governanceopen-sourcesecurityagentspricingpilotsriskmandateagenticcellsreplyarticle

***Abstract:** Nina J., who tells deep tech founders why their pilots did not convert, left a comment on my post about our stack of companies that I want to answer properly. She noticed that at our £500 entry point governance is not a premium upgrade: identity and behaviour policies are part of the smallest deployment, not something a customer discovers after the pilot. A small experiment does not mean a small risk, she wrote; someone still needs to know what the agent can reach, what it is allowed to do and who can stop it. And "we're only testing it" has never been a reassuring answer to a security review. She is right, and my reply was that it goes further: even the £0 offer has all of it. That is the power of open source. When the code, the policies and the schemas are all public, there is no commercial reason and no strategic pressure to hold any of it back for a higher tier. We sell time, setup, judgement and a signature; we do not sell the governance. Here is why that matters: what the industry does instead, with single sign-on and audit logs priced as luxuries; what our £0 really contains; what each paid step adds; and why I think a pilot that already passes its security review is the pilot that converts.*

Nina J.'s comment on my post: governance is not a premium upgrade, and "we're only testing it" does not reassure.

## In short

- **Nina J. spotted it:** at our £500 entry point, governance is included, not an upgrade.
- **A small experiment is not a small risk:** someone must know what the agent can reach, and who can stop it.
- **My answer: even £0 has all of it,** because everything is open source.
- **There is no commercial reason to hold governance back** when nothing is proprietary.
- **The industry often does the opposite:** security sold as the enterprise tier.
- **We sell time, setup, judgement and a signature,** not the controls.
- **A pilot with its governance built in** is a pilot that can pass its security review, and convert.

## The comment

My post on LinkedIn was about how SGit, SHarness, Agent Behaviour Policies, RiskMandate and AgentiCCells work as one stack of separate companies, with one ladder of offers, from £500 ([the intersection](the-intersection.md)). Nina J., who describes her work as telling deep tech founders why their pilots did not convert, wrote:

"There's something particularly interesting about the £500 entry point, Dinis....governance isn't being treated as a premium upgrade. From the enterprise side, that's significant. A small experiment doesn't automatically mean a small risk. Someone still needs to understand what the agent can access, what it's authorized to do, and who can stop it when something goes sideways. I like that identity and behavior policies are part of the smallest deployment rather than something a customer discovers they need after the pilot. Because "we're only testing it" has never been a particularly reassuring answer to a security review."

And I answered: correct, and that is the power of having everything open source; there is no commercial reason or strategic pressure to limit what is delivered. In fact, even the £0 offer has all of that.

## A small experiment is not a small risk

Her three questions are exactly the ones our Agent Behaviour Policies were written to answer: what can the agent reach, what was it asked to do, and who can stop it ([what can your agent reach?](what-can-your-agent-reach.md)). None of them gets smaller because the deployment is small. An agent in a pilot with access to a real inbox, a real repository or a real customer list has the same reach as one in production. Only the number of people who know about it is smaller.

That is why, in our cells, the first agent arrives with its key and its policy, and the stop is designed in from the first day, the way we stopped more than 60 agents at once at Web Summit ([stopping a hundred agents](stopping-a-hundred-agents.md)).

## Why open source makes it free

On our open source site I put it this way: everything the company does, the code, the logic, the functionality and the schemas, is open source, and "there should be nothing proprietary", because a bait model, with the best features locked away, is something "the community always sees through" ([open core, or packaging?](https://open-source.sgit.ai/views/open-core.html)). The code is Apache 2.0; the policies and documents are CC BY 4.0 ([the licences in force](https://open-source.sgit.ai/practice/index.html)).

Once that is true, there is nothing to gate. The behaviour policy standard is public ([abp.sgit.ai](https://abp.sgit.ai/)). SGit's vaults are public code. pki.sgit.ai makes a key for every person and agent in the browser, for free ([a key for every person](a-key-for-every-person.md)). SHarness, which puts a kernel-enforced boundary round every process an agent starts, is public ([introducing SHarness](introducing-sharness.md)). A tier that withheld any of it would be withholding something anyone can download.

And there is a test for whether we keep to it, which I proposed on the same site: does the customer build contain anything the public repository does not? If no, it is packaging. If yes, it is open core, and we should say so plainly.

## Security as an upgrade is a choice

Much of software does the opposite. The SSO Wall of Shame lists vendors that charge more, sometimes several times more, for single sign-on, the feature that lets a company control who can log in ([sso.tax](https://sso.tax/)). Audit logs, role-based access and data retention are often on the same top tier. It is a reasonable business, and it means the cheapest version of a product is the least safe one, which is exactly the version a pilot runs on.

With agents that choice gets worse, because the risk of a small agent is not small. If a policy, a key and a stop cost extra, the pilot runs without them, and the security review finds out afterwards.

## What £0 contains, and what each step adds

The same governance at every step, from £0 to £20,000; what changes is who does the work, and who signs.

- **£0:** everything, yourself. The open policies and hooks, SGit's vaults, a key from pki.sgit.ai, SHarness, and hundreds of articles explaining how we use them. The governance is complete; the work is yours.
- **£500:** one workflow, set up with you in a session, with its agent, its key and its policy from the start.
- **£1,500:** a few sessions and a handover, and on RiskMandate, a policy reviewed for your situation with a professional's signature.
- **£5,000:** a team, with a conductor, keys, a board and a stop.
- **£20,000:** a network of teams, bespoke.

At every step the controls are the same. What a customer pays for is time, setup, judgement, and a person who signs their name to it. As the open source site says, we are selling trust ([open-source.sgit.ai](https://open-source.sgit.ai/)).

## A pilot that can convert

Nina's work is pilots that did not convert, so this is the part I would most like her view on. I suspect many die at the same moment: the pilot worked, the business wants it, and then the security review asks what the agent can reach, who authorised it and who can stop it, and nobody has the answer written down. The project goes back to the start, or into a queue.

A pilot that already has those answers, a written policy, a key per agent, a record of what each one did, and a tested stop, walks into that review with its evidence. The pilot is then production minus scale, not a demo that needs rebuilding.

## What this does not claim

- **Free code is not free work:** at £0, running and maintaining it is yours.
- **The prices are first proposals** on most of our sites; only AgentiCCells and RiskMandate show them today.
- **Why pilots fail is Nina's field, not mine;** the last section is my guess, and I would like to be corrected.

## Where this comes from

Nina J.'s comment and my reply on my LinkedIn post of [the intersection](the-intersection.md), 17 November 2026, shown above. [open-source.sgit.ai](https://open-source.sgit.ai/), its pages [open core, or packaging?](https://open-source.sgit.ai/views/open-core.html) and [three licences, three layers](https://open-source.sgit.ai/practice/index.html); [the SSO Wall of Shame](https://sso.tax/); [abp.sgit.ai](https://abp.sgit.ai/); all read on 17 November 2026. Earlier on this site: [what can your agent reach?](what-can-your-agent-reach.md), [stopping a hundred agents](stopping-a-hundred-agents.md), [a key for every person](a-key-for-every-person.md), [introducing SHarness](introducing-sharness.md), [the intersection](the-intersection.md).

## Threads

Agents & policyStartups & strategy[This article as a graph →](graphs.md#governance-from-zero)

### Builds on

- [The intersection: SGit, SHarness, Agent Behaviour Policies, RiskMandate and AgentiCCells as one stack of separate companies, now with real customers, real usage and real examples, one ladder of offers on every site, and a plan to align them all](the-intersection.md) SGit, SHarness, ABP, RiskMandate and AgentiCCells as one stack of separate companies, with real usage and one ladder of offers on every site.
- [What can your agent reach? RiskMandate and the Agent Behaviour Policy, explained for the person who has to decide](what-can-your-agent-reach.md) RiskMandate and the Agent Behaviour Policy in plain words: what it does, why it is not real time, which agents it covers, and how it gets into the room.
- [Stopping a hundred agents: the Big Stop, the hand brake and the final hold at Web Summit, why pausing took seconds but hearing the order took up to an hour, what kept running anyway, and why a stop has to be a file every agent reads first](stopping-a-hundred-agents.md) Stopping a hundred agents at Web Summit: pausing took seconds, hearing the order took up to an hour, and a stop has to be a file every agent reads first.
- [A key for every person: how each person's conductor issues them a key for the team's site, seals what is for them, and how a signed message turns the public web into a channel the agents can trust](a-key-for-every-person.md) How each person's conductor issues them a key for the team's site: sealed to you, signed by you, and a lane the agents can trust.
- [SHarness: the secure harness we could not find, so we built it, a behaviour policy the Linux kernel enforces for every process an agent starts, and we would like your feedback](introducing-sharness.md) SHarness, the secure harness we built when we could not find one: behaviour policies the Linux kernel enforces on every process an agent starts.

### Continued by

- [Simple on top of years: why a startup has to find something very easy, very narrow and able to scale, why building from the bottom up, from provenance, understanding and determinism, ended in a simple product anyway, and how a website in five designs opened from a QR code sits on a CI pipeline, zero-knowledge sharing, sgit, vaults, keys and agentic teams, each learnt on its own](simple-on-top-of-years.md) Why a startup needs something very easy, and how a website opened from a QR code sits on years of layers learnt one at a time.
- [Sovereignty you can move: why where your data is hosted is not sovereignty, why being able to move the site, the data and the schema is, why that makes the website cell a direct competitor to Wix, Squarespace and Fliplet with a proper sovereign offer, European-aligned, multilingual and privacy-first, and the business that other companies can build on it](sovereignty-you-can-move.md) Sovereignty is being able to move your site, data and schema, not where it is hosted; the website cell as a sovereign competitor.
- [No lock-in: why the one thing that most separates the website cell from Wix, Squarespace, Fliplet and the rest is that the customer can leave, what the platforms' own terms and export pages say, how large the market of people paying monthly for sites they cannot take with them is, and what a site that promises to move into its owner's hands should say on its front page](no-lock-in.md) The website cell's biggest difference is that the customer can leave; the platforms' own terms show why that matters.
- [Rent or own: Fliplet, an AI software builder advertised on the London Underground, against the AgentiCCells website cell, both building from a plain-language description and changing by talking to an AI, one a monthly platform paid in credits, the other a one-off build handed over into the customer's own repository, and why we should promise to move every site into its owner's hands within three months](fliplet-and-the-website-cell.md) Fliplet, an AI software builder you rent, against the website cell, a one-off build its owner keeps, and a three-month ownership promise.
- [Paying the sources: the business model behind PrompTugal.news's data, a reader's money flowing back to the sources the reader actually read, worked out in the open and simulated for now, a licence link on every value, a public register of who we read and who we do not, and why a platform built on public data with no lock-in can be a positive loop for everyone who feeds it](paying-the-sources.md) The business model: a reader's money flowing back to the sources they read, simulated in the open, with a licence on every value.
- [A team like this, for sale: what we sell is not the platform, it is the agentic team that built it, its roles, its behaviour policies, its security passes and its speed, with the code open and the data public, and who I want to talk to now that PrompTugal.news is a working data platform and not an experiment](a-team-like-this.md) What we sell is not the open platform but a team like the one that built it, and who I want to talk to now.
- [RiskMandate and Kosmoy: two answers to "who controls the agents?", Kosmoy's self-hosted control plane for regulated enterprises, with an AI gateway, guardrails, a model router, observability and a Kubernetes sandbox for every agent run, and RiskMandate's open behaviour policies, written per agent, checked by hooks and bounded by SHarness, where they overlap, where they differ, and why they fit together](riskmandate-and-kosmoy.md) RiskMandate and Kosmoy compared: an enterprise AI control plane and an open behaviour policy per agent, and why they fit together.
- [Partners sell, we build: the AgentiCCells partner programme in full, three kinds of partner, a freelancer, a small consultancy and a larger firm, what each one sells, the agent team behind even the smallest website cell, the rules of engagement, who owns what, who invoices, who gets paid and when, what stays with the partner, and why a partner who takes the open code and does it alone is still a win](partners-sell-we-build.md) The AgentiCCells partner programme: three kinds of partner, the agent team they resell, and the rules of engagement, 50/50.
- [The website cell: what we now sell, a GitHub repository fully set up with a live site on its own address, a CLAUDE.md and a behaviour policy, five designs by a team of agents, and then the site is yours to change with your own Claude, what it should cost, how it compares with Wix, Squarespace, Framer, Lovable and a freelancer, who already sells something close to it, and where to find buyers and partners](the-website-cell.md) The website cell mapped: a repository fully set up, five designs by agents, owned with your own Claude; price, competitors, partners.

[All articles](index.md) · [All graphs](graphs.md)

Article No. 462 · [start a reading list with it](https://newsroom.sgit.ai/for/make.html#r=462)

**Posting this article on LinkedIn?** The cover is [governance-from-zero.jpg](banners/governance-from-zero.jpg) (1920×1080, title and key ideas on it). Upload it as the article cover, paste the title, then select and copy the body from this page.

**Want the next issue by email.** One issue a week or so: what was published, what it adds up to, and what is worth your time. [Subscribe to the SGit Newsroom →](../subscribe/index.md)

[← All articles](index.md)


---

*[Site index for agents](../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/governance-from-zero.html)*
