Skip to content
A darkened corporate meeting space with a single warm lamp, set up and empty before an all-hands.

Town halls · all-hands · onboarding

Ask two thousand colleagues something, and get an answer you can believe.

An anonymous pulse check is only worth running if the anonymity is real. Here it is a storage decision rather than a display one. The rest of the room's machinery is the same engine that runs a keynote.

  • Anonymous by storage
  • Single sign-on, no tier
  • Longitudinal pulse
  • 5,000 in one room

The claim that is usually a lie

Anonymous mode changes what is written, not what is shown.

A per-session switch. Turning it on is not a filter over a table that still has names in it: the names are never written, and several rows are never created at all.

A stream of identical lit forms breaking into unlinked particles before they reach a sealed dark vault, so nothing that goes in still carries its shape.

No name on the answer

The per-question rows are stored with the player name null, and they are shuffled before insert so that row order cannot reconstruct who answered when.

A row of recesses cut into a metal plate, each holding a lit mark except one, which sits dark and empty.

No leaderboard row, no participant record

An anonymous session writes no final standing and creates no event participant. The identity is not resolved and then discarded; it is dropped at the door.

A bright line across the dark: below it a handful of motes are held still and dim, above it a large crowd of them moves freely.

Small groups stay unpublished

Means, distributions and net promoter scores are withheld below five respondents. A headcount is still shown, because knowing that only three people answered is not the same as knowing what they said.

A drift of separate points of light losing its individuals into one smooth unbroken curve.

Only the average timing leaves

Response timings are a quasi-identifier in a small room, so an anonymous session exposes their mean and nothing per-response.

5,000in one room

Measured on one node against the real server over real sockets: 5,000 of 5,000 players joined with zero failures, every one received the question inside a 34ms window, and every answer was counted with the exact expected split. The same room was killed outright with a SIGKILL and came back with all 5,000 players in under two seconds.

What IT asks about

Single sign-on is configuration, not a sales call.

OpenID Connect, on any deployment, at no tier. The market leader keeps SSO, along with the reporting API and provisioning, behind its enterprise tier.

A single tall arched gateway in a dark hall, its threshold lit gold and a blank seal glowing on the keystone, with one clean beam passing through.

OIDC, properly

PKCE, nonce and state, ID-token signature verification against the provider's JWKS, and a domain allowlist for who may sign in at all.

A warm gold hub on a dark floor with a handful of cool-lit panels held close around it, and nothing at all connecting it to anything beyond.

Run it on your own network

A laptop can host a room over the local network with no internet at all, which is the answer for a site with no guest wifi and for a venue whose uplink you do not trust.

A dark, unlit machine with a single cable entering it from outside the frame, carrying gold light inward.

AI on your own provider key

There is no BamzIQ model and no BamzIQ key. You connect your own Anthropic, OpenAI or OpenRouter account, each feature is opted into separately, and there is no markup because there is nothing to mark up.

Two tokens side by side: one an empty ring of cool light, the other solid metal carrying a struck gold seal.

Attendees can be verified, not just claimed

Signing in through your directory is the only path that marks an identity verified, and the report distinguishes the two rather than flattening them.

The same pulse question, quarter after quarter.

A one-off pulse check is a slide. The same question across four town halls, plotted, is the thing somebody makes a decision from.

Dozens of fine threads entering from one side and converging into a single wide ribbon of gold light.

After the meeting

One report for the event, not twelve for twelve sessions.

  • Attendance, engagement and sentiment across the whole run of show.
  • Per-attendee participation: how many sessions, how many responses, and the point at which somebody stopped.
  • Per-option distributions rather than a percentage correct. Everybody converging on one wrong answer is a shared belief worth naming; spread evenly is guessing.
  • The chosen answer is recorded as a fact rather than inferred, which is what makes the distribution possible at all.
  • CSV at any size, on every plan, with no row limit past which the export degrades into raw data.

Stated plainly

What is not built.

On the same page as everything that is, because a gap somebody finds after the demo costs more than the gap itself.

  • SCIM provisioning and domain claimBamzIQ provisions on first sign-in instead. SCIM earns its place at a headcount where nobody hand-invites.
  • Slack, Teams and calendar integrationNo async pulse into a channel, and sessions do not land in attendees' calendars yet.
  • A configurable retention windowDeletion is manual today. What is kept and how to have it removed is set out on the privacy page.

Commercial use, every plan

Internal comms is commercial use, and that is fine here.

Product launches, recruitment events, client work and all-hands are permitted on the free plan and on every pass, with no cap on how long a session runs. No payment is taken yet; a purchase is recorded and settled by invoice.