LibertyTalk is a passion project born in 2021, rebuilt three times and validated in the field. In 2026 it is the operating system of your community — and still a passion project.
No shortcuts: code, feedback, time.
A community now lives on five, six, eight networks at once. Each one imposes its rules, its algorithm, its moderation, its impossible export. You spend more time juggling tools than energizing people.
We built LibertyTalk to flip that balance of power: one platform that listens to your networks, applies your rules and acts everywhere — without a line of code, without locking your data in.
Taking back control doesn't mean leaving the platforms. It means no longer depending on them.
Not a success story rewritten after the fact: a trajectory, with its detours and what they taught us.
It all starts in a community we run ourselves. The tools are missing, the networks don't talk to each other: we hack together a first bot, then a first dashboard. The need is there; the product isn't yet.
The prototype can't carry the load, nor the ambition. We start over: a real API, a first multi-network vision. Above all, we learn what not to do.
Per-workspace isolation, real-time events, a workflow engine: today's architecture is born here. Meanwhile we pitch to creators, associations, businesses and public bodies — and the same need comes back every time.
The product becomes a platform: cross-network node editor, live overlays, gamification, marketplace, AI. The stack and the team settle. It's the last time we start from scratch.
LibertyTalk runs in production, from the solo streamer to the multi-workspace organization. Clu builds workflows in plain language, LibertyBroad drives the live overlays, the MCP server opens the API. The passion project became a product — without ceasing to be a passion project.
Deep black, neon, lines that light up as you pass: our visual identity comes from Tron. So do two of our names.
In Tron, Clu is the program Flynn wrote to build in his place. Here, Clu reads your request in plain language and assembles the workflow nodes. You keep your hands on every one of them.
The Master Control Program is the platform's administration account — and the name of our MCP server, which lets your agents and third-party tools drive LibertyTalk from outside.
The dashboard speaks the language of the Grid: a black background, light flowing between your networks and the hub, and only one element glowing at a time — the one that matters.
Tron is an inspiration, not an affiliation: the names are a nod, the product is ours.
They survived three rebuilds. They will survive the next feature.
OAuth 2.0, API, inbound and outbound webhooks, MCP server, marketplace: nothing is locked in. What you build on LibertyTalk follows you.
A dedicated database per workspace, EU hosting, a declarative GDPR registry and per-tenant erasure. Your members are not our product.
Trigger → condition → action, visually or in plain language with Clu. A developer's power without needing one — and the API for those who are one.
We don't publish a schedule we couldn't keep. We publish what is shipped, and what is in progress.
The roadmap is discussed in the open, on Discord. Priorities move with your feedback — by design.
Every rebuild started from field feedback. The next improvement probably comes from you.
Roadmap, announcements, mutual help and direct access to the team: it's where everything gets discussed.
A bug, an idea, a use case we hadn't seen? One message is enough — we answer ourselves.
Create your workspace for free, connect a network, run a workflow. Then tell us what got in the way.
Create your workspace in under a minute. Free to start, no credit card.
