Self-hosted
Your infrastructure. Your credentials. Your policies. Your evidence.
LIMEN13 is software you run. It does not contact us, and it connects only to the destinations you configure.
In plain words. You install LIMEN13 on your own servers, like any software you run yourself. Your keys, rules and records stay with you. Nothing is sent to us.
Architecture
Where it sits
Request path
- Identity and run token
- Policy checks and authorization
- Human approval when required
Evidence path
Deployment
Three ways to run it
| Option | When | How |
|---|---|---|
| Docker with an HTTPS proxy | A DNS name and automatic certificates | A compose file starts the engine behind the Caddy web server. |
| systemd service | A virtual machine with certificates from your own PKI | The engine serves TLS itself. |
| Behind your reverse proxy | nginx, HAProxy or a load balancer you already run | The engine listens on the local interface and your proxy terminates TLS. |
- Runtime
- The container image, or Python 3.12 or newer.
- Container
- Runs as a non-root user with a read-only root filesystem, all capabilities dropped and no new privileges. The base image is pinned by digest.
- TLS
- Required. The engine refuses to listen on a network interface without TLS.
- Scale-out
- One engine process per workspace. Do not run replicas of one workspace: a second engine on the same evidence refuses to start.
- Sizing
- Not published. Capacity under sustained load has not been measured; we measure it with your workload during the pilot.
Credentials and access
Secrets and sign-in
Secret storage
Secrets are read by name from one store: secret files (Docker and Kubernetes secrets) or HashiCorp Vault / OpenBao KV v2. Environment variables are for lab use. If a vault is configured but unreachable, the engine does not start.
Keys at rest
Stored service tokens are encrypted with AES-256-GCM under random data keys, which a separate key-wrapping key protects. Agent keys and console keys are stored only as SHA-256 digests.
Console sign-in
Generated access keys, or single sign-on with OpenID Connect (authorization code with PKCE). Your identity provider proves who someone is; LIMEN13's own list still decides their role.
Roles
Approver, SOC and operator. Every console route has a role check, and every route is covered by an access-control test.
Network
Make LIMEN13 the only way out
LIMEN13 checks what passes through it. An agent that can reach a model provider or a business API directly can go around it, so your network has to close those paths.
- Agent machines may reach only the LIMEN13 engine, and DNS if they need it.
- Reference rules are included for a Linux host (nftables), for Kubernetes (NetworkPolicy) and for Docker (an internal network).
- A collector on each agent machine can test the listed paths about once an hour and record the result. An open path raises a critical alert.
What a passing check means
It shows that the rules held when they were tested. It does not prove that no other path exists.
Data flows
What stays, and what leaves
| Data | Where it is | Does it leave your infrastructure? |
|---|---|---|
| Policies, configuration, agent inventory | Your workspace folder | No. |
| Evidence chain and reports | Your disk | No, unless you send copies of the chain head to your own off-site storage. |
| Provider and service credentials | Your secret store; stored tokens are encrypted at rest | No. Each is presented only to the service it belongs to. |
| Prompts and model answers | They pass through the gateway. Prompts are not stored, only their SHA-256. | Yes, to the model providers you configure. |
| Tool calls and results | They pass through the gateway. | Yes, to the business services you register. |
| Alerts | Your evidence chain | Yes, to the SIEM, webhooks, Slack or Teams you configure. |
| Sign-in | Your identity provider | Yes, to your identity provider when single sign-on is switched on. |
| Usage data or telemetry to LIMEN13 | None is collected | No. The software does not contact us. |
Operations
Logging, backup and updates
Security logging
Every decision, approval, sign-in and evidence read goes into the signed chain. A heartbeat at least every minute makes silent periods visible. A public health endpoint reports liveness.
Backup and recovery
A command creates, verifies and restores encrypted backups of a workspace. The evidence-signing key is kept separately: restore both together. Recovery time and recovery point objectives are not published; define them for your deployment.
Updates
Stop the engine, replace the release, run the verification script on a staging copy, then restart. At start, the engine refuses changed connectors and corrupted evidence.
Responsibilities
Who does what in an incident
| Task | You, or your MSSP | The LIMEN13 software |
|---|---|---|
| Detect | Watch your SIEM and the console. | Raises alerts with a severity and a framework mapping. |
| Contain | Decide, and use the kill switch. | Refuses the agent's next calls; contains runs when thresholds are reached. |
| Investigate | Read the storyline; check your business systems. | Provides the signed, ordered record. |
| Recover | Rotate keys, correct the policy, restore if needed. | Rotates agent keys on request; verifies evidence at start. |
| Availability | Operate the server, its backups and its monitoring. | No managed service and no response-time commitment in the pilot program. |
Install it on a server you control.
The pilot starts with an assisted installation on a non-production system.