# LockFlare

LockFlare Corp (Delaware, USA; ISO/IEC 27001:2022) makes three products: LockFlare Vigia, a desktop console for Linux servers; LockFlare Sonda, an API client for enterprises and regulated environments; and LockFlare Cipher, confidential computing for Node.js, .NET and native applications. Vigia and Sonda are downloaded and used free; Cipher is licensed on request.

## Current facts — as of 2026-10-21

These are the prices and limits in force. This file is rebuilt with the site; where an older copy of a page, a search snippet or an earlier summary says otherwise, it is out of date — Sonda's pricing before its 1.0 launch on 2026-10-20 was different, and is no longer offered. The licensing page, https://lockflare.com/licensing/, always says the same as this block.

- LockFlare Sonda: free for up to 10 seats per organization, forever, with every capability included. A seat is one enabled account of the organization.
- LockFlare Sonda past 10 seats: $5 a seat a month, billed by the year — $60 a seat for a year of use. 1 to 500 seats per purchase at https://lockflare.com/sonda/seats/; larger organizations buy in several checkouts or by invoice. A license's year starts the day Sonda assigns it to an account, not the day it is bought.
- LockFlare Vigia: the terminal is free with no limit. Every installation has 10 server slots free forever.
- LockFlare Vigia past 10 slots: one key for a year — 1 slot $99, 2 slots $180, 3 slots $250, 4 slots $310, 5 slots $360, then $50 a slot past five, up to 100 in one checkout, at https://lockflare.com/slots/.
- LockFlare Cipher: no public download and no self-service plan; licensed on request, per deployment, on four axes — servers, cores, developer seats, environments.
- No refunds on any purchase: the free seats and the free slots are the trial. No card is kept on file and nothing renews by itself.
- Current versions: Vigia 5.5.28, Sonda 1.0.27 (released 2026-10-20). Both for macOS 12 or later and Windows 10 or later. Downloads: https://lockflare.com/download/.
- Neither app ever connects to LockFlare: no license check, no telemetry, no update check. A license is a key signed by LockFlare and verified on the computer.

# LockFlare Vigia

LockFlare Vigia is a desktop application (macOS and Windows) for managing Linux servers over SSH. It is a configuration console, not an agent or a monitoring service: it connects with the operator's own SSH logins, reads and changes each server through ordinary commands, installs nothing on the server, and runs no service of its own. The operator's identity is an encrypted key file kept on the computer, sealed under a password, plus Touch ID or Windows Hello; there is no login and no cloud account in the loop.

Pricing: the terminal is free with no limit — any box you can SSH into is a "terminal" in Vigia, with unlimited servers, no license and no count. What is licensed is what Vigia does to a box as root (security setup, system setup, backups, packages, databases, clusters): every installation has 10 slots for those, free forever, with no account; past them, slots are bought in one key for a year — 1 for $99, 2 for $180, 3 for $250, 4 for $310, 5 for $360, then $50 per slot, up to 100 in one checkout. No refunds.

What Vigia does on a server: a full terminal (splits, broadcast, history, recordings), Security Setup (firewall, Fail2Ban, SSH hardening proven by a fresh login, password policy, WAF with ModSecurity and CrowdSec, integrity and rootkit checks, AppArmor/SELinux, kernel hardening, scheduled tasks, time), System Setup (users, groups, certificates with a vault, automatic updates, audit, services, storage, network), tunnels, an HTTP tunnel through the server, file management with an editor, backups to named repositories, and an AI sysadmin, Themis, who reads through curated probes and proposes changes the operator confirms.

What Vigia installs and administers: nginx or Apache with sites as things, vsftpd or ProFTPD, Postfix with DKIM and DMARC and Dovecot mailboxes, Docker with compose stacks and stack templates, KVM/libvirt virtualization, MariaDB, PostgreSQL and MongoDB with replication, MongoDB sharding, cluster backups and TLS between members, Redis or Valkey with Sentinel, a WireGuard mesh between servers — built by dropping them in, every tunnel proved from both ends, listening ports shut to everything but the private network in one firewall change, the MTU measured on every wire — and an HAProxy load balancer that follows a database pair's primary.

Across servers: Overview (the servers at a glance — security, health, disk, backups, updates and more, a dot per check, read without opening a tab), Actions (run a command exactly as typed, ask a question, install, set up the same thing on every picked server), Snippets, Flows (steps drawn once on a canvas and run on one server or many — all at once, a few at a time, or one at a time, a row per server and a column per step) and Themis, asked about the picked servers or a saved group of them — all on one shared pick of servers; Deployments (a folder from this computer — an app, a website, configuration, scripts, certificates — onto one server or a whole group from a kept recipe: every box checked first, the upload staged beside the live folder and verified by hash, the first box alone then a few at a time, only changed files sent, and any run undone on the servers in one press); and NOC diagrams where every wire is proved from the box the traffic starts at.

