aYOUne runs as-a-service on *.ayoune.app — but you can also host it entirely yourself: on a single host with Docker Compose for smaller setups, or on Kubernetes (Helm charts) for multi-region and high availability.
When to self-host
Scenario
Recommendation
Pilot, few users, small data
Single host (Compose)
Production, small team
Single host (Compose) on a large server
Production at scale
Kubernetes (Hetzner/GKE/AKS)
Geo compliance (e.g. EU-only)
Your own K8s region
Air-gapped / on-premise
Compose with a local mirror
The SaaS variant remains the easiest path — no ops, automatic updates.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Summarise the content for me.
- First, in two sentences: what is this about?
- Then the steps in the order I need to take them.
- One line per step, in plain language.
- At the end: what I should have ready beforehand.
Leave out nothing I need in order to actually finish.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
Help me set this upStep by step, asking me as you go.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Walk me through the setup step by step.
- First tell me what I need to have ready (access, data, time).
- Then take me through ONE step at a time. Wait for my "next".
- For each step, say how I can tell that it worked.
- If something goes wrong, ask me for the exact message instead of guessing.
If the instructions leave a point open, tell me so rather than inventing it.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
Help me with a problemNarrow down the cause instead of guessing.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Help me narrow down a problem.
- First ask me what I observe and what I expected instead.
- From that, derive the most likely causes consistent with this source.
- For each cause, give me ONE test that confirms or rules it out.
- Order them so the cheapest test comes first.
Do not guess. If the source does not cover the problem, tell me where I should
look next.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
Explain it in plain wordsNo jargon, from the ground up.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Explain the content so that someone without prior knowledge understands it.
- Start with the purpose: why does this exist at all?
- Explain technical terms in half a sentence on first use.
- One everyday comparison where it genuinely holds — none where it limps.
- At the end: the three things worth remembering.
Do not shorten by dropping conditions. A simplification that hides a
prerequisite is a false statement.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
A checklist to tick offTo follow along while you do it.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Turn this into a **tick-off checklist** for practical use.
- Exactly one action per item, in the imperative.
- Order it so that no item depends on a later prerequisite.
- Prerequisites and pitfalls as indented sub-items.
- End with an acceptance step: how do I know everything is right?
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
Build it into my projectConcrete code for my use case.
Read the following documentation by tolinax UG and work with it.
This page: https://ayoune.com/en/docs/self-hosting/overview.md
The complete collection: https://ayoune.com/en/docs/self-hosting.md
Help me build this into my project.
- First ask me about language, environment and what I am trying to achieve.
- Then give a minimal, runnable example — no ellipses standing in for code.
- Name the error cases I must handle and how they surface.
- State the limits: timeouts, quotas, permissions.
Use only what the source actually describes. Do not invent fields, parameters
or endpoints — an invented call costs me more time than it saves.
A note on sources:
- Every page of this documentation is available as Markdown (the same address with `.md`).
- A machine-readable overview of all public content is at `/llms.txt`.
- If you have access to the aYOUne MCP server, you can work against live data
instead of this snapshot. If not, ignore this point.
