AsyncUp

💬

One-tap standups

A DM card opens one form — yesterday, today, blockers, plus a private mood with an optional comment. Edit until the deadline; the posted card updates in place.

🧵

Tidy date threads

Every answer lands as one card per person under the day's thread. The wrap-up posts the count and exactly who's missing.

🏖️

Away-aware

Skip today with a one-line reason posted to the thread (and undo), vacation mode, personal weeks and days off, and Google Calendar OOO sync — away people are never nagged or counted as missing.

⚠️

Blockers that follow up

Blockers open from answers and can be worked as items — tag teammates, acknowledge, post updates, resolve — with daily nudges and stale-blocker escalation.

📊

Insights built in

Trend charts (participation, mood, blockers), weekly digests, anonymous team-mood mode, CSV export, polls, and signed outbound webhooks.

👥

Rosters that keep up

A People grid for who's on, who's required and which days each person works — or follow a Google Group so joiners and leavers sync themselves.

🖥️

Consoles with SSO

Workspace admins sign into the console; everyone else gets a personal page. Google sign-in or SAML, SCIM provisioning — all in the MIT core.

🤖

MCP for your own assistants

Claude Code and other MCP clients can read standups, answer or skip, work blockers, and nudge the team — scoped tokens, no model inside AsyncUp.

🪶

Lightweight forever

One ~300 MB container on 1 vCPU / 512 MB. Embedded SQLite by default — or bring your own PostgreSQL with one env var.

🔌

Platform-agnostic core

Google Chat today; Slack and Microsoft Teams adapters are next on the roadmap. MIT licensed, never SaaS.

How a morning works

No meeting, no interrogation bot — one card, one form, one thread.

The bot DMs your team

At 09:30 in each person's own timezone, everyone gets a card with a Fill standup button — yesterday pre-filled from their last "today". One gentle reminder before the deadline.

Answers thread up neatly

Each submission posts as a card under the day's thread in your team space. Re-submit to edit in place. Skips, vacations, and calendar OOO show as away — never as missing.

The wrap-up holds the line

At the deadline: who submitted, who didn't, who's away and why, open blockers — plus a weekly digest with trends. Moods stay private, in the web app.

What your team space sees

A real thread from a Wednesday.

📅 Daily Standup — Wed, 11 Jun

😄

Asha

Yesterday

Shipped the payments retry queue

Today

Start on the invoice exports

Blockers

✅ None

😐

Rohit · edited

Yesterday

Auth refactor review rounds

Today

Land it, then pick up the flaky e2e

Blockers

⚠️ Waiting on staging API keys (2d)

📊 Wrap-up · ✅ 7/8 submitted · ❌ Missing: Dev · 🏖️ Away: Mei · ⚠️ 1 open blocker

Why self-host AsyncUp?

Hosted standup bots charge per user per month and hold your team's daily history.

	AsyncUp	Hosted standup bots
Cost	$0 forever — MIT licensed	Per user, per month
Your standup history	In your SQLite file or Postgres	On their servers
AI	None inside; your own assistants connect over MCP with scoped tokens	Their model, their terms
Infrastructure	One small container, scale-to-zero friendly	—
Customization	Questions, schedules, escalation, the web app — and the source code	What the plan allows

AsyncUp

Hosted standup bots

Cost

$0 forever — MIT licensed

Per user, per month

Your standup history

In your SQLite file or Postgres

On their servers

None inside; your own assistants connect over MCP with scoped tokens

Their model, their terms

Infrastructure

One small container, scale-to-zero friendly

—

Customization

Questions, schedules, escalation, the web app — and the source code

What the plan allows

AsyncUpAsync daily standups for Google Chat