Lolly Work
⚠️
Public testing sandbox. Sign-in is passwordless: anyone can enter as any persona, including admin. State is in-memory and resets on redeploy. Do not put anything real or sensitive here.

Lolly Work — Demo

Lolly helps people make files on their own devices. Lolly Work adds your organisation’s sign-in, approved tools, rules and shared services. This sandbox lets you explore them with demo data.

Explore Lolly Work

Explore the architecture ↓ Read the docs Open the admin console View on GitHub ↗

Read the setup and operator guides without signing in.

Security and platform

See where the work happens.

Read the full guide →
Choose a workflow

Use tools already on your device. Your inputs and export stay local.

Follow the work, step by step

Your organisation Lolly Work

Not needed for this workflow

Tools already on the device

Your device Lolly

Choose a component to learn what it does.

Tools and engine

Lolly takes the tool, inputs and assets, then uses the app’s capabilities to make the output.

Choose a perspective

A local render can avoid uploading working content. Catalog signatures check tool-file integrity; Content Credentials record the output’s provenance.

Limits

A signed tool still needs review. The engine is not a universal WASM sandbox, and a signature does not prove that content is true.

More detail →

Sign in as a demo persona

One click, no password. Each persona opens the same console with different governance applied, so pick two and compare what they can see and change.

Admin Ada (Admin) admin@suse.example Manages access, tool rules, approvals and usage reporting. groups: admin Brand team Bruno (Brand lead) brand@suse.example Manages brand inputs and reviews work awaiting approval. groups: brand-team, approver Marketing Mira (Marketer) marketer@suse.example Uses approved tools and requests approval when needed. groups: marketing Contractor Cveta (Contractor) contractor@suse.example Sees the tools and actions available to a contractor. groups: contractors

What the control plane does

Choose the controls and services your teams need:

Approved tools

Give each team access to the tools and assets it needs. Control who can change the catalog.

Rules for inputs

Lock an input to a brand value, offer a fixed set of choices, or hide it. The server checks these rules before it renders.

Review and approval

Set up review steps and decide who can approve work. Review the approval guide for the enforcement available in your workflow.

Records you can inspect

Record governed actions in a tamper-evident audit log. Choose what usage labels are collected and whether they identify people.

Your identity and infrastructure

Connect your identity provider, manage roles and permissions, and run Work on infrastructure your organisation operates.

Open source

Lolly and Lolly Work use the MPL-2.0 licence. Read the code, host the service, and follow the documented paths to move your data.