Moorhold Data
One governed workspace over the tools you already trust
Moorhold is an integration layer. It never forks, proxies or rebuilds a tool. It signs people in, wires the tools together through their own interfaces, keeps them in the state you declared, and records every change.
Identity
One account
People sign in through Keycloak, and every tool in the stack uses that sign-in. Once you've signed in to the portal, Superset opens without a sign-in page of its own.
- Groups are defined once and projected into each tool's own roles.
- Each tool keeps its native permissions. Moorhold does not invent a new permission model on top.
- A launchpad shows each tool, whether it is healthy, and opens it in its own interface.
Why not one permission model?
Every tool already has its own idea of who may do what. Replacing that would mean rebuilding the tools. Moorhold keeps the tools' own rules and shows you where they differ.
Provisioning
Declarative sources
Declare a data source once, as plain configuration. Moorhold creates what each tool needs, and removes it again when the source goes.
- Adding a source sets it up in each tool that uses it in one apply: a schema in Trino, a pipeline in Airflow and an ingestion source in DataHub, with its datasets in Superset once the first load has run.
- Before anything changes you see the plan, tool by tool.
- A reconciler compares what you declared with what each tool really has. It reports any difference it finds.
- Sources can be databases or awkward REST APIs with tokens, paging and rate limits, loaded with dlt.
# a web service source (fictional example)
apiVersion: moorhold/v1alpha1
kind: RestSource
metadata:
name: crm
spec:
baseUrl: https://api.example.test
auth:
style: header
name: X-Api-Key
secretRef: file:///etc/moorhold/secrets/CRM_API_KEY
extractor: crm_supplier.extract:source
resources:
- key: contacts
primaryKey: [id]
cursor: updated_at
writeMode: merge
rateBudget:
requests: 600
windowSeconds: 60
destination:
catalog: warehouse
schema: crm
schedule: "0 6 * * *"
AI agents
Agents propose, people approve
AI agents are users of the workspace, not a back door into it. An agent always acts for a named person, with that person's permissions and no more.
- Agents connect through the Model Context Protocol (MCP), to each tool's own server where one exists.
- Changes from agents are proposals. A person in the admin group approves them, and never the person who asked.
- Tools that write are off by default.
- Secrets are references only. A literal secret in a proposal is rejected.
- Moorhold does not ship a model or an assistant. You bring your own agent and your own model endpoint.
A proposal has a lifecycle
Awaiting approval then Approved then Applied.
A proposal can also be rejected or withdrawn. Once applied, it becomes part of what you've declared. Moorhold records it as declared, reports any difference it finds, and removes it when you delete it.
Metadata
Lineage and audit
Pipelines, tables and dashboards are connected in DataHub without anyone drawing the lines by hand. The tools report what they read and wrote, using the OpenLineage standard.
- Lineage comes from the tools themselves: the scheduler, the data models and the query engine.
- The audit log brings together the portal's own actions, sign-in and token events, and the query engine's record of what was read.
- Every agent action is attributed to the person it acted for.
- Retention is configurable.
| When | Who | What |
|---|---|---|
| 09:12 | claude-code for carol | Proposed add-source-grants |
| 09:40 | alice | Approved add-source-grants |
| 09:41 | Moorhold | Applied 4 changes across 4 tools |
| 11:05 | claude-code for bob | Read grants.public.awards through Trino |
No lock-in
Removable
You should be able to stop using Moorhold and keep everything it set up.
- Export all of the portal's state as plain, declarative configuration.
- Moorhold is designed so the stack keeps working if you remove it, because the tools are unmodified and configured through their own interfaces.
- Components are swappable. Each one meets a small set of contracts: sign-in, lineage, data, provisioning and agents.
Removable by design
Being removable is a design rule. Exporting everything as plain configuration is tested. Removing Moorhold from a running stack hasn't been tested.
Sovereignty
Runs on infrastructure you own
Everything runs on servers you control: a single virtual machine to start with.
- Secrets stay on your server. A source's password is a file under
/etc/moorhold/secretsthat only root can read. Moorhold keeps only the reference, andsudo moorhold applygives each password only to the service that uses it. - Values are kept in memory-backed files for the service that uses them, and never written to logs or errors.
- Each tool has its own service account. No shared credentials.
- The default stack is built from permissively licensed components. Each release is licence-checked.
Release 2026.11.4 runs on a single virtual machine with Docker Compose. Kubernetes isn't supported.
What leaves your network
Superset, Airflow, dbt and DataHub, four of the tools Moorhold runs, can send their own usage analytics. Moorhold switches each one's analytics off when it sets them up.
Moorhold checks for updates only if an admin turns that on, or presses Check for updates. Your server asks get.moorhold.dev for the latest version number. It sends no data, but our site will see your server's address. Turning checks off stops the daily check.
Releases that include the plan check also check the server's plan with account.moorhold.dev. The server sends its access key and the number of the release it runs, never your data, and we record the address it comes from. The privacy notice lists when it checks.
If you connect an AI agent, you choose where its model runs.
The default stack
What Moorhold runs
Moorhold is proprietary software. The tools below are open source and stay that way: you can use them without Moorhold.
| Tool | What it does | Licence |
|---|---|---|
| Keycloak | Sign-in (OpenID Connect) | Apache-2.0 (Keycloak licence) |
| Trino | Query engine | Apache-2.0 (Trino licence) |
| Apache Airflow | Scheduling and pipelines | Apache-2.0 (Apache Airflow licence) |
| Apache Superset | Dashboards and charts | Apache-2.0 (Apache Superset licence) |
| DataHub | Catalogue and lineage | Apache-2.0 (DataHub licence) |
| PostgreSQL | Database | PostgreSQL Licence (PostgreSQL licence) |
| dlt | Loading data from APIs and databases | Apache-2.0 (dlt licence) |
| dbt Core | Data models (SQL transformations) | Apache-2.0 (dbt Core licence) |
Licences checked by Allotment Technology, 28 September to 3 October 2026. Licences can change; each release is checked again before it is supported.
Status, October 2026
What is built, and what is not
Moorhold is in early access. The current self-install release, 2026.11.4, is published and signed. On a Mac, download the app. On a server, install it with an access key. Access keys are open at account.moorhold.dev. Each new organisation is approved automatically, or by a person at Moorhold if it's held for review.
Not every feature on this page is finished. We've built and tested them against copies of the stack on our own test servers, and none has run in a customer's environment. If you'd like to help test Moorhold, get in touch.
Talk to us
Free for solo use. If your organisation runs its own data stack, or wants to, tell us what you need.