Truke Studio

• The question people ask internally and never out loud

What happens to our knowledge if Truke disappears?

It is the right question. The data you would put in KF is not a set of documents you could rewrite over a weekend — it is years of accumulated engineering experience, often the part your competitors do not have. Anyone asking you to hold it in their software owes you an answer with specifics in it rather than reassurance.

Here are ours.

• While we are here

It runs on your infrastructure. KF is self-hosted. There is no mandatory cloud, and no dependency on Truke operating a server for your installation to work. Air-gapped deployment is supported and is a normal thing for customers to want.

The database is one SQLite file. Not a proprietary container — a documented, open, widely-implemented format. You can copy it, back it up, and read it with tools that have nothing to do with us.

Everything is reachable over a documented API. The REST API covers what KF stores, and the MCP endpoint exposes it to an AI assistant you choose. Neither is a partial view kept deliberately incomplete to make leaving harder.

Export is a first-class path, not a courtesy. The FMEA table, the compliance register and any listing export to CSV and XLSX, each carrying a provenance header naming the database and the moment it came from. A component tree round-trips: export it, edit it elsewhere, import it back.

Your licence is perpetual for the version you obtained. If a subscription lapses, the software you have keeps working. You are not renting access to your own records.

• If we stop

Self-hosting already means our disappearance does not switch anything off. But a running binary you cannot fix is a slow problem rather than no problem, so the licence addresses it directly:

EULA §13.3 — Open-source fallback In the event that the Rights Holder permanently ceases development and commercial distribution of the Software — defined as a continuous period of twenty-four (24) months without a new release and without a substantive response to reported defects — the Rights Holder commits to releasing the Software source code under the MIT License.

Two years of silence and the source becomes MIT. There is also §13.2: the end of our commercial activity does not affect your right to keep using the version you licensed.

The licence states its own limit on this, and so will we: the commitment is contractual, and its enforceability against an estate or legal successors may vary by jurisdiction. It is a real undertaking rather than a guarantee that survives every possible circumstance, and you should read it as the former.

• What this is not

A page about trust that only lists reassurances is not worth reading, so:

KF is not open source today. It is commercial software under a EULA, and the licence does not permit reverse engineering beyond what EU law provides for. The MIT fallback is a dormancy clause, not the current licence.

This is not a source-code escrow arrangement. No third party holds a copy on your behalf. If you need formal escrow, ask us before you buy rather than after — it is not something we offer today, and you should know that while it is still a cheap thing to find out.

We are a small vendor. Self-hosting, an open database format and a documented API reduce what that costs you if we fail. They do not make us large.

Your knowledge remains yours.

• The question people ask internally and never out loud

• While we are here

• If we stop

• What this is not