About
Who builds Keylane
You are being asked to trust a messenger with your conversations. The least we can do is be specific about who is asking.
Livotov Labs Ltd.
Keylane is built by Livotov Labs Ltd., an independent software company registered in Varna, Bulgaria. We are a small team that has been building software for a long time, and Keylane is the product we wanted to exist and could not find.
The company is entirely self-funded. There is no venture capital behind Keylane, no outside investors, no accelerator and no grant — the work is paid for out of our own revenue. We do intend to apply for public-interest, non-dilutive grants for the open-source parts of the work; if one is accepted, it will be disclosed here and on the pricing & funding page. That makes progress slower than it would otherwise be, and it means no one can require us to monetize the people who use it.
Being registered in Bulgaria places us under EU law, including the GDPR. That is a genuine benefit, though a smaller one than it sounds: the strongest protection is not which courts we answer to, but that the architecture leaves almost nothing for a court to reach.
- Legal entity
- Livotov Labs Ltd.
- Company ID
- 202346120
- EU VAT
- BG202346120
- Registered address
- P.O. Box 99
Varna 9002
Bulgaria - Funding
- Self-funded
Why we built it
Encrypted messaging is largely a solved problem. What is not solved is everything around the encryption: the phone number that ties an identity to a person, the database that records who spoke to whom, the single company that can be bought, subpoenaed, or persuaded to change its mind.
Existing options each solve part of this. Signal removed the ability to read your messages but kept the phone number and a central network. Matrix removed the central network but kept substantial server-side metadata. Our comparison page goes through this properly, including where those projects are ahead of us.
Keylane is an attempt at the combination: no identifier to collect, no sender records to seize, no operator you are locked into, and post-quantum key exchange from the first release rather than retrofitted later.
How we work
Bounded claims only
We do not say “unhackable” or “military-grade”. We say what the system does and what it does not, and we publish a threat model that lists the failures.
Document before announcing
The protocol was written up before the product was promoted. The whitepaper exists so the claims can be checked.
Say when something is not ready
Self-hosting is unfinished, the audit is not done, and the client source is not fully published. All three are stated plainly wherever they are relevant.
No tracking, anywhere
Not in the app, not on this website. This page loaded without a single third-party request, cookie, or analytics call.
Contact
General
Support
Security
Press and brand
Logo files, product screenshots, and the rules for using the Keylane name are on the brand page. For interviews or questions about the protocol, write to us.