Answers that do not expire.

Dium turns community questions, AMAs and live sessions into a knowledge base people can search. It is built by TAO.ai.

Our mission

Every community answers the same hard questions over and over, then loses the answers in a chat scroll. Our mission is simple: when someone in your community answers a question well, that answer should be easy to find, for everyone, for as long as it is true.

New here? A Flow is your community space. A Wave is a thread inside it: a question, discussion, AMA or live session. The best answer is the reply the asker marks as the one that worked.

Where Dium comes from

Dium grew out of TAO.ai's community stack. It started as SASQ, a live Q&A tool, and shares its building blocks with its sister products.

Identity

Moat

Your name and avatar come from one Moat profile, shared across TAO.ai products. Update it once and Dium follows.

Sign-in and payments

Werify

Single sign-on for members, and hosted checkout through Werify Paywall. Dium never sees card numbers.

Real time

Echo

Live updates travel through Echo rooms, with polling as a fallback when a connection drops.

Q&A and knowledge

Dium

Flows, Waves, live sessions and best answers. The part that turns questions into a knowledge base.

Because members sign in with the same Moat identity, someone who already uses a TAO.ai product can join a Flow without making a new account.

What we believe

Answers should outlast the chat

A good answer given on a Tuesday should still help someone next year. We design every feature around finding it again.

Say what is true

We publish what Dium does not do yet, next to what it does. No borrowed logos, no certifications we do not hold.

Your community owns its knowledge

The Waves and answers belong to the people who wrote them and the Flow that holds them. We are the place they live, not the owner.

Small changes, often

We would rather ship a real fix this week than a big launch next quarter.

How we build

Dium is made by a small team that ships every week. Most changes are small fixes found by people using Dium at real events and in real cohorts.

  • Plain PHP and one hand-written JavaScript app, with no build step, so a fix goes live as soon as it ships
  • Fixes land in weekly batches, not quarterly releases
  • Every change that affects members goes in the dated changelog

Milestones

  1. Dium gets its own home

    The first commit lands on April 26. A day later the code that ran SASQ, TAO.ai's live Q&A tool, moves to dium.io with its own API paths.

  2. People with context

    The member list starts showing each person's title and city, so you can see who is likely to know the answer.

  3. A support assistant in the app

    Dium gets an in-app support assistant that answers from one shared FAQ, plus embeddable group widgets for partner sites.

  4. Partner events, done properly

    Events that run inside partner sites send members back to the right domain, keep event times in the partner's time zone, and sync sessions and exhibitor booths in place.

  5. Weekly fix batches

    Fixes ship in weekly batches, from direct message tabs to an @mention picker for replies.

Dates come from Dium's commit history.

The team

Template, not live data. Leadership, board, investors and headcount are not published yet. Add real people here: name, role, a one-line bio and a photo, each with that person's consent. Add investors only if the backing is public. If the team prefers not to list people, delete this section instead of leaving it empty.

Team profiles will appear here.

Press

Logos, colours and a short description in the press kit. Or write to [email protected].

Careers

No open roles right now. See how we work, or send a note to [email protected].

Say hello

Questions about Dium or TAO.ai: [email protected], or use the contact page.

Put your community's answers somewhere they last.

Free while you are under 50 members. No credit card. Set up a Flow in a few minutes.