How Apuna works — for the people who use it.

Our first paper, co-authored by JTO and an Apuna AI agent (disclosed as such): how we build AI you can audit — a documented loop where agents propose, a review panel scores, a verification step checks every claim against the rendered page, and a human greenlights each change before it ships. The proof is reflexive: this site was built that way. Read it on the page, or download it as a PDF.

Every engagement starts the same way: you bring your brief and, if you have one, your company URL. We run discovery and deep research to understand the operation, the constraints, and the decision you actually need to make. From there the crew builds in a stream of small, contained changes — each one reviewable before it ships. When the work is done, the application runs on your infrastructure, the code is licensed Apache-2.0, and it is yours. No proprietary cage, no lock-in clause. The expensive part of leaving would be replacing the people who know your system — and most clients find that is a reason to stay, not to leave.

This is the most important thing to understand about how we build. Every change we make is rendered for you as a real page before it ships. You review what the change looks like and does — not the underlying code. You greenlight it, it ships. You push back, we revise. The decision is always yours, made on the thing a real user would see, not on a wall of coloured code. That principle is not an aspiration — it is a structural constraint we build every engagement around.

After handover, Apuna Care is the subscription that keeps your application running. Three tiers: Community is self-service — the open-source documentation and best-effort community support, right for teams who want to run it themselves. Standard adds managed maintenance: patches, security updates, and business-hours support with defined response times. Premium is full assurance: everything in Standard, plus priority incident response across extended European hours (currently around GMT±1), a target of approximately one hour response on critical issues within those hours, proactive monitoring, and a named contact who knows your system. We commit to response time — when a specialist starts work — not a guaranteed fix clock, because real systems vary. No prices on this page; talk to an engineer. Follow-the-sun coverage across more time zones is the direction we are heading — one zone at a time as the team grows.

Commodity Intelligence is a live tool available at /commodity. Paste your company URL: the system surfaces up to five key purchasing commodities — the materials or inputs that drive the most value in your direct procurement, weighted accordingly. It then tracks spot and futures markets for those commodities in a live dashboard. The purpose is to give your procurement team evidence-based timing for buying and hedging decisions. It is decision support, not financial advice, and the judgment call is always yours.

The AI in our tools is disclosed, never disguised. The full privacy policy — what we collect, why, the legal basis, your rights, and the sub-processors involved — is at /datenschutz. If you have a specific question about how your data is handled in an engagement, write to hello@apuna.dev. A human answers.

If you are ready to scope a project or just want to understand what is feasible for your operation, the contact form is the right first move. Tell us where you are today and where you want to be. We respond with a concrete plan — not a sales deck. Typical response: within one business day.

The agent crew that researches, designs, writes, and builds Apuna — the codices, skills, methodology, and prompts that make up apuna/core — is open-source and fully documented on GitHub. We keep it there deliberately: in the open, version-controlled, auditable, and not duplicated here. If you want to understand how the crew operates, the repository is the primary source. What you find in this Academy is documentation for working with Apuna as a practice and a product — a different thing.