Not combine, but intersect.Not enclose, but project.
A workbench for discovering that all things are one, and projecting them.
Everything is a set.
An item is a set, a list is the intersection of the sets it belongs to, and the tree you see is computed from them — so nothing ever has to be filed in just one place.
- (A)
- Set
- (A, B) = A ∩ B
- Intersection
- (A, B) ⊂ (A)
- Subset · nesting
- x ∈ A ∩ B
- Item
Intersections
An item belongs to as many sets as it needs. Enter your graph from any one of them and the rest of the structure is still intact.
Subsets
Complex ideas emerge from simpler ones intersecting. Depth comes from composition, not from nesting folders inside folders.
Computed views
Views are derived, never stored. Rename, regroup, reshare — there is no migration, because there was nothing to migrate.
Why intersections beat folders.
A note about a Q1 product design meeting
✕ FilingBuried in /Meetings/2026/Q1/ — invisible from the design or product view.
LisctAppears in meetings, design, product and Q1 views automatically.
A task that is urgent, for client-x, and design-related
✕ FilingTags pile up, drift out of sync, and searching becomes guesswork.
LisctQuery 'urgent ∩ design' or 'client-x ∩ urgent' — same task, different views.
Reorganising an entire knowledge base
✕ FilingHours of work, things still break, and you give up halfway.
LisctOld views keep working, new views appear instantly, nothing breaks.
One structure, endless views.
Collaboration that inherits the structure.
Sharing, publishing, AI and the API aren't four bolted-on modules. Each is the same set model, seen from a different side.
Share a set, share its world
Membership is just another intersection: hand someone a set and they receive exactly that subtree — no parallel permission tree to keep in sync.
Publish any branch
The same tree projects into documentation, a blog, or a slide deck. Write once, present three ways.
AI that edits in your voice
Ask an agent to restructure a branch. It proposes real edits, authored as you, which you diff and accept inside your own view.
Open to your agents
An MCP server and a REST API expose the same graph you edit, so scripts and assistants are first-class collaborators.
Free while we're in beta.
There's no pricing page yet because there's no price yet. Here are the actual terms instead.
$0 during beta
Lisct runs on a single self-hosted server and is offered as-is. If paid plans ever arrive, we'll say so well before anything changes for you.
Read the full beta policy- Access
- Invite code required · 1000 seats in total
- Price
- Every feature, free, for the whole beta
- Reliability
- One self-hosted box, provided as-is — expect the occasional outage
- Your data
- Persisted on a best-effort basis; keep your own copy of anything important
- Changes
- Features, quotas and structural limits may still move
Make one set. Intersect it with another.
That is the entire learning curve. The rest is computed.
Invite-only · free during beta · no card