> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ferrufino-tech-solutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Ferrufino Tech Solutions is a Case Knowledge Platform for technical operations teams. Capture what you learn on the shop floor, in the lab, or in the field — then find it again when it matters.

<Note>
  **New here?** Head straight to the [Quickstart](/en/quickstart) — you can create your first case in under five minutes.
</Note>

## What FTS does

Every technical operations team accumulates hard-won knowledge: a failure mode a technician diagnosed at 2am, a workaround an engineer scribbled in a notebook, a photo of a burned connector that turned out to be the root cause of a recall. This knowledge is almost always lost the moment the person who owns it changes role, retires, or simply forgets.

**FTS turns that tacit knowledge into a structured, searchable, auditable asset.** You write it down once, attach the evidence, run it through a lightweight review, and from that point on the case is reusable across your whole team — and usable by AI assistance that understands your taxonomy.

We designed FTS for teams that do **complex, high-stakes, technical work**:

* Manufacturing quality and reliability
* Automotive testing and homologation
* Energy and utilities operations
* Aerospace MRO (maintenance, repair, overhaul)
* Industrial R\&D and prototyping

If your team fills out 8D reports, root-cause analyses, field service tickets, lab notebooks, or failure reports, FTS is built for you.

## Why a "case" and not a "document"

Most knowledge tools (Notion, Confluence, SharePoint) treat everything as a free-form document. That is fine for brainstorming, but poor for technical operations, where you need:

1. **A clear state** — is this observation a rumor, a verified finding, or the official record?
2. **Traceable evidence** — every claim has an attached photo or PDF.
3. **A review trail** — someone else has to confirm the claim before it becomes canon.
4. **Structured metadata** — so you can answer "show me every verified failure on part number X in the last 6 months" without reading 200 pages.

A **case** is the unit that ties all of this together. It has a lifecycle (`Draft → In Review → Verified → Published → Deprecated`), attached evidence, tags from your taxonomy, and a permanent audit log.

## How FTS fits into your stack

FTS is a web application. You do not need to install anything. Your team signs in at `https://app.ferrufino-tech-solutions.com`, and all data is stored in a secure EU-hosted database. The tenancy boundary is the **organisation**, not the workspace: data belonging to another organisation is not reachable. Inside an organisation it is not a boundary — see [Workspace isolation](/en/account/security).

FTS does not replace your ERP, MES, PLM, or ticketing system. It lives **alongside** them and captures the knowledge that those systems do not — the "why", the "what we tried", and the "what actually worked".

## What's next

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/en/quickstart">
    Create your first case in under five minutes.
  </Card>

  <Card title="Core concepts" icon="lightbulb" href="/en/concepts">
    Workspaces, cases, evidence, reviews, taxonomy — in one page.
  </Card>

  <Card title="First case walkthrough" icon="book-open" href="/en/guides/first-case">
    A guided example using a real failure report.
  </Card>

  <Card title="Invite your team" icon="users" href="/en/guides/invite-team">
    Roles, permissions, and how to onboard reviewers.
  </Card>
</CardGroup>