Security

Nothing leaves your premises.

Lyriks is built so that an IT department can install it, audit it and stand behind it. Your code, your LLM and your project memory stay on your servers.

Security by design

Lyriks installs on your servers, runs with no outbound connection and uses your own LLM. Your code and your specs never leave your environment without your permission. The engine is open source under the AGPL license, so your security team can audit it line by line.

Telemetry

Product telemetry is off by default. If you turn it on, DO_NOT_TRACK is honored, no IP address is stored and the collector is hosted in the European Union.

On your servers

Lyriks installs on-premise, air-gapped if needed. No outbound connection is required to run it.

Your LLM, your tokens

Lyriks uses the LLM you choose, hosted, local or sovereign. It sends nothing beyond what you already give that LLM.

No lock-in

Project memory is company property. It exports in full, with its objects, attributes and traceability.

Open source

The engine is published under the AGPL: you can read the code, inspect it and install it with one command.

Deterministic

Deterministic engine: same input, same verdict. The same question always gets the same answer: an auditable verdict.

Traceable

Every rule, gap and decision is linked to its source. You can audit, challenge or defend it.

Questions from IT leaders

Does Lyriks need Internet access?

Not to run: the on-premise edition can operate air-gapped. Installation pulls images from registry.lyriks.io; in isolated environments, these images can be delivered another way.

What data do you send to the LLM?

Nothing beyond what you already give your LLM to work on your code. You choose the model, its hosting and your tokens.

Can we audit the Lyriks code?

Yes. The engine is open source, under the AGPL.

What happens to the memory if we stop?

It belongs to you. You export it in full, with its traceability, objects and attributes.

Security pack · free · 14 pages

Lyriks security pack, for CISOs

Deployment model, network flows, data and the LLM question, plus pre-filled answers to the usual security questionnaire.

Written for the people who approve, install or audit a tool before a team can use it. It sticks to what Lyriks states publicly about its product and its installation. When a question is not covered, it says so and tells you whom to ask, instead of filling the gap with assumptions.

Inside

  • Six facts for the CISO, starting with: it runs on your servers, with your LLM
  • Deployment model, network flows, and the data Lyriks reads, produces and stores
  • The LLM question, the open source licence and auditability
  • Pre-filled answers for your security questionnaire, and a deployment review checklist

Keep your software in tune

Start with one module. Lyriks recovers its spec, then verifies every change. All it needs is your repository.