No trial key or account is required. Each edition is available as a complete download, with no expiry or licence-server connection.
Start with CORE for a small application. Evaluation needs no account. Follow the first-app walkthrough, or see CORE source and local-model availability.
A licence is due within 30 days of your first production deployment. Evaluation, development, testing and staging do not require payment or registration.
Each download is a self-installing archive: it verifies its own
payload, places the engine where your builds can find it, puts the
lounge command on your PATH and runs an environment check. It
carries the toolchain too — the CLI, the agent skill and the Lounge UI.
Requires JDK 25 and, for the bundled database, Docker.
Development use is free and is not time-limited.
You may build, test, benchmark, demonstrate and stage on any number of machines, with every PRO capability enabled, without a key or registration. A licence is required for production use and must be purchased within 30 days of the first production deployment.
sh lounge-core-1.0.5.run # installs the engine and the CLI lounge install ~/work/my-app "MyApp" # scaffolds and builds a real app cd ~/work/my-app && lounge dev # hot-reload development loop
From there, lounge build validates the schema, runs
strict lint and executes the tests. lounge deploy asks a short
list of questions about the application and writes its deployment files. The
full verb reference ships inside the archive and lives in
the wiki.
A coding assistant can produce the application description and
its handlers using the reference material included in the archive. Its work
remains subject to lounge build, which checks the schema, strict
lint rules and tests before the application is accepted.
1 · Give your assistant the skill. It ships inside the
archive as tools/lounge/ — a skill file plus the reference
material behind it. Install it for your assistant (create the parent directory first):
mkdir -p ~/.claude/skills ln -s ~/.lounge/current/tools/lounge ~/.claude/skills/lounge # Codex mkdir -p ~/.codex/skills ln -s ~/.lounge/current/tools/lounge ~/.codex/skills/lounge
Any other harness: point it at
~/.lounge/current/tools/lounge/SKILL.md and let it read the
references/ beside it.
2 · Point it at the installation. Everything it needs
to read — the skill, the guides, the full CLI reference — is under one
directory, and ~/.lounge/current always points at the version
you last installed:
~/.lounge/current/tools/lounge/ the skill and its references ~/.lounge/current/docs/guide/ the guides, incl. agent-onboarding.md ~/.lounge/current/docs/wiki/ the long-form documentation
Start it with docs/guide/agent-onboarding.md —
it is written for an assistant arriving cold, and says what to read, in what
order, and which mistakes to avoid.
3 · Ask for the application. Describe it in your own
words — the events that arrive, what should happen to them, what to
remember, what to answer. The assistant scaffolds with
lounge install, writes project.yaml and the
handlers beside it, and iterates against lounge build until
the tree is valid. Review the resulting project.yaml together
with the handler code it references.
4 · Run and manage the application. The CLI and Lounge UI expose the same lifecycle operations:
lounge dev # hot-reload development loop lounge build # clean rebuild, schema validation, strict lint, tests lounge deploy # answers a few questions, writes the deployment lounge run / stop # start and stop what deploy generated lounge heartbeat # is it alive? edition, pipeline, in one line
The Lounge UI presents those verbs as controls beside a generated map of the application, its record types and its queries. Install its dependencies once per machine:
cd ~/.lounge/current/tools/ui && npm install APPTREE_PROJECT_ROOT=~/work/my-app npm run dev # then open the address it prints
The UI canvas can add and connect nodes, then write the
changes back to project.yaml while preserving comments. It runs
locally and does not transmit the project content to LoungeTech.
The same project file runs as core, pro or cluster; editions use the same description vocabulary and query semantics while exposing different operational capabilities. Every download below includes the selected edition's complete capability set. The listed price applies when that edition is used in production.
single-node production
single-node parallelism and durability
multi-node deployment and independent subtree sizing
These are introductory prices. Future price changes apply only to later purchases. Existing perpetual licences are not repriced, and the purchase includes 12 months of updates.
CLUSTER and multi-node purchases can be invoiced directly. Contact us for an invoice payable by transfer with the applicable VAT treatment.
Every archive carries its own payload checksum and refuses to extract if it does not match. This detects corruption in transit. To verify the publisher as well, check the signature on the checksum file:
curl -LO https://github.com/lounge-labs/lounge-dist/releases/download/v1.0.5/SHA256SUMS curl -LO https://github.com/lounge-labs/lounge-dist/releases/download/v1.0.5/SHA256SUMS.asc curl -sSL https://lounge.tech/lounge-signing-key.asc | gpg --import gpg --verify SHA256SUMS.asc SHA256SUMS # verify the LoungeTech signature shasum -a 256 -c SHA256SUMS # verify the downloaded files
Recent GnuPG versions can fetch the key directly from this domain through Web Key Directory:
gpg --locate-keys paul@lounge.tech
The signing key's fingerprint is
CC88 D45F 14FE F07C 0635 C8D0 D882 1C4A 7283 892C, and the same
fingerprint is printed in the release repository's README. A copy that
disagrees with both is not ours.
Download, build, test, benchmark, demonstrate and stage without a licence or registration. The obligation begins with the first production deployment; the corresponding licence is due within 30 days.
A licence is perpetual and per instance — the version you buy remains licensed for continued use, with 12 months of updates included. The installed version does not expire or require a licence-server connection, and it continues to run after the update window ends. The engine does not check a key; the edition is selected by configuration, while the licence grants the corresponding production use.
Need longer than 30 days, or a different arrangement? Contact us to discuss it.