In short
- One status report is harmless; the whole record maps what a government will miss before it is public.
- Data residency is where the data sits; data sovereignty is whose law and control apply to it.
- Map every way the record leaves: files, backups, email, AI calls, integrations and support access.
The national programme office is choosing its platform. Twelve entities will report into it: ministries, authorities and two state companies. The evaluation has gone well on features. Then the chief information officer asks the panel to list what the record will hold once it is running.
The list takes a few minutes. Decisions taken by ministerial committees, some not yet announced. Contract values and the suppliers behind them. Forecasts of which commitments will slip, and by how long. The names of the officials accountable for each one. Risks that, if read by the wrong person, would be a headline.
Nobody had thought of the PMO software as sensitive. Read as a whole, it is the most complete account of the state's commitments that exists.
What goes wrong
Programme management software is often bought as a productivity tool. It is judged on screens and reports, and its data is classified, if at all, below the finance and personnel systems it draws from. Four mistakes follow.
The sensitivity accumulates, and nobody classifies the total. One project's status report is harmless. Ninety of them, with their budgets, their slips and the decisions behind them, show what a government will fail to deliver before it says so. Classification usually happens system by system, and the PMO record falls between the systems.
Residency is checked for the database only. The contract says the data is stored in the country, and the database is. The attachments may sit in another storage service, the backups in another region, the notification emails on a mail service abroad, the AI requests at a foreign endpoint, and the support team's access may come from anywhere. Each is a copy of part of the record.
Residency is confused with sovereignty. Data residency is where the data is physically stored. Data sovereignty is whose law applies to it and who controls it: who can be compelled to hand it over, who holds the keys, who runs the service and from where. Data can be resident in the country and still be under another jurisdiction's reach.
The exit is not planned. A programme record grows for years. If it can only be read by the vendor's software, the office cannot leave without losing its history, and the choice of supplier becomes permanent by default.
What good looks like
A sovereign PMO is one whose record stays under the state's law and control, wherever the software comes from. Five moves.
Classify the record like the systems it summarises
The PMO record draws on finance, contracts, people and cabinet decisions. Classify it at least as high as the most sensitive system it summarises, and classify the whole, not each field. Then the hosting, access and AI decisions follow from a classification rather than from a feature list.
Map every way the record leaves
Draw where one status update travels. Into the database, then into files and backups, into notification emails, into AI requests, into integrations with finance or document systems, and into the screens of anyone who supports the platform. Each path needs a stated destination inside the boundary or an approved one outside it, enforced by the system rather than by a policy. A path nobody drew is the one that leaks.
Choose where it runs from the classification
For most programmes, an approved cloud region in the country is enough. For some, the platform belongs in the organisation's own data centre. For the most sensitive, it runs air-gapped, with no connection to the internet at all. The software should run in each of these without a different product, and its AI should work in each one too, on a model you are permitted to use.
Keep identity, keys and storage in your hands
People should sign in through the organisation's own identity service, so access ends the day someone leaves, without waiting on the vendor. Files and backups should sit in storage the organisation controls. Support access should be granted for a stated purpose and recorded. These three controls decide sovereignty more than the location of the database does.
Plan the exit on the first day
Agree the formats the record can leave in, and test an export during the pilot: schedules in standard project formats, reports in documents anyone can open, and the audit trail intact. A record that can leave keeps the choice of supplier a real choice.
Lodestar runs wherever the client needs it: on any cloud and in any region, in the client's own data centre, or air-gapped. Air-gapped deployments sign people in through the client's own identity service, keep files in the client's own storage and run the AI on a model server inside the client's own network. Outbound connections for AI, documents and email can be limited to approved endpoints, and a call to any other is refused. The national programme view is described on the national programmes page.
Questions for your next review
- How is our programme record classified, and is it at least as high as the systems it draws on?
- Where do our attachments, backups, notification emails and AI requests actually go?
- Who outside our organisation can reach the record, under which country's law, and how is that access recorded?
- If we changed supplier next year, what would we take with us, and have we tested it?
A national programme's record is a register of the state's promises and the risks to them. It deserves the same sovereignty as the decisions it records.
Short answers
What is the difference between data sovereignty and data residency?
Data residency is where data is physically stored. Data sovereignty is whose law applies to it and who controls it: who runs the service, who holds the keys and who can be compelled to disclose it. Data can be resident in a country and still be within another jurisdiction's reach.
What is a sovereign PMO?
A sovereign PMO is a programme office whose record stays under the organisation's own law and control: hosted where its classification requires, with sign-in through its own identity service, files and backups in its own storage, AI on a permitted model, and a tested way to take the record out.
Can Lodestar be hosted on-premises or air-gapped?
Yes. Lodestar runs wherever the client needs it: on any cloud and in any region, in the client's own data centre, or air-gapped with no internet connection. Air-gapped deployments sign people in through the client's own identity service and run the AI on a model inside the client's network.
