Your data.
Your keys. Your runtime.
lynox is built so you never depend on us to keep operating. Source-available, self-hostable, encrypted-at-rest, with the door wide open. Solo-maintained today by someone who's been shipping operational IT for 15+ years — not a first-time AI founder.
How control stays with you
Five pillars.
Zero lock-in.
Encrypted vault for secrets
API keys, passwords, OAuth tokens live in an AES-256-GCM encrypted vault. lynox never sends raw secrets to the AI provider — only the result of using them.
Encrypted backup snapshots
Daily encrypted snapshots to your own Google Drive. SQLite database + vault + workflows + KG — restore on any machine with one command.
Self-host → Managed migration
Moving from self-host to our managed hosting? Export your full state — DB, vault, settings — as a portable bundle and import on the managed side. Reverse path (managed → self-host) is on the roadmap; for now, contact support and we'll bundle your data.
Self-host vs managed — same engine
The npx-installable Core and our managed hosting run the identical engine binary. No feature gating, no managed-only tricks.
ELv2 source-available license
Read the code. Modify it. Deploy it your way. The only restriction is offering lynox-as-a-service to third parties — everything else is yours. Closer to open-source than closed, honest about not being OSI.
Deployment options
Self-host vs managed.
You decide.
About ELv2
Source-available.
Honest about the licence.
lynox ships under the Elastic License v2 (ELv2). You can read the code, modify it, run it for your own business or your customers, and fork it freely. The one restriction (verbatim from the license): you may not provide the software to third parties as a hosted or managed service where the service provides users with access to any substantial set of the software's features. We call this open-core, not open-source — the official OSI definition rules out commercial protections, so honest labelling matters. Full Q&A on the license FAQ.