US Open-Source Software on European Terms

A Gift Worth Recognising

Somewhere inside Target Corporation, one of the largest US retailers, a team of engineers built an on-call platform. They designed escalation policies, rotation schedules, alert routing. They solved the hard problems: who gets woken up at 3 AM, in what order, with what fallbacks. Then they released it all under the Apache 2.0 license.

This deserves a moment of appreciation. A company with no obligation to share its internal tooling chose to give it away, irrevocably. Apache 2.0 is not "open-source until we change our minds." It is a permanent, unconditional grant. Target cannot revoke it, restrict European usage, or change the terms for existing code. Every commit to GoAlert is a gift that cannot be taken back.

In an industry increasingly shaped by license rug-pulls, the bait-and-switch from open-source to "source available," and the quiet enclosure of community projects behind enterprise paywalls, releasing production-grade software under Apache 2.0 is an act of genuine generosity. This is what doing good looks like in software. European organisations building on GoAlert are not taking a risk. They are accepting a gift.

Running It On Our Terms

We run GoAlert on European infrastructure. The PostgreSQL database lives in our Kubernetes cluster. The GraphQL API serves from our network. User data, contact methods, escalation policies, rotation schedules never leave European jurisdiction. Target Corporation has no access to our instance, no telemetry connection, no control plane.

The entire on-call topology is defined as Kubernetes Custom Resources, stored in Git, on our GitLab instance, applied through Flux. A declarative operator reconciles the desired state to GoAlert's API. The system of record is ours. The runtime is ours. The operational knowledge encoded in escalation policies and rotation schedules, the genuinely valuable part, lives entirely under European control.

Self-hosted Apache 2.0 software is sovereignty in practice, not sovereignty in theory.

The Twilio Question

GoAlert sends notifications. For SMS and voice, it uses Twilio. This means a US company processes phone numbers and delivers messages through US-operated telecommunications infrastructure. Worth acknowledging.

Also worth putting in perspective.

An on-call system has two layers. The orchestration layer decides who to alert, when, through what escalation path. The delivery layer puts a message on a screen or makes a phone ring. The orchestration is the complex, valuable part. It encodes institutional knowledge about team structures, response priorities, and escalation logic built up over months. The delivery is a commodity.

Twilio handles the commodity. It knows a phone number received a message. It does not know which service is down, what the incident looks like, or how your infrastructure is shaped. The blast radius of Twilio's US jurisdiction is limited to delivery metadata.

Replacing Twilio with a European SMS gateway is straightforward engineering work. GoAlert supports multiple notification backends. The notification interface is a plugin point, not a load-bearing wall. Nobody has prioritised this yet because Twilio works reliably and the sovereignty exposure is narrow. That seems like a reasonable allocation of engineering attention.

What Actually Threatens Sovereignty

Contrast this with the mainstream alternative. PagerDuty, Opsgenie, and similar platforms run your entire on-call logic on US infrastructure. Your escalation policies, rotation schedules, alert history, incident timelines all live in a US data centre, operated by a US company, subject to the CLOUD Act. You cannot self-host. You cannot fork. You cannot migrate without rebuilding from scratch.

The difference is structural. With GoAlert self-hosted, the US dependency is a replaceable delivery channel at the edge. With SaaS on-call platforms, the US dependency is the entire system. One architecture gives you a clear upgrade path. The other gives you vendor lock-in dressed up as convenience.

European organisations should focus their sovereignty energy where the leverage is highest: owning the control plane, owning the data, owning the operational logic. A replaceable US delivery channel is a minor pragmatic concession compared to surrendering the whole stack to a SaaS provider that holds your data hostage.

Walking the Path

Accept Twilio for now. Not out of indifference, but because the architecture makes replacement easy when the time comes. The on-call logic runs in Europe. The data stays in Europe. The desired state lives in Git, versioned and auditable, on European infrastructure.

The foundation is sound. The path to full sovereignty is short and well-marked. And it was made possible by engineers at a US retailer who chose to share their work with the world, no strings attached.

That generosity is worth building on.