Skip to content

Spiking Labs Lab

Experiments, run in the open.

The Lab is where new tools start. Each one begins with a question, is built in the open and is run with real people. Then it either graduates into a product or is written up and retired.

Bench readout Live
Experiments running
01
Open source
01 / 01
Accounts required
0

01 / On the bench

What we are testing now.

EXP–001 Retrospectives and meetings Since October 2026 Running

Rondel

Question

Can a team run its retros and everyday meetings without accounts, with nothing readable on the server?

Write, group, vote, discuss and agree actions in a retro, or run a meeting with an agenda, timer, shared notes, decisions and action items. Prepare before it starts, and repeat it weekly or monthly from one link. Everything people write is encrypted in the browser with a key that lives only in the meeting link.

Try Rondel Read the source
Report a finding

Setup

Accounts
None. Share a link
Encryption
End to end, in the browser
Server sees
Room ids, sizes, timing
Retention
90 days on the lab server
Licence
Apache-2.0
Self-hosting
Cloudflare, Node, Docker or static files

Stage 3 of 4: Run with people

EXP–002 · Bench free

Have a question worth testing?

Tell us about a problem your team keeps running into. The good ones become the next experiment.

Propose an experiment

02 / Protocol

How an experiment runs.

Every tool in the Lab goes through the same four stages. The bar on each experiment shows where it is.

  1. P–01

    Question

    Every experiment starts with one thing we want to find out, written down before any code.

  2. P–02

    Build in the open

    The source is public from the first release, under an open licence anyone can read and reuse.

  3. P–03

    Run with people

    A working version runs on our lab servers. Anyone can use it, and every finding is welcome.

  4. P–04

    Graduate or retire

    If it earns its place, it becomes a product we look after. If not, we say what we learned and wind it down with notice.

03 / Lab rules

What to expect from a lab tool.

L–01

Expect change

Lab tools move fast. Features can change from one week to the next, and we note what changed in each release.

L–02

Private by design

No accounts unless an experiment truly needs them, no tracking, and as little data on our servers as the tool allows.

L–03

Findings in public

Bugs, ideas and objections go to the experiment's public issue tracker, so everyone can see what was reported and what we did about it.

Tools that graduate move to Products, where we look after them for the long run.