Nothing we make ever phones home.
Not to check a license, not to count your servers or your people, not to report a crash. Vigia talks to your servers and to the AI provider you chose; Sonda talks to your APIs, your store and your own services — and neither one ever talks to LockFlare. Cipher, whose job is to move code, encrypts it on your machine before anything leaves, so its control plane receives ciphertext it has no key to open.
What LockFlare holds about you
Your servers, your store, your providers.
Vigia opens exactly two kinds of connection: SSH to the servers you point it at, with your login, checked by each server's own sshd — and your AI provider, Anthropic, OpenAI or xAI on your key and your bill, or a local model on your own hardware, only when you ask Themis something.
Sonda talks to whatever you send to, and to the team's own services once you configure them: the store, Sonda Server, your SSO provider and directory, your SMTP server, your secret manager at the send, your AI provider. lockflare.com appears in Sonda only as text and links.
Cipher is the exception by design, and says so: its control plane is ours, and all it ever receives is ciphertext.
Every host Sonda can contactWhat "air-gapped" means here.
The word gets used loosely, so here is the version you can check against a packet capture rather than against a marketing claim.
No license check, ever.
Neither app asks us whether you may run it. The free servers and seats need nothing at all; a bought slot or seat is a signed key opened on your own computer, and the signature is the proof. There is no activation server to be down, to throttle you, or to log that you opened the app at 3 am.
No telemetry, no crash reports.
No usage counters, no feature analytics, no crash upload, no "anonymous diagnostics" that turn out not to be. If something breaks, you tell us — or you do not, and we never learn about it.
No update ping.
Neither app polls for a new version or contacts LockFlare; the newest release is always on the download page. There is no list fetched on a button either: even the model Themis thinks with is a name you type, sent unchanged.
No LockFlare account to sign in to.
Vigia's identity is an encrypted key on your computer, behind a password, plus Touch ID or Windows Hello. Sonda seals every file it keeps under a key Argon2id makes from your startup password. Nothing is validated against anything of ours.
Your servers, your store.
Every reading and every change Vigia makes travels over the SSH session you opened. Sonda's team store is a bucket, a folder on a server, a Git remote or a database you already own — or Sonda Server on a box of yours. LockFlare is not in the path and could not read a byte if it were.
Your AI provider, on your key.
The one other connection either app makes is for Themis: to the provider you chose, with your key, on your bill — when you ask her something, or in Sonda when you test the seat or an MCP server you connected asks her model to sample. With a local model, not even that. We are not in that conversation and never see a byte of it.
What we hold, and what we never see.
The complete list for each product — not a summary of it. The keys are kept for one purpose: so they can be sent to you again.
Vigia: an email, and its slot keys.
We hold nothing, for the free servers. Past them: the email of your account and the slot keys issued to it.
We never see your servers — not an address, a hostname, an operating system, a provider or a role, nor whether one runs a database, a website or nothing at all. Your map, groups and notes; SSH credentials, private keys and sudo passwords; the certificate vault; snippets, boards and NOC diagrams; how many boxes you really manage; when you last opened the app.
Sonda: an email, and its seat keys.
We hold, once you take a license, the email of your account and the keys issued to it. The organization id is in the key and means nothing to us.
We never see your requests and what came back; your projects, environments and secrets; the team store and everything in it; who sits on which seat, or any name; what your APIs are, or where they live.
Cipher: the topology, and ciphertext.
We hold the agreement, and the control plane: environments, servers, users, licenses, deployment manifests and the activity log. Your builds as ciphertext, stored exactly as received — or no copy at all, when they rest on your engines or in storage you run.
We never see your source. It is readable only on your machine; everywhere else it is AES-256 ciphertext, which the control plane has no key to open, or briefly in RAM on a server you own.
Payments: a confirmation.
We hold a confirmation that a payment cleared. Then the key is issued.
We never see your card. It is typed into Stripe's form, handled by Stripe, and never touches a LockFlare system.
A license is an artifact, not a check.
A conventional product checks a license server, and that check is a phone-home by definition: it says you are running, from which address, how often, on how many machines. So a license here is a string signed with LockFlare's private key — your account, and the slots or seats you bought — opened with the public half built into the app and verified on your own computer. Nobody is asked, nothing is reported, and it works with the network cable unplugged.
It comes from a web page in your browser rather than from inside the app: one deliberate visit made by you, instead of a permanent channel opened by us. And it never says which: a slot key carries how many servers and until when, a seat key how many licenses — which box or which person ends up on them is decided on your side and known nowhere else.
Beside it, one key, from the page it is issued on to the computer that opens it.
How each product is licensedDo not take our word for it.
Every claim on this page is observable from outside the applications. Five minutes with tools you already have.
Watch the wire.
Run a packet capture on your own machine while you work — unlock, open servers, run jobs, send requests, publish to the team, take a backup. Every connection you see goes to an address you typed or a service you configured, and nothing else.
Block us at the firewall.
Deny lockflare.com and cdn.lockflare.com outright on the computer, then work normally for a day. Nothing degrades, nothing nags, nothing stops. The only thing you lose is the download page.
Unplug the internet.
Keep only your local network, or a VPN to your own boxes. Vigia unlocks, your map opens, your servers connect and every tool works; Sonda opens and its licenses hold — because every signature was verified on your computer, not ours.
Read what is on the box.
After Vigia has managed a server for a month, look for what it left: one folder if you allowed Themis, a named file per tool it configured, and no process of ours. Sonda's team store is plain files: it runs no code and holds no secret, because every document in it is signed by its writer and sealed to its readers.
Ask for the certificate.
Our ISO/IEC 27001:2022 certification and the scope behind it are available on request, and the Statement of Applicability under NDA.
Ask us anything harder.
If a claim here does not hold up to something you tried, we want to know before your security team does. Write to us with "security" in the subject.
Questions people ask.
The ones a security review asks first — and the price of the design, stated plainly.
Does LockFlare software phone home?
No. Vigia opens exactly two kinds of connection: SSH to the servers you point it at, and your own AI provider if you use Themis. Sonda talks only to what you send to and to the services your team configures — the store, Sonda Server, your identity provider, your mail server, your secret manager, your AI provider. Neither one contacts LockFlare: not to check a license, not for telemetry, not for updates.
How can they be licensed if they never phone home?
Because a license check would itself be a phone-home. A license is a signed artifact instead: a string signed by LockFlare's private key, carrying the account and the slots or seats bought. The app opens it with the public half built into it and verifies the signature on your own computer. The free servers and seats need nothing at all; past them, the keys come from a web page in your browser — one deliberate visit rather than a permanent channel.
What data does LockFlare hold about its customers?
For Vigia and Sonda, two things, and only once you take a license: the email address of the account and the keys issued to it, kept so they can be sent again. LockFlare does not know what your servers are, what your APIs are, or who your people are. Card details are not held either; payments go directly to Stripe. Cipher's control plane holds the topology of a deployment — environments, servers, users, licenses — and your builds only as ciphertext, or not at all.
What does zero-knowledge architecture mean at LockFlare?
That LockFlare keeps nothing about a server — not even its address — and nothing about what you build or who builds it. A slot key says how many servers and until when, never which; a seat key says how many licenses, never who. Everything operational lives on your own computers and in storage you own, sealed under keys we never see.
What happens if LockFlare is breached?
For Vigia and Sonda, an attacker would find the license issuer — email addresses and the keys issued to them — and nothing else: no server addresses, no fleet maps, no projects, no stored credentials, no card numbers, and no route into any customer's infrastructure, because that data was never collected. Cipher's control plane would yield ciphertext it has no key to open.
If I lose my computer, can LockFlare recover my data?
LockFlare can send your license and every key again: the license page takes the email of the account, mails a six-digit code to that mailbox, and shows them once the code is typed. It cannot restore your server map, saved logins, certificate vault or snippets, because it has never held a copy. Vigia gives you the protection you control: an encrypted backup written beside the key, and a backup file of it to keep elsewhere, which restores the whole account on any computer under its passphrase. A Sonda team's work lives in its own store, which backs up to a zip, sealed as it was.
Is LockFlare Cipher air-gapped too?
No, and we would rather be exact than borrow a word that does not fit. Cipher's job is to move an application onto servers, so it applies the same principle at a different layer: the source is encrypted with AES-256-GCM on the developer's own machine before anything leaves it, what travels and what is stored is ciphertext, and it is decrypted only into volatile memory on the target server, never written to that disk in the clear. A build can rest on your engines only, in Cipher repositories, or in storage you run.
Who is this not for?
Anyone who wants a "forgot password" button that recovers everything from a cloud account, a web dashboard the team opens from anywhere without carrying anything, or a vendor who can log in and fix the fleet for you. Those are legitimate needs; they are just not what this is.
One email. That is the whole relationship.
Download Vigia or Sonda, put them to work, and check the wire yourself.