We build
in the open.
The infrastructure behind our work ships as open source — readable, auditable, and free to run. When the code is public, trust isn't a claim. It's something you can check for yourself.
claude-pipelines
Multi-agent plugins for Claude Code — autonomous development, review, and research, orchestrated as slash commands.
Explore the projectorno
LLM agents under a runtime-enforced contract for CI. Declare the ceiling in YAML; the agent can't step outside the box.
Explore the projectAuditable
Every line is public. Read exactly what the agents can and cannot do — no black box.
Trustable
Open work earns trust the honest way: by being inspectable, not by asking for it.
Yours to run
Permissive and copyleft licenses. Clone it, extend it, run it on your own hardware.
Why open matters here
Show, don't promise. Let an outside engineer build AI inside your patient, client, or customer data, and "trust me" stops being enough. The PDPL (Federal Decree-Law 45/2021) puts the burden on the controller to apply the technical and organisational measures that protect that data, and to stand behind them. Infrastructure you can read is infrastructure you can show: to a regulator, to your DPO, to an auditor. Not a slide describing the controls. The controls themselves, line by line.
A human stays in the loop. Under the PDPL, a data subject can object to an automated decision that carries legal or otherwise serious effects. Both projects are built around that. A human signs off, and the agent's reach is bounded: claude-pipelines pauses at approval gates, and orno caps iteration, tool surface, and effects in YAML. None of this asks for your trust. You read it in the source. If you're incorporated in the DIFC, or you process personal data there, Regulation 10 has expected evidence of exactly this kind of human-intervention trigger since it came into force on 1 September 2023. orno's contract is a near-literal fit.
The same tools I ship to you. These aren't a side hobby. They're the infrastructure that runs inside client engagements, so the auditability you can inspect here is the auditability you get when I build your system. The code is MIT and AGPL-3.0, free to run. What you pay for is the deployment, the regulatory mapping, and the ownership handover: a fixed-price 2-week POC from AED 15,000, scaling to a 6-week production deployment at AED 40,000-80,000. After I leave, you keep the source and run it on your own hardware. That's the opposite of a SaaS box you can never open or walk away from.
Two licenses, on purpose
claude-pipelines is MIT, permissive tooling you can embed, fork, and ship without friction. orno is AGPL-3.0, copyleft on the guardrail itself, so the enforcement layer can't be quietly forked and closed. The thing that holds the line stays open.