Your products
The software you’re building.
Your software.
Your rules.
A home for your products, customer licenses, and encrypted files. Keep control of what you build.
◈
AES-256-GCMSIGNED LICENSESYOUR PROTECTION AT A GLANCE
Workspace overview.
Everything you need to manage access to your software.
◇
Lock it. Keep the key.
Encrypt releases, resources, or any file with a fresh 256-bit key. It all happens in your browser.
Encrypted files are downloads, not runnable executables.Recent licenses
A clear view of your customer access.
ACCESS, ON YOUR TERMS
License management.
Issue keys, manage device limits, and revoke access.
Activated devices
Release a device slot when a customer changes computers.
Existing signed leases expire within one hour. Revocation and device release take effect on the next server refresh.
ENCRYPTION WITHOUT THE UPLOAD
● Client-side encryptionYour private file vault.
AES-256-GCM encryption, directly on your device.
◇
Your files stay yours.
The browser creates an encrypted copy and downloads it. The original file stays untouched.
- Choose your file
- Generate and save an encryption key
- Download your encrypted .vforge file
Keep the key separate from the encrypted file. A lost key cannot be recovered.
License keys and encryption keys serve different purposes. Connect licensing to your application with the .NET client.
CONNECT YOUR APPLICATION
RSA-PSS signaturesMade for your .NET app.
Validate customer access with short-lived, signed activation leases.
1. Choose a product
Product ID
Create a product to get started.
2. Add the client to your project
The SDK source is in sdk/VaultForge.Client. It targets .NET 8 and has no NuGet dependencies.
dotnet add YourApp.csproj reference sdk/VaultForge.Client/VaultForge.Client.csproj
Use a stable per-installation random device ID stored by your app. Keep the signing public key pinned in your application.
3. Pin your server public key
This public key verifies activation responses. Keep the private signing key on the server.
REA MCP
Project-scoped configuration is prepared in .codex/config.toml. REA is a development analysis tool and is separate from your customer-facing app. See docs/REA.md for installation and connection status.
WORKSPACE HISTORY
Activity log.
Recent account, product, license, and device events.