EthosGov vs EthosOne

EthosGov and EthosOne are sister products.

Same technical foundation. Same team. Same design commitment to reducing friction for school leaders. Different markets, by design.

The question this article answers: why are there two products rather than one?

Because the governance models of independent and public schools are different, and the infrastructure that serves one is not the right fit for the other.

Two Markets, Two Governance Models

An independent school is a sovereign institution. It has its own Board. It has a Business Manager. It authors its own policies. It sets its own strategy. It procures its own software. It exists as a closed governance unit inside a regulatory envelope.

EthosOne was built for that world. The Board is the governance authority. The BM holds the rail. The Principal leads. The framework is organised around governance, risk and compliance in the traditional sense. The buyer is the school, because the school is the governing entity.

A public school is different. It sits inside a system of hundreds of schools, under a Chief Executive, through a chain of Education Directors, with policy written by the Department and compliance set by the Education Standards Board. Accountability is federated. Authority is bounded. The Business Manager role has been absorbed. The Principal carries the site's responsibilities inside a system's constraints.

EthosGov is built for that world. Four verbs the sector already uses: Lead, Improve, Assure, Oversee. The Governing Council has a narrower scope than a Board. The Education Director is a role that has no analogue in the independent system. The buyer is the Department or the Director, not the school.

Shared Architecture, Divergent Surfaces

The technical architecture and the data model are substantially shared between EthosOne and EthosGov.

This is deliberate. Governance data, risk registers, compliance calendars, incident records, action registers, policy endorsements, looks structurally similar in both markets. The underlying ontology is the same. A risk is a risk. An action is an action. An obligation is an obligation.

Where the products diverge is in the surfaces and workflows that sit on top of that shared foundation.

EthosOne's surfaces are oriented around the Board, the BM, and the Principal. Board papers. Governance dashboards. Compliance reporting suited to independent school regulatory context.

EthosGov's surfaces are oriented around the Principal, the Deputy, the Administrator, the Director, the Council, and the Department. The four-verb framework. Plain-language Council packs. Director portfolio views. Centre-out deployment models.

The same risk register logic presents differently to a Board Chair in EthosOne than it does to an Education Director in EthosGov. The underlying data is the same. The view is different because the audience is different.

Language Differences That Matter

The language divergence is not cosmetic. It reflects structural differences in the governance models.

EthosOne talks about "board-ready" reporting. EthosGov does not. Public schools do not have a board in the sense EthosOne means. They have a Governing Council with a narrower remit and a community-volunteer composition. The analogous concepts are "Council-ready" and "Director-ready," and they are different in shape, tone and scope.

EthosOne uses "GRC" as a framing. EthosGov does not. The public sector uses Lead, Improve, Assure, Oversee as the verbs that describe the work. Imposing GRC vocabulary on a public system asks the sector to learn a language it does not use.

EthosOne's dependency test is whether a school would be devastated to lose the product. EthosGov's is whether an Education Director would be devastated to lose the portfolio view. Dependency travels differently in the two systems.

These choices are not incidental. They reflect the product strategy of meeting each sector in its own language rather than asking both to adopt a generic GRC framework.

Buyer and Deployment Differences

In EthosOne, the buyer is the school. The Principal and the Business Manager close the deal. Procurement is typically a single-school decision. Contracts are per-school. Onboarding is school-by-school.

In EthosGov, the buyer pattern is different. The Principal opens the door. The Education Director validates fit. The Department or a pathway like Go2Gov signs the cheque. Contracts are at portfolio or system tier. Onboarding is centre-deployed, site-configured, centre-reported.

Per-site SaaS does not fit the public procurement model. Enterprise-scale licensing does. The pricing model has to mirror the governance model.

Framework and Features That Differ

Specific features exist in EthosGov that do not exist in EthosOne.

The Director portfolio view. No analogue in EthosOne. Independent schools do not have Education Directors.

The plain-language Council pack. Different design centre from the Board pack. Community volunteers read differently to a Board.

Centre-deployed compliance calendars. The Department maintains state-level calendars that configure across every site. Independent schools maintain their own.

Parent trust portal. Present in both products, but shaped differently. In the public system, the portal has to serve duty-of-care communication to a parent community that increasingly expects transparency without needing regulatory literacy.

Conversely, specific features exist in EthosOne that do not exist or are less prominent in EthosGov.

Board paper distribution and meeting scaffolding. Boards govern differently to Councils, and independent schools often have elaborate board meeting cadences.

Policy authorship tooling. In the independent world, policy is written inside the school. In the public system, it is written by the Department, and authorship tooling is less relevant.

Why Not Just One Product With Toggles

A reasonable question. Why maintain two products?

Two reasons.

First, the framing matters. An independent school Board Chair visiting a product page does not want to read about Education Directors and centre-out deployment. A Departmental sponsor visiting a product page does not want to read about Board governance. The framing has to be right for the audience, and the framing is difficult to make right in a single unified product.

Second, the roadmaps diverge. As each product matures, its roadmap is driven by the customers it serves. EthosOne's roadmap is shaped by independent school boards and business managers. EthosGov's roadmap is shaped by Departments, Directors and Principals. Trying to hold both in a single product would either fragment the roadmap or prioritise one sector over the other.

Maintaining two products preserves clarity on both fronts.

Shared Engineering, Shared Values

The two products share engineering resources, security posture, and design values. A feature built for one sector is often available to the other, configured differently.

When EthosOne builds a more sophisticated risk register module, EthosGov benefits from the underlying capability. When EthosGov builds the Director portfolio view, the architecture contributes to EthosOne's multi-campus scenarios.

The brand separation is real. The engineering is shared. This is the structure that lets both products mature without fragmenting the team behind them.

Capability Comparison

Capability	EthosOne	EthosGov
Framework language	Governance / Risk / Compliance	Lead / Improve / Assure / Oversee
Primary buyer	Principal + BM	Principal signals, Director validates, Department signs
Tagline	The governance infrastructure your responsibility deserves	Lead with less friction
Policy source	School-authored, supported by state frameworks	Department-authored
Governance authority	Board	Governing Council (narrower) + Education Director
Business Manager role	Central user	Largely absent, absorbed by Deputy
Deployment model	Per-school contract	Centre-deployed, site-configured, centre-reported
Scaling unit	One school at a time	Portfolio (20 to 30 schools) at a time
Dependency test	Would this school be devastated to lose it?	Would this Director be devastated to lose it?
Board pack	Present, primary artefact	Not primary; replaced by Council pack and Director view
Council pack	Secondary	Primary Lead surface
Director portfolio view	Not present	Primary Oversee surface
Parent trust portal	Yes	Yes, more prominent
Brand anchor colour	Navy #2F3C56	Forest #003B1B

The Line We Stand On

EthosOne gave independent schools the infrastructure their responsibility deserves. EthosGov gives public school leaders the infrastructure their system forgot to build.

That distinction is the rationale for two products. Two markets with genuinely different governance models deserve genuinely different infrastructure, not a single product trying to serve both with awkward compromises.

Take the Next Step

If this article speaks to your situation, two routes from here.

Go deeper on the verb. Read the Lead cornerstone. It is the deep page that sits underneath every article in this category.

See it on your site. Book a Governance Review. 45 minutes. No deck. We measure what the friction is costing you and whether EthosGov reduces it measurably.

---

Part of the EthosGov resources library. Governance infrastructure for public school systems. Lead. Improve. Assure. Oversee.