Most of the Irish AI conversation right now is happening in Dublin boardrooms and on LinkedIn carousels. That's fine, but it's not where the work is. The work is in regulated firms — solicitors, accountants, clinics, schools, councils, small manufacturers — who need to use AI without handing client data to a US frontier lab and without waiting for a Brussels guidance note to tell them what's allowed. I run IMPT from Annerpark House in Clonmel. From here, the question isn't "will AI change Irish business" — it obviously will. The question is whether Irish firms run their own intelligence layer, on Irish soil, under Irish control, or rent it from someone else and accept the consequences. This is my position on that.
Sovereignty is a technical property, not a marketing claim
"Sovereign AI" gets used loosely. A vendor saying their model is "EU-hosted" because the inference endpoint sits in a Frankfurt data centre is not sovereignty in any meaningful sense. The model weights are still controlled by a non-EU entity. The training data lineage is opaque. The terms of service can change. The endpoint can be deprecated. The company can be acquired. The data you send for inference may or may not be retained for "service improvement" depending on which page of the contract you read. Sovereignty, technically, means three things. First, the weights live on hardware you control or your supplier controls under Irish law. Second, the inference path — prompt in, response out — never leaves that perimeter. Third, the audit trail of what was asked, what was answered, and what context was supplied is yours, written to storage you own, in a format you can read without the vendor's tooling.
If any of those three breaks, you don't have sovereignty. You have a hosting arrangement. The distinction matters because the EU AI Act, GDPR, the Solicitors Accounts Regulations, the Medical Council guidance, and the Department of Education's data protection rules all assume you can answer the question "where did this output come from and who saw the inputs". You cannot answer that with a hosted frontier model. You can answer it with a local one.
Why Clonmel, and why that matters
I get asked why I didn't set this up in Dublin or move to London. The honest answer is that the technical work doesn't require either. The Intelligence Brain is built on commodity GPU hardware, open-weights models, and a stack that runs the same in Tipperary as it would in Sandyford. What Clonmel gives me is distance from the noise. The Dublin AI scene is heavily oriented toward selling integration services on top of OpenAI and Anthropic APIs. That's a legitimate business, but it's the opposite of what I'm building. I'm building the thing you run when you can't or won't send data to those APIs.
There's also a practical point about the Irish regional economy. The firms I work with — accountants in Limerick, solicitors in Waterford, clinics in Cork, schools across Munster — are not going to be served well by a model that assumes everyone has a Grand Canal Dock budget. The pricing reality of regulated mid-market Irish firms is that they need a fixed-cost, on-premise solution they can depreciate, not a per-token bill that scales with usage. Building from Clonmel keeps that reality in front of me every week.
The regulatory stack Irish firms actually face
If you're a regulated Irish firm thinking about AI, here is the stack you're sitting under, roughly in order of how often it'll bite you:
- GDPR, enforced by the DPC. The hard parts are lawful basis for processing, data minimisation, and the rules around international transfers since Schrems II. Sending client data to a US-based LLM API is a transfer. You need a legal basis and you need to document it.
- The EU AI Act, phasing in. Most Irish small-business AI use will fall under "limited risk" or "minimal risk", but professional services applications that influence legal, medical, or financial outcomes can drift into higher categories. Documentation requirements scale accordingly.
- Sector regulators: the Law Society for solicitors, CCAB-I and Chartered Accountants Ireland for accountants, the Medical Council and HIQA for clinical settings, the Teaching Council and DPC again for schools. Each has guidance, and the guidance is converging on the same theme: you remain professionally responsible for the output, regardless of what tool produced it.
- Professional indemnity insurance, which is starting to ask pointed questions about AI usage at renewal.
None of that prohibits AI. All of it requires you to know what your AI is doing, on what data, under whose control, with what audit trail. A sovereign on-premise system answers those questions structurally. A SaaS API answers them with a contract clause and a hope.
What "audited" means in practice
Audit is the part most vendors skip. They'll show you a chat interface, demo a few prompts, and ask for a signature. Then six months later the partner asks "how do we know what advice this thing has given to clients" and there's a long silence. In the Intelligence Brain, every interaction writes to an append-only audit log: timestamp, user, prompt, retrieved context (with document references), model version, response, and any tool calls made. That log is queryable. If a client makes a complaint, or a regulator opens a file, or the firm wants to do an internal review, there is a record. The record sits on the firm's hardware. It is not deletable by the user who made the query. It survives the AI vendor going out of business, because the AI vendor is me, and even if I go under, the firm still has its hardware and its logs.
This is not exotic engineering. It's the same principle as a case management system or a practice management system: write everything down, keep it locally, make it searchable. The novelty is just that AI vendors haven't been doing it because the SaaS economic model rewards opacity. On-premise inverts that incentive.
What I will and won't claim about Irish AI
I'll claim that on-premise, open-weights AI on Irish soil is technically viable today for the use cases regulated mid-market Irish firms actually have. Document review, client correspondence drafting, internal knowledge search, compliance checking, summarisation of long technical material — these all run well on hardware that fits in a server room or a sturdy cupboard. I won't claim it matches GPT-5 or Claude Opus on every benchmark. It doesn't, and for the use cases above, it doesn't need to. The frontier labs are optimising for general intelligence on the open internet. Regulated Irish firms are optimising for accurate, traceable, cited answers on their own documents. That's a different problem and a smaller one.
I won't claim Ireland will have a sovereign foundation model in the next few years. We won't, and chasing that is the wrong target. The right target is sovereign deployment of the best open-weights models — Llama, Mistral, Qwen, whatever is current — under Irish operational control, with Irish audit trails, on Irish hardware, billed in euro at fixed cost. That's achievable now. That's what I do.
If you want the longer-form technical writeup of how this fits a founder's risk picture, I've put more on the founder view of the Intelligence Brain. The system itself, across all verticals, is documented at the Intelligence Brain overview.
Where to start this week
If you run a regulated Irish firm and you've been putting off the AI question, do three things this week. First, write down — actually write down — every place AI is already being used in your firm. That includes staff using ChatGPT on personal accounts to draft emails, because they are. Second, write down what data has been pasted into those systems in the last three months. You will be uncomfortable with the answer; that's the point. Third, decide whether your professional, regulatory, and insurance position is consistent with what you've just documented. If it's not, you have a problem to solve, and you can solve it with a SaaS contract you trust or with on-premise infrastructure you own. Either way, the decision is now yours to make consciously rather than by drift. That's the position from Clonmel.