Licensing: every installation has 10 server slots free forever (they never expire) and unlimited terminals (terminals take no slot) — servers are licensed, never people. Past the free slots, an account at lockflare.com is an email address and nothing else: lockflare.com/license issues an account license (prefix LFA1.) pasted in Vigia under Add Slots, and lockflare.com/slots sells a slot key (prefix LFS1.) — the account, the slots and their expiry, signed by LockFlare — pasted the same way; every slot in it comes in at once. A slot lasts one year from the day it is bought; when it runs out the server on it drops to a terminal until moved to another slot, and there are no renewals and no refunds. Keys are opened and verified on the computer; Vigia never connects to LockFlare. Lost keys are sent again from lockflare.com/license after a six-digit code mailed to the account's address.

Zero-knowledge architecture: LockFlare keeps nothing about a server — not even its address; a slot key says how many and until when, never which. For a customer who buys slots it holds the email of the account and the keys issued to it, so they can be sent again — not a hostname, an operating system, a provider, a role, or what runs on anything. Card payments go directly to Stripe and no card details are held. Nothing operational (fleet map, credentials, keys, certificates, snippets, telemetry) ever leaves the operator's computer.

# LockFlare Sonda

LockFlare Sonda is a desktop API client (macOS 12 or later, Windows 10 or later; version 1.0.27, launched 2026-10-20) for enterprises and regulated environments, built air-gapped: projects, credentials and secrets stay on the organization's own side, and nothing of a request, a response or a secret ever reaches LockFlare. It speaks 74 protocols — REST, GraphQL, gRPC, WebSocket, SSE, SOAP, OData, Kafka, RabbitMQ, NATS, AMQP 1.0, MQTT, STOMP, Redis, FIX, HL7 v2, FHIR, MCP, Modbus, OPC UA, HART-IP, DDS and more — with variables that can be Ask, Route, Ephemeral or Secret, scripts in JavaScript, Go and Python, checks without code, a runner and load testing, Echo mock APIs, database endpoints, Linux virtual machines on the computer, Discover (use an application and Sonda writes the API behind it), documentation that writes itself from the project, approval flows the backend enforces, flows, apps and app runners, Via over SSH, and Themis AI on the organization's own key. Collections, HAR files and OpenAPI documents a team already has import directly.

