LockFlare
  • Home
  • Deep Dive
  • Security
  • AI
  • Pricing
  • Login
  • Contact Sales
  • Community Edition
LockFlare

Lock your code. Flare it to production.

The in-memory application platform where source code is encrypted at rest, decrypted only in RAM, and invisible to everyone — even server operators.

engineering@lockflare.com

Platform

How It Works DevOps Studio Multi-Environment V8 Isolate Runtime File Repositories Version History

Security

AES-256 Encryption Code Protection Threat Immunity 2FA Enforcement Air-Gapped Deploy

AI & IDE

AI Architect Multi-File Context Claude Opus Integration Monaco Editor Live Preview

Company

Pricing Request a Demo Contact Sales lockflare.com Community Edition
© 2026 LockFlare Inc. All rights reserved.
Privacy Policy Terms of Service

{{ legalPanel === 'privacy' ? 'Privacy Policy' : 'Terms of Service' }}

Last updated: April 2026

1. Company Information

LockFlare Inc. is a corporation incorporated in the State of Delaware, United States. This Privacy Policy describes how LockFlare Inc. ("LockFlare," "we," "us," or "our") collects, uses, and protects your personal information when you use our platform and services.

2. Information We Collect

We collect information you provide directly, including your name, email address, company name, and any messages submitted through our contact forms. When you use the LockFlare platform, we collect account credentials, project metadata, and usage analytics.

3. How We Use Your Information

We use your information to provide and maintain the LockFlare platform, respond to your inquiries, send service-related communications, and improve our services. We do not sell your personal information to third parties.

4. Source Code & Data Security

All source code stored on the LockFlare platform is encrypted using AES-256-CBC encryption. Source code is decrypted exclusively in volatile memory (RAM) during execution and is never written to the filesystem. We implement industry-standard security measures to protect your data.

5. Data Retention

We retain your personal information for as long as your account is active or as needed to provide services. Contact form submissions are retained for the purpose of responding to your inquiry and for business records.

6. Your Rights

You may request access to, correction of, or deletion of your personal information by contacting us at engineering@lockflare.com. We will respond to your request within 30 days.

7. Cookies

The LockFlare website uses essential cookies for session management and authentication. We do not use advertising cookies or third-party tracking cookies.

8. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the updated policy on this page with a revised "Last updated" date.

9. Contact

For questions about this Privacy Policy, contact us at engineering@lockflare.com.

Last updated: April 2026

1. Agreement

These Terms of Service ("Terms") constitute a legal agreement between you and LockFlare Inc., a corporation incorporated in the State of Delaware, United States ("LockFlare," "we," "us," or "our"). By accessing or using the LockFlare platform, you agree to be bound by these Terms.

2. Service Description

LockFlare provides an in-memory application development and runtime platform, including the DevOps Studio (IDE), Interpreter (runtime engine), AI code generation tools, file repository integrations, and related services. All source code is stored as AES-256 encrypted documents and executed exclusively in volatile memory.

3. Licensing

The LockFlare platform is licensed on a per-server, per-core, per-seat, and per-environment basis. License terms, pricing, and usage limits are as agreed in your service agreement or as displayed on our pricing page. Cores are pooled across your server fleet and may be distributed as needed.

4. Intellectual Property

You retain all ownership rights to the source code, content, and data you create using the LockFlare platform. LockFlare does not claim any ownership of your code or content. The LockFlare platform, including its software, design, and documentation, is the intellectual property of LockFlare Inc.

5. Source Code Protection

LockFlare encrypts your source code at rest using AES-256-CBC encryption. Code is decrypted exclusively in RAM during execution. While we implement robust security measures, no system is completely immune to all risks. LockFlare is not liable for unauthorized access resulting from factors outside our reasonable control.

6. Data Export

You may export your source code at any time using the platform's export functionality. Exported projects are provided as standalone applications with zero LockFlare dependency. You are never locked in.

7. Acceptable Use

You agree not to use the LockFlare platform for any unlawful purpose, to distribute malware or malicious code, to attempt to gain unauthorized access to our systems, or to interfere with other users' access to the platform.

8. Service Availability

We strive to maintain high availability of the LockFlare platform. However, we do not guarantee uninterrupted access and are not liable for any downtime or service interruptions. Custom SLA terms are available for Enterprise customers.

9. Limitation of Liability

To the maximum extent permitted by law, LockFlare Inc. shall not be liable for any indirect, incidental, special, consequential, or punitive damages, including but not limited to loss of profits, data, or business opportunities, arising from your use of the platform.

10. Termination

Either party may terminate the service agreement with 30 days' written notice. Upon termination, you may export your source code and data. After the termination period, your encrypted data will be permanently deleted from our systems.

11. Governing Law

These Terms are governed by the laws of the State of Delaware, United States, without regard to conflict of law principles. Any disputes shall be resolved in the courts of Delaware.

12. Contact

For questions about these Terms, contact us at engineering@lockflare.com.

Data Sovereignty

What is Self-Hosted Code Storage?
Instead of storing your encrypted source code on LockFlare's MongoDB, you provide a read/write connection to your own MongoDB instance. All source code, environment variables, version history, and project metadata reside on infrastructure you control.

How It Works

You grant LockFlare a MongoDB connection string with read/write access. LockFlare Studio and the Interpreter connect to your database instead of ours. All code is still AES-256 encrypted before it is written — the data in your MongoDB is ciphertext that cannot be read without LockFlare's encryption keys and a valid LockFlare account.

Your database, our encryption. Even your own database administrators cannot read the source code. It is encrypted at the application layer before it reaches MongoDB. Accessing the raw documents reveals only encrypted blobs — no file names, no structure, no logic.

What You Control

Physical location — choose any data center, any region, any jurisdiction. Meet data residency requirements for GDPR, HIPAA, FedRAMP, or any national regulation.

Backup & replication — apply your own backup policies, replication strategies, and disaster recovery procedures to the encrypted data.

Network isolation — place the database inside your VPN, behind your firewall, in an air-gapped environment. LockFlare Studio connects over the network path you define.

Audit & compliance — monitor all database operations with your existing tooling. Every read and write is visible in your MongoDB logs.

What LockFlare Controls

Encryption keys — AES-256-CBC keys are managed by LockFlare. Without our keys and our software, the data is unreadable.

IDE access — all code editing, AI generation, version control, and deployment flows through LockFlare Studio. There is no alternative client.

Interpreter runtime — your servers run the LockFlare Interpreter, which decrypts code from your MongoDB into RAM. No interpreter license, no execution.

When You Need This

Government & Defense
Classified or sensitive applications where data cannot leave sovereign infrastructure. Air-gapped environments with no external network access. FedRAMP, ITAR, and national security compliance.
Healthcare
HIPAA-regulated applications where patient data logic must reside on compliant infrastructure. Hospital systems requiring on-premises code storage with auditable access trails.
Financial Services
Trading platforms, banking systems, and fintech applications subject to SOC 2, PCI DSS, or regional financial regulations requiring data to remain within specific jurisdictions.
SaaS Vendors Deploying On-Prem
You sell software to enterprise clients who demand on-premises deployment. With self-hosted code storage, your client hosts the encrypted database on their servers — but they still cannot read your source code. Close deals you previously walked away from.
Data Residency Requirements
EU organizations subject to GDPR data localization, or any jurisdiction where source code is classified as regulated data that must remain within national borders.

The Bottom Line

Self-hosted code storage gives you complete control over where your encrypted data lives while LockFlare retains complete control over how it is accessed, decrypted, and executed. The data is yours. The tools are ours. The code is invisible to everyone.

Discuss Your Requirements →