Lolly for Builders

Build a tool once and the request stops coming back to you: the job becomes a template other people fill in themselves, correctly, without you in the loop. Your work is plain HTML, CSS and JavaScript - version-controlled, diffable, reviewable and running on an open engine, so it stays yours with nothing to unwind later.

Lolly is a platform-agnostic engine that runs the same render path across several shells - the web PWA, the desktop and mobile apps, the CLI and the TUI - and tools are data rather than bundled code: a manifest, a template and optional hooks, so a new tool ships without an app update. Pick the lane below that matches what you are here to build.

You are the multiplier in the relay: a creative authors the rules and you scale them into a pipeline, a CLI batch or an MCP endpoint, so The lifecycle of a campaign follows one asset through all three pairs of hands.

New here? The Quickstart gets a brand and your first render in place before you go deep. About states the licence boundary and the repositories each piece lives in, and Lolly for Operators is the door for whoever will ask you about rollout and security.

Designers

Bring finished work in, set the rules once and keep the tools you already use. What you decide here is what every tool in the gallery obeys, so a colour or a typeface is fixed in one place rather than argued about per asset.

• Import a design - bring a .fig, .penpot, .ai, .idml or SVG file in as an editable, re-renderable tool rather than a flat picture.
• The Brand Studio - the on-device editor for logos, colours, type and the rest of the design system (#/start).
• Design Tokens - the DTCG token model a brand is expressed in and how a tool reads it at render time.
• Authoring Assets - catalog assets, tiers, locales, palettes, themable icons and fonts.
• The Dashboard - your design system shown read-only, plus the capability map for the device in front of you.

Developers

One render path behind every surface: the GUI, the CLI and an agent all produce the same file from the same inputs. A tool is a manifest, a template and optional hooks, and every input is expressible as a URL parameter, which is why a link and a command line are the same thing here.

• Architecture - why Lolly exists, the engine/shell/tool separation and the commitments that hold it together.
• Authoring Tools - the full guide: manifest, template, styles, hooks, composition and publishing.
• Host API - the HostV1 capability bridge every tool is written against, plus the note that hooks are not a sandbox.
• URL Mode - every input as a URL parameter: reserved params, compact encoding and packed links.
• Constraints - why output comes out right by construction, with the tests that enforce each rule.
• Determinism - same inputs, same file: what is byte-reproducible and what is not.
• Reproducibility - the URL as the artifact, and how far a bare link can carry.
• CLI - headless rendering over the same path as the GUI, driven by --foo=bar argv pairs.
• Signing from the terminal - give CLI output a real signing identity instead of an anonymous on-device key.
• TUI - the interactive terminal shell, for when a pipeline needs a human in it.
• MCP Server - the native endpoint an AI agent uses to discover and run tools.
• AI Agents - driving Lolly from a model, where a URL is the API.
• Browser Extension - capture a live URL as a reusable asset for a tool to compose.
• Content Credentials Identity - CA-issued signing for on-device C2PA, with the engine contracts behind what an export carries.

Infrastructure

For standalone use, deploy static files or a prepared air-gapped app; local rendering needs no server. For organisation identity, policy and shared work, add lolly.work, the Lolly project's separately deployed service. It also offers persistent render jobs and batches for automation.

• Deployment - the web app, packaged apps, optional integrations and lolly.work: where each piece runs.
• Organisation automation - use lolly.work's lw client and authenticated API for queued renders, batches and governed delivery.

• Configuration - profiles, brand packs, capability gating, feature flags and catalog validation.
• Build Guide - build every target: CLI, TUI, desktop, mobile and the web PWA.
• Building for iOS - the extra gates Apple adds, and what a device build needs on top of the desktop one.
• Contributing Setup - a development checkout sized to what you are here to do, from a slim clone upward.
• Data Transfer - the lolly-backup bundle: envelope, integrity and the cross-shell guarantees.
• Threat Model & Trust Boundaries - what Lolly defends against, what it does not and where each boundary falls, before a review asks.