What we are building, and why.

A reworked feed is running on our sister deployment and is being prepared for dium.io.

Why it is here: Held back from the September 21 release so it can be finished properly.

Live component status, incident updates and history on status.dium.io, hosted outside Dium.

Why it is here: Today /status/ explains our process; live monitoring comes next.

Keep every time, agenda and "event ended" check correct for people in any time zone.

Why it is here: Six time zone fixes shipped between July and August 2026.

Create, scope and rotate partner API keys yourself instead of asking our team.

Why it is here: Keys are issued by hand today.

Download your Flow's Waves and answers yourself, whenever you want.

Why it is here: Today owners request an export by email.

Get a call to your own system when a Wave is created, answered or solved.

Why it is here: Dium receives profile updates by webhook but does not send events to you yet.

Read Flows you have opened before when you lose signal, and post when you are back.

Why it is here: The storage layer exists in the app but is not switched on.

Pay once a year instead of monthly.

Why it is here: All plans are monthly today.

See earlier versions of an edited reply or message.

Why it is here: Dium records that a message was edited, not what changed.