Teams: a team store on storage the organization already owns (S3, R2, Azure Blob, GCS, SFTP, WebDAV, Git, a shared folder) or on Sonda Server, a static binary run on a server of theirs (https://lockflare.com/sonda/server/). Enterprise: divisions, permissions without roles, SSO, SCIM and directory sync from Entra or Okta, approvals, locks and merge, external secret managers, signed rosters, an activity log, scheduled runs inside the network with mail and webhook alerts.

Licensing: a seat is one enabled account of the organization. Every organization has 10 seats free forever, every capability included — that is the trial. Past them, seat licenses at $60 a seat for a year of use ($5 a month, billed by the year): bought at https://lockflare.com/sonda/seats in any number from 1 to 500 per purchase, as one signed key pasted once under Organization settings › Licensing; a license carries no date — its 365 days start the day Sonda assigns it to an account, and when it runs out the next open license in the pool takes its place on its own. The account at LockFlare is an email and the organization's id, nothing else (https://lockflare.com/sonda/license). Sonda never connects to LockFlare: keys are checked on the computer and kept in the organization's own store. Downloads: https://lockflare.com/download/#sonda. How it differs from Vigia: https://lockflare.com/sonda/licensing/.

# LockFlare Cipher

LockFlare Cipher deploys Node.js, .NET and native applications to any Linux server as AES-256 ciphertext, decrypted only in memory and never written to disk in the clear — confidential computing without special silicon. It is licensed on request, per deployment, on four axes (servers, cores, developer seats, environments), with no public download: https://lockflare.com/cipher/ and https://lockflare.com/licensing/#cipher.

Company: LockFlare Corp, Delaware, USA. Contact: engineering@lockflare.com. Website: https://lockflare.com.

## LockFlare Vigia, feature by feature

- [LockFlare Vigia — everything it does](https://lockflare.com/lens/): Everything LockFlare Vigia does on a server and across a fleet: terminal, security, databases, web, mail, containers, VPN, backups, AI.
- [Terminals in LockFlare Vigia — free, on unlimited servers](https://lockflare.com/lens/terminals/): A full SSH console for free: unlimited servers, no license, no account. Tabs and splits, broadcast to every shell, history, tunnels, files, snippets.
- [Actions in Vigia — one thing, every server](https://lockflare.com/lens/actions/): Pick servers, run one line on all of them, ask one question and read the answers grouped, install what is missing, or make the same change everywhere.
- [Deployments in LockFlare Vigia — a folder onto every server](https://lockflare.com/lens/deployments/): Send a folder to ten servers from one recipe: every box checked first, the first goes alone, only changed files travel, and any run is undone in one press.
- [Overview in LockFlare Vigia — every server at a glance](https://lockflare.com/lens/glance/): One reading on every server at once, a dot per check, without opening a tab: security, health, disks, backups, databases, updates, exposure, drift.
- [Servers and terminals in LockFlare Vigia](https://lockflare.com/lens/servers/): The SSH console in LockFlare Vigia: the map, bastions, split-pane terminals, broadcast, history, tunnels, files, actions across a fleet.
- [The NOC in LockFlare Vigia — every wire between servers, proved](https://lockflare.com/lens/noc/): Drop your servers on a canvas and Vigia draws how they connect from their own firewalls and live connections, and proves every wire from the box it starts at.
- [Security setup in LockFlare Vigia](https://lockflare.com/lens/security/): LockFlare Vigia hardens a Linux server in plain words: firewall, Fail2Ban, SSH proven by a fresh login, ModSecurity and CrowdSec, AIDE, rkhunter, AppArmor.
- [Databases in LockFlare Vigia — MongoDB, PostgreSQL, MariaDB](https://lockflare.com/lens/databases/): MariaDB, PostgreSQL and MongoDB in LockFlare Vigia: explorer, users, backups, performance, replication, sharding, TLS, Redis with Sentinel.
- [Server management in LockFlare Vigia](https://lockflare.com/lens/system/): Users and groups judged, certificates with a vault, updates that stay applied, audit, services, storage and network — the day-to-day of a Linux box.
- [MariaDB in LockFlare Vigia — install, replicate, tune](https://lockflare.com/lens/mariadb/): MariaDB on your own servers, run from Vigia: installed secure, replication built by dropping servers in, TLS between members, every setting explained.
- [MongoDB in LockFlare Vigia — replica sets and sharding](https://lockflare.com/lens/mongodb/): A replica set in two minutes and a nineteen-server sharded cluster in 43, on real screens: TLS, safe updates, cluster backups, restore.
- [Web, mail, containers and VPN in LockFlare Vigia](https://lockflare.com/lens/packages/): nginx or Apache, Postfix with DKIM and DMARC, Docker, KVM, a WireGuard mesh, an HAProxy balancer and backups — installed from one hub.
- [Redis and Valkey in LockFlare Vigia](https://lockflare.com/lens/redis/): Redis installed safe by default, a Sentinel set built by dropping servers, grown live, failed over by the sentinels, connect strings per driver.
- [Containers in LockFlare Vigia — Docker, end to end](https://lockflare.com/lens/containers/): Docker in LockFlare Vigia on real screens: the daemon governed, ufw made to rule its ports, stacks, logs, volumes backed up and restored.
- [Virtualization in LockFlare Vigia — KVM guests](https://lockflare.com/lens/virtualization/): KVM guests on your own servers: a machine from a cloud image in one form, an ISO installed over a tunnel, a port published, and a bridge with an armed revert.
- [WireGuard in LockFlare Vigia — a private mesh between servers](https://lockflare.com/lens/wireguard/): A WireGuard mesh between your Linux servers, built by dropping them in: nine boxes wired in 43 seconds, every tunnel proved, ports shut to the internet.
- [Your account — how LockFlare Vigia knows it's you](https://lockflare.com/lens/account/): Vigia has no login: an encrypted key on your computer, sealed under your password, Touch ID or Windows Hello behind it. One backup file restores it.
- [Mail in LockFlare Vigia — our own mail server, on real screens](https://lockflare.com/lens/mail/): The mail server behind lockflare.com, run from Vigia: Postfix, DKIM, SPF and DMARC with the records to copy, a spam filter, guarded logins, mail traced.
- [Websites in LockFlare Vigia — nginx and Apache](https://lockflare.com/lens/websites/): A site made from one form with HTTPS, names and redirects, protection, traffic from its own log, files edited on the server, backups.
- [Themis AI — the AI sysadmin inside LockFlare Vigia](https://lockflare.com/lens/themis/): Themis is the AI sysadmin inside LockFlare Vigia: ask in your own words and language, and she reads the server and proposes what to run. Nothing installed.

## LockFlare Sonda, feature by feature

- [LockFlare Sonda — the air-gapped API client for enterprises and regulated environments](https://lockflare.com/sonda/): The air-gapped API client: 74 protocols, Linux machines inside, documentation that writes itself, approval flows the backend enforces. Free up to 10 seats.
- [LockFlare Sonda — every capability, listed](https://lockflare.com/sonda/capabilities/): Every capability of LockFlare Sonda, the air-gapped API client: 1,687 lines across 55 areas, each checked against the code that ships. All of it free.
- [LockFlare Sonda, air-gapped by design — what leaves this computer, and what never does](https://lockflare.com/sonda/air-gapped/): No telemetry, no analytics, no crash upload, no update check, no license phone-home. Every file sealed with Argon2id and AES-256-GCM. Verified offline.
- [HTTP, GraphQL and RPC in LockFlare Sonda — requests and answers](https://lockflare.com/sonda/http/): Every body type, nine auth methods, a verdict the status code cannot give, a timing waterfall, diffs between sends, types in five languages, Excel out.
- [WebSocket, Socket.IO, SSE, gRPC and STOMP in LockFlare Sonda](https://lockflare.com/sonda/realtime/): WebSocket, Socket.IO, server-sent events, gRPC in all four shapes with a live stream kept open, and STOMP over WebSocket, each a live item of a Sonda project.
- [Kafka, RabbitMQ, NATS, AMQP 1.0, Redis, MQTT and STOMP in LockFlare Sonda](https://lockflare.com/sonda/messaging/): Kafka, RabbitMQ, NATS, AMQP 1.0, Redis, MQTT and STOMP from one desk, read without moving production state: no offset committed, no message taken.
- [FIX, HL7 v2, FHIR and OData in LockFlare Sonda — finance and health](https://lockflare.com/sonda/vertical/): A FIX engine with the full session layer and a 1,600-field dictionary. HL7 v2 over MLLP, sender and listener, twelve versions. FHIR and OData with verdicts.
- [Modbus, OPC UA, HART-IP and DDS in LockFlare Sonda — industrial devices](https://lockflare.com/sonda/industrial/): Modbus, OPC UA, HART-IP and DDS as items of a project: one tag model, report-by-exception watching, confirmed writes, a reading past a line starts a flow.
- [MCP servers in LockFlare Sonda — tools, resources, prompts, OAuth](https://lockflare.com/sonda/mcp/): Connect an MCP server over stdio or HTTP, call its tools from a form built from the schema, read resources and prompts, sign in with OAuth. Themis drives it.
- [Variables, environments and the workspace in LockFlare Sonda](https://lockflare.com/sonda/variables/): Environments that build on each other, "My values" that never leave the computer, and variables that can be Secret, Ask, Route or Ephemeral. All sealed.
- [Scripts and checks in LockFlare Sonda — JavaScript, Go, Python; tests without code](https://lockflare.com/sonda/scripts/): Scripts in JavaScript, Go or Python with one sonda API. Checks as sentences: ten subjects, 25 operators, JSON Schema. Other clients' scripts import too.
- [The runner, the Runner view and load testing in LockFlare Sonda](https://lockflare.com/sonda/runner/): Run a project with datasets up to 10,000 rows and HTML, JUnit or JSON reports. A Runner view for people who only send. Load tests with 500 virtual users.
- [Echo mock APIs and database endpoints in LockFlare Sonda](https://lockflare.com/sonda/echo/): Echo answers instead of a real API from live data, a body, a script or a flow. Databases become endpoints at sonda:// with bound parameters, reads-only.
- [Discover in LockFlare Sonda — true reverse engineering of an API from the traffic](https://lockflare.com/sonda/discover/): Use the application and Sonda writes the API behind it: a browser read over DevTools, a proxy for phones and apps, or a HAR. Paths templated, tokens traced.
- [Linux virtual machines in LockFlare Sonda — a server on your own computer](https://lockflare.com/sonda/machines/): Small Linux servers on your Mac or PC, from Sonda's title bar: install Node, PostgreSQL, nginx in a click, run the API there, call it from any request.
- [Specs, imports, exports and documentation in LockFlare Sonda](https://lockflare.com/sonda/specs/): Import OpenAPI, Swagger, WSDL, OData, FHIR, HAR, cURL and other clients' collections. Read answers against the spec, update without losing edits, write docs.
- [Flows in LockFlare Sonda — a canvas of steps, started by a message or a reading](https://lockflare.com/sonda/flows/): Thirteen step kinds on a canvas. A Call is any request, gRPC, MCP tool, broker or device. Started by hand, by a message, by a device reading, or as a webhook.
- [Apps and app runners in LockFlare Sonda — screens over your own APIs](https://lockflare.com/sonda/apps/): An app turns a project's requests into screens, tables and dashboards for people who never see a request. A runner seat sends only what its apps send.
- [Via in LockFlare Sonda — send a request from a server you reach over SSH](https://lockflare.com/sonda/via/): A tunnel item is an SSH login Sonda holds open. Pick it under Via and the request is made from that server: no agent, no local port, changed keys refused.
- [Themis AI in LockFlare Sonda — your key, your provider, your click](https://lockflare.com/sonda/themis/): Your key for Anthropic, OpenAI, xAI or a local model. Forty-two tools that build inside Sonda's own code. Sending, deleting and running a folder need a click.
- [Schedules in LockFlare Sonda — your APIs run on a cadence, inside your network](https://lockflare.com/sonda/schedules/): Sonda Server runs a request, a folder or a whole project on a cadence, inside your network. Alerts by mail or webhook, a daily or weekly summary.
- [The team store in LockFlare Sonda — collaboration on storage you own](https://lockflare.com/sonda/team-store/): A file store that runs no code and keeps no secret: S3 and its houses, Azure, Google Cloud, SSH, WebDAV, Git, MongoDB or Sonda Server. A key per project.
- [Sonda Server — the team store on a server of the organization's own](https://lockflare.com/sonda/server/): One static binary for Linux and Windows that keeps the team store on your server. TLS 1.3 only, a pinned certificate, an empty 404 without the token.
- [Organizations, divisions and permissions in LockFlare Sonda](https://lockflare.com/sonda/organization/): An owner, divisions that are teams of their own, administrators and members. Permissions without roles: one flag per action per person, with hours and expiry.
- [SSO, SCIM and directory sync in LockFlare Sonda — enterprise identity](https://lockflare.com/sonda/identity/): OpenID Connect and SAML 2.0 single sign-on with no LockFlare server in the loop. A SCIM 2.0 bridge on your own server. Directory sync from Entra ID and Okta.
- [Approvals, edit locks, merge and history in LockFlare Sonda — change governance](https://lockflare.com/sonda/governance/): Approval workflows with quorums, stages and conditions; items frozen while a submission is open; edit locks of 1 to 168 hours; three-way merge; history kept.
- [Secrets in LockFlare Sonda — resolved at send, never written](https://lockflare.com/sonda/secrets/): A secret:// reference fetched at send from Vault, AWS, Azure, Google, 1Password, Doppler or Infisical, never written. Or Sonda's own vault, a key per secret.
- [Activity log and mail triggers in LockFlare Sonda](https://lockflare.com/sonda/activity/): Every action signed by the person who did it and sealed to the owner and administrators. Nineteen triggers mail chosen people the moment something happens.
- [How LockFlare Sonda is licensed — seats, ten free, a year of use each](https://lockflare.com/sonda/licensing/): Sonda licenses seats, not servers: ten free forever, then $60 for a year of use that starts the day a license is assigned. Renewal from the pool, offline.

## The rest of the site

- [LockFlare — cybersecurity solutions for enterprises and regulated organizations](https://lockflare.com/): Air-gapped cybersecurity solutions for enterprises and regulated organizations: Vigia hardens servers, Cipher runs apps unreadable at rest, Sonda speaks APIs.
- [Air-gapped — nothing LockFlare makes phones home](https://lockflare.com/air-gapped/): Vigia and Sonda never connect to LockFlare; Cipher sends only ciphertext. What each one talks to, what we hold, and how to check it yourself.
- [Confidential computing without the silicon — LockFlare Cipher](https://lockflare.com/cipher/): LockFlare Cipher runs your applications on any Linux server encrypted at rest and executed only in memory. Node.js, .NET and native engines.
- [The LockFlare Cipher desktop app](https://lockflare.com/cipher/app/): LockFlare Cipher for macOS and Windows: import the projects you have, push them encrypted, group servers into environments, seal servers, run your team.
- [LockFlare licensing — Vigia, Sonda and Cipher](https://lockflare.com/licensing/): Vigia licenses servers, Sonda licenses seats — both free to start, with signed keys opened offline. Cipher is licensed per deployment, on request.
- [How LockFlare Cipher works — the architecture](https://lockflare.com/cipher/architecture/): One desktop app, one encrypted control plane, one engine per server. Source is readable only on your machine; everywhere else it is ciphertext, or RAM.
- [Download LockFlare Vigia and Sonda; Cipher on request](https://lockflare.com/download/): Download LockFlare Vigia and Sonda for macOS and Windows: signed, notarized universal Mac apps and signed Windows installers, a SHA-256 beside every file.
- [Getting started with LockFlare Vigia](https://lockflare.com/get-started/): From nothing to a server on your map in five minutes: an account on your computer, the first server on one of ten free slots, connect. Nothing to sign up for.
- [Projects in LockFlare Cipher — bring your own code](https://lockflare.com/cipher/projects/): Import a frontend build, a backend or a full-stack app into LockFlare Cipher as it is: twenty build tools, Node.js and .NET, native binaries, no SDK.
- [Contact LockFlare](https://lockflare.com/contact/): Write to the people who build LockFlare Vigia and Cipher: a feature question, licensing for a larger fleet, Cipher, or a security report.
- [Environments in LockFlare Cipher](https://lockflare.com/cipher/environments/): A set of servers running the same code. One push lands on all, each confirms on its own; compare builds by hash, promote without rebuilding, reset.
- [A LockFlare Cipher server, on disk and in RAM](https://lockflare.com/cipher/servers/): What is on a LockFlare Cipher server and what is in RAM: the engine and a license bound to its address, and nothing of yours on disk. Disposable by design.
- [The Node.js runtime in LockFlare Cipher](https://lockflare.com/cipher/node/): One vm context per tenant, host-installed packages, cluster workers, hot reloads in seconds — and nothing of yours on the host filesystem.
- [The .NET runtime in LockFlare Cipher](https://lockflare.com/cipher/dotnet/): Published .NET 10 apps — Razor Pages, MVC, Blazor Server, minimal APIs — decrypted in RAM and loaded from memory streams. No files on the server.
- [Trust and compliance — ISO/IEC 27001:2022](https://lockflare.com/trust/): LockFlare Corp is ISO/IEC 27001:2022 certified and won The Hacker News Awards 2026. Certificate and ISMS documentation on request.
- [The native runtime in LockFlare Cipher](https://lockflare.com/cipher/native/): Push a static Linux binary in Go, Rust, Zig, C or C++. Cipher decrypts it in RAM and launches it from an anonymous memory descriptor — zero files.
- [The security model of LockFlare Cipher](https://lockflare.com/cipher/security/): Every layer on one page: AES-256 end to end, five gates on every request, 2FA for everyone, encrypted transport on every leg — and the honest limit.
- [Server Enclave in LockFlare Cipher](https://lockflare.com/cipher/enclave/): Seal a server: every login disabled — SSH, console, KVM, IPMI — while sites and APIs keep serving. Second factor and a single-use nonce to seal or unseal.
- [Website privacy policy](https://lockflare.com/privacy/): How lockflare.com handles the little information it collects: your account, licensing, email and server logs. Nothing from Vigia reaches us.
- [Data sovereignty in LockFlare Cipher](https://lockflare.com/cipher/sovereignty/): Where the encrypted build rests: on your engines, in Cipher repositories, or in storage you run inside your perimeter. Ciphertext everywhere, no key with us.
- [Website terms of service](https://lockflare.com/terms/): The terms that govern lockflare.com, the licenses and server slots issued through it, and the LockFlare Vigia downloads it offers.
- [Team and permissions in LockFlare Cipher](https://lockflare.com/cipher/team/): Invitation-only members, two-factor for everyone, permissions per area and per environment, login rules per member. A vendor deploys, never extracts source.
- [Activity log and monitoring in LockFlare Cipher](https://lockflare.com/cipher/activity/): Every action attributed and timestamped — pushes, promotions, resets, seals, sign-ins — per project and per member. Plus live latency and heap per server.
- [How LockFlare Cipher is licensed](https://lockflare.com/cipher/licensing/): Licensed on request, to companies we have spoken with. A server license is bound to the machine's address and keys the builds it may decrypt.
- [LockFlare documentation — Vigia and Cipher](https://lockflare.com/docs/): LockFlare's documentation: Vigia screen by screen, what it writes on a server and what it refuses; Cipher, how a build is encrypted, delivered and run.

## Documentation

- [LockFlare Cipher documentation](https://lockflare.com/docs/cipher/): The technical documentation for LockFlare Cipher: how a build is packed, encrypted, delivered and executed in memory; the three pieces.
- [LockFlare Vigia documentation](https://lockflare.com/docs/lens/): Every screen in LockFlare Vigia, documented at the feature level: what it reads, what it writes on the box, what it refuses to do.
- [What is LockFlare](https://lockflare.com/docs/cipher/overview/): LockFlare keeps your source code encrypted everywhere it rests — on disk, in transit, and in storage.
- [The doctrine every feature follows](https://lockflare.com/docs/lens/doctrine/): The four rules every LockFlare Vigia feature follows: air-gapped, nothing installed on the server, long work detached on the box, and proved before kept.
- [How it works](https://lockflare.com/docs/cipher/how-it-works/): Four stages: pack, encrypt, deliver, execute. The only one that produces readable code is the last, and it happens in memory on a machine you own.
- [Identity, the gate and the slots](https://lockflare.com/docs/lens/identity/): How Vigia knows it is you: an encrypted key on the computer behind a password, Touch ID or Windows Hello, the backup file, the license and the slots.
- [The three pieces](https://lockflare.com/docs/cipher/components/): Three pieces, with a deliberate split of knowledge between them. Each one holds what it needs and nothing more.
- [The console frame](https://lockflare.com/docs/lens/console/): The LockFlare Vigia console: the chairs and the top bar, the map and its groups, colour bands, bastions, tabs and split panes, shortcuts, jobs, the ledger.
- [Understanding a LockFlare server](https://lockflare.com/docs/cipher/server-model/): A LockFlare server is an appliance, not a computer you keep. Treat it as disposable from the day you register it.
- [The terminal](https://lockflare.com/docs/lens/terminal/): The terminal in LockFlare Vigia: logins and the sudo path, resume, tmux keep-alive, recordings, command history, broadcast, snippets and a local shell.
- [Where the build is stored](https://lockflare.com/docs/cipher/editions/): One runtime, one encryption model, one feature set. Accounts differ only in where the encrypted build rests: your engines, or Cipher repositories too.
- [Per-server: the readings](https://lockflare.com/docs/lens/readings/): What LockFlare Vigia reads from a server: the Overview control panel, Monitor with its spike log, About this server, and the pending updates badge.
- [Licensing](https://lockflare.com/docs/cipher/licensing/): Cipher is licensed on request, per deployment, on four axes: servers, cores, seats, environments. What a license does, and how capacity behaves after.
- [Security Setup (twelve tabs)](https://lockflare.com/docs/lens/security-setup/): The Security Setup screens in Vigia: exposure, access, permissions, firewall, Fail2Ban, SSH proven by a fresh login, passwords, WAF, integrity, MAC, kernel.
- [Server requirements](https://lockflare.com/docs/cipher/requirements/): A LockFlare server is an appliance. It should run the Engine and nothing else — no database, no second application, no files that matter.
- [System Setup (ten tabs)](https://lockflare.com/docs/lens/system-setup/): System Setup in LockFlare Vigia: users and groups judged, certificates with a vault, automatic updates, audit, services, storage, network and logs.
- [Installation](https://lockflare.com/docs/cipher/installation/): The whole path, once: install Cipher, create an environment, register a server, install the Engine on it, import a project, push.
- [Tools on every server](https://lockflare.com/docs/lens/tools/): The tools on every server in LockFlare Vigia: tunnels, the HTTP tunnel, a flow run on the box, files with an editor, buckets, backup plans and Themis AI.
- [Migrating an existing app](https://lockflare.com/docs/cipher/migrating/): Most applications deploy unchanged. The ones that need work usually need one adjustment, and it is nearly always the same one.
- [Setup Packages: the software on the box](https://lockflare.com/docs/lens/packages/): The hub is one card per package; a card is built or not, and an unbuilt card is never shown.
- [LockFlare Cipher](https://lockflare.com/docs/cipher/cipher-intro/): Cipher is the desktop app you deploy from. It is also the only piece of LockFlare software that ever reads your source in plaintext.
- [The Databases tool (MariaDB, PostgreSQL, MongoDB)](https://lockflare.com/docs/lens/databases/): The Databases tool in LockFlare Vigia: every tab for MariaDB, PostgreSQL and MongoDB, replication, sharding, cluster backups, Mirror and reports.
- [Signing in](https://lockflare.com/docs/cipher/cipher-signing-in/): Two-factor is required on every account. Which second factor you use is your choice, and you can register more than one.
- [The chairs](https://lockflare.com/docs/lens/chairs/): The chairs in LockFlare Vigia: Terminals only, Overview of the fleet, Actions on the picked servers, Snippets, Flows, and NOC diagrams with proved wires.
- [The home screen](https://lockflare.com/docs/cipher/cipher-home/): The home screen answers one question before you read a word: is anything wrong right now?
- [Themis (the activity)](https://lockflare.com/docs/lens/themis/): Themis in LockFlare Vigia: asking about the picked servers, groups asked about together, and choosing the model she thinks with on your own account.
- [Projects](https://lockflare.com/docs/cipher/cipher-projects/): A project is a folder on your disk plus the settings that describe how to run it. LockFlare serves the build you give it.
- [Files (the activity)](https://lockflare.com/docs/lens/files/): The Files activity in LockFlare Vigia: up to six panes over this computer, any server and every repository, with one copy call between any two.
- [Worker models](https://lockflare.com/docs/cipher/cipher-worker-models/): Every project picks a worker model, and the choice has real consequences. Get it wrong and a scheduled job can run once per core instead of once.
- [Frontend projects](https://lockflare.com/docs/cipher/cipher-frontend/): A static build from any toolchain that emits a folder with an entry document can be deployed on its own.
- [Setup — the things you do to Vigia](https://lockflare.com/docs/lens/setup/): Setup in LockFlare Vigia: the encrypted backup of your account and its file, the password, licenses and slots, notifications and the AI model.
- [Environments](https://lockflare.com/docs/cipher/cipher-environments/): An environment is a deployment target with servers behind it. Development, Staging, Live — or whatever your process calls them.
- [Platform](https://lockflare.com/docs/lens/platform/): LockFlare Vigia on macOS and Windows: one signed app, no server and no account behind it, and every storage and database protocol spoken directly.
- [Servers and licenses](https://lockflare.com/docs/cipher/cipher-servers/): Registering a server issues a license key bound to that machine’s IP address. The Engine uses that key to prove which account it belongs to.
- [Pushing code](https://lockflare.com/docs/cipher/cipher-push/): One action: pack, encrypt, upload, serve. The chain on screen shows each stage as it completes.
- [Comparing environments](https://lockflare.com/docs/cipher/cipher-compare/): Which build is each environment actually running, and is Live what you tested? The Compare pane answers both, and promotes between them without rebuilding.
- [Domains](https://lockflare.com/docs/cipher/cipher-domains/): A domain tells the interpreter which requests belong to which project. Without one, a push has nowhere to land.
- [Environment variables](https://lockflare.com/docs/cipher/cipher-env-vars/): Configuration for your application, held encrypted and injected into the process at start. Nothing is written to a file on the server.
- [Monitoring](https://lockflare.com/docs/cipher/cipher-monitoring/): Live interpreter health across every environment, polled continuously while the window is in front of you.
- [Enclave](https://lockflare.com/docs/cipher/cipher-enclave/): Sealing a server disables every login on it — SSH, console, direct access. After that only LockFlare reaches the machine.
- [Team management](https://lockflare.com/docs/cipher/cipher-users/): Everyone who can sign in to this account, and what each of them can reach. Seats are one of the four licensed axes.
- [Activity log](https://lockflare.com/docs/cipher/cipher-activity/): Every action against the account, attributed and timestamped. Nothing that changes state happens without a record.
- [Node Engine — Installation](https://lockflare.com/docs/cipher/engine-node-install/): The Node Engine runs behind a web server on port 3000. Everything below assumes a fresh Linux x86-64 box with systemd and root access.
- [Node Engine — Configuration](https://lockflare.com/docs/cipher/engine-node-config/): The engine reads its configuration from .env in its install directory. Only LICENSE is required; everything else has a working default.
- [.NET Engine — Installation](https://lockflare.com/docs/cipher/engine-dotnet-install/): The .NET Engine binds port 80 directly — there is no reverse proxy in front of it. It can also terminate TLS itself on 443.
- [.NET Engine — Configuration](https://lockflare.com/docs/cipher/engine-dotnet-config/): The engine reads its configuration from .env in its install directory. Only LICENSE is required.
- [Known limitations](https://lockflare.com/docs/cipher/limits-overview/): Running from memory with no writable application directory rules some things out. This section is the list.
- [Both runtimes](https://lockflare.com/docs/cipher/limits-shared/): What running from memory rules out in both Cipher runtimes, and the shapes of application that need a change before they will deploy.
- [Node.js runtime](https://lockflare.com/docs/cipher/limits-node/): Two constraints are specific to the Node runtime: where packages resolve from, and what happens to your listen() call.
- [.NET runtime](https://lockflare.com/docs/cipher/limits-dotnet/): The .NET runtime carries fewer application-level constraints than Node — dependencies travel inside the artifact.
- [A server will not come online](https://lockflare.com/docs/cipher/trouble-server-offline/): A registered server that never appears online, or drops out later. In practice this is one of four things, and the first is by far the most common.
- [Reading the engine log](https://lockflare.com/docs/cipher/trouble-logs/): The engine log is the first place to look for anything that is not a network problem. Messages are prefixed by scope, and a !! marks a warning or an error.
- [A push fails or does nothing](https://lockflare.com/docs/cipher/trouble-push/): Cipher checks four conditions before it will start a push, and reports which one failed rather than failing generically.
- [A domain is not serving](https://lockflare.com/docs/cipher/trouble-domains/): A domain returning nothing, an error, or somebody else’s project. The interpreter routes by Host header.
- [Certificates and TLS](https://lockflare.com/docs/cipher/trouble-tls/): Certificate problems fall into two groups: the server terminating TLS itself, or something in front of it doing so.
- [An app keeps restarting](https://lockflare.com/docs/cipher/trouble-restarting/): An application that starts, dies and starts again. The engine retries with backoff, so this can run for a long time without anyone noticing.

The full documentation as one file: https://lockflare.com/llms-full.txt