Plain answers.
Real ones.
Most facilitator questions have a short, honest answer. The longer ones live on GitHub. If anything below is wrong, file an issue. We treat this page as the source of truth.
Getting started
First session, step by step
Do I need to be a certified LSP facilitator to use BrickThink?
No. Anyone can use it. But this is a method tool, not a blank whiteboard. If you have never been through the five stages, the screen will feel empty. The hosted site is free. The cheapest way to find out is to run one.
How long does it take to set up a session?
Five minutes. Sign up. Make a session. Pick your stages. Paste in your people. Start. Default times are 15, 13, 30, 25, 20 minutes. Change them per stage if you want.
Do people in my room need an account?
Yes — so their stories stick to their name. Magic-link sign-in works fine. No password needed.
Sessions
Running a session live
Do you replace our video tool?
No. Use your own video tool — Meet, Zoom, Teams, whatever. We handle the bricks, the story, and the record. The video call stays where it is.
What if someone loses their connection mid-session?
Their work is safe. When they reconnect, they jump back in where the rest of the room is. You can also pause the stage from the toolbar while you wait.
Can I run a single stage instead of all five?
Yes. Each session is set up stage by stage. Skipping out of order is allowed by the tool — but it breaks the method. That call is yours.
How many people can join a session?
Eight today. Bigger groups are on the way. Eight is also the top end LSP suggests for one facilitator.
Pricing & licence
Free now. Free later. Free forever.
How much does BrickThink cost?
Nothing. The code is open source. The hosted site at www.brickthink.io is free for everyone. No paid tier. No plans for one.
Is there a Pro plan coming?
No. Older copy mentioned a future Pro tier. We dropped it. If we ever change our minds, we will say so loudly — not hide it in a pricing page.
How can I support the project?
Three honest ways. File bugs or pull requests on GitHub. Run sessions and tell other facilitators. Sponsor the repo if your firm wants us to keep going. None of these are needed to use the tool.
Will the LSP method stay openly referenced?
Yes. LSP is open (CC BY-SA 3.0). We keep using it under that licence. Our code stays Apache 2.0.
Accessibility
Built in from day one
How well does this work for people with disabilities?
We aim for WCAG 2.2 AA from day one. The brick canvas works with a keyboard. Every button shows a focus ring. We stop motion if a person asks. Our colours work for colour-blind people, with patterns to back them up.
Does the canvas work with a screen reader?
Yes. Each brick has a name, a spot, and an owner. Like: "2x4 terracotta brick, diagonal hatch, B6, made by Idris." Voice-described build mode is coming — that turns the model into a spoken description.
Can I give someone more time on the timer?
Yes. Each stage has three timer modes: strict, standard, no pressure. You set it per session.
Privacy & security
Where your data lives
Where is my data stored?
In the EU. GDPR rules apply. Session canvases, stories, and exports stay inside your team. They are not shared with anyone else.
Do you use my session data to train AI models?
No. The AI helper only runs on prompts you write. With your consent. We never feed canvas or story content into AI training.
How do I delete a session?
In session settings, pick Delete. The canvas, stories, and exports are gone within 30 days. Backups go too, on the same clock.
How do I report a security issue?
Email security@brickthink.io. We reply within one working day. Please do not open a public GitHub issue for security bugs.
Self-host
Run your own copy
Can I run my own copy of BrickThink?
Yes. The code is open. Clone the repo. Point it at your own Supabase. Run it on Railway, Fly, or any Node host. The README has the steps.
Do I have to keep my copy open source?
No. The licence (Apache 2.0) lets you change and share on your own terms. If your change might help others, please send a pull request.
Is there paid support for self-hosted copies?
No paid support. We are not planning any. GitHub issues are where we answer. If you need hands-on help, write to us. We will point you at someone who knows the code.
Still stuck?
Talk to a human.
We answer support email ourselves. No bot. No outsourcing.