What we believe, plainly stated.

Most of the software a serious organisation now depends on is rented from someone else, runs on someone else's servers in someone else's country, and stores its data in someone else's jurisdiction. That arrangement was a reasonable trade for a while. It is no longer.

Ether-X exists to build software that respects the people who run it — UK-engineered, UK-hosted on equipment we own, with documented export paths that work. That is the bias behind every product we ship.

Every Ether-X product honours the same three commitments. They aren't differentiators — they're the price of admission for our work to count as ours.

• See Everything. You can't reason about systems you can't observe. Our products surface state — of your information, your assets, your operations — and the connections between them.
• Own Your Data. UK-hosted by default, on equipment we own and operate. Documented exports. Your data stays in the UK, and leaves when you decide it leaves.
• Build Better. Software you can trust, audit and extend. APIs that reward inspection. Documentation written for the engineers who'll inherit the system, not the buyers who'll sign the cheque.

We ship in small, frequent increments. We write our own documentation as we build. We run our own infrastructure in the UK, with regional options where customers need them. We treat operability — the property of being something a real team can actually run — as a first-class design concern rather than a delivery afterthought.

That makes us slower in the short term and considerably more durable in the long term. We make that trade deliberately and we've never regretted it.

We sell software as a UK-hosted SaaS subscription, run from our own equipment in UK datacentres. Pricing is per-product and visible on each product's site. We don't charge per seat for the act of sharing knowledge, and we don't charge for export.

We are not funded by selling user data to anyone, anywhere, in any form. We have no advertising business. We don't share customer data outside our infrastructure without explicit consent. We mention this here because it shapes every other decision we make.

• We won't claim certifications we don't hold. ICO registration is a fact; certifications are not.
• We won't lock customer data into formats only our software can read. Documented schemas and working exports are part of every product.
• We won't share customer data outside our infrastructure without explicit consent.
• We won't add dark-pattern friction to downgrade or cancel paths.
• We won't name our competitors. Our work has to stand up on its own.
• We won't quantify our team to make it sound bigger or smaller than it is. The work is the artefact.

The shortest way to test these principles is to read what we've shipped. Each product has its own changelog, its own security page, and its own export documentation. The umbrella site you're on now exists to make those easy to find and to make our overall posture legible — not to summarise the products in a way that lets us hide behind the summary.

If anything we've written here doesn't match what we've built, we'd consider that a bug worth filing. Tell us about it at [email protected].