Standly
Standup questions in a private chat. One digest in the channel.
Standly asks each teammate at their own local time, reminds once, and posts the day's answers to your channel with blockers flagged. Built for Teams and Azure DevOps.
Coming to the Microsoft Teams store.
How a standup day runs
An example for a team that sends the questions at 09:00 and posts the digest at 17:00. Every value here is a setting on the standup.
-
Lisbon
The questions arrive in a private chat from Standly: What did you do? What will you do? Any blockers? Type the answers on the card and press Submit, or press Snooze 2h to get it again later.
-
Singapore
Same questions, same clock time. Standly works out each person's send time in advance, with daylight saving handled, so nobody's standup lands in the middle of their night.
-
Reminder delay: 60 min
Anyone who has not answered gets one reminder with two buttons: Fill it in now, and Snooze 2h. That is the only reminder.
-
Team timezone
Standly posts one message to the channel: each person's answers under their name, blockers highlighted, and a final line, Waiting on, with the names of anyone who did not answer.
The scheduler runs every five minutes, so a prompt set for 09:00 can arrive at 09:04.
What you get on every plan
Local-time prompts
Each participant gets the questions in a private chat at their own send time. Standly does the timezone and DST math ahead of time, so a 9:00 standup is 9:00 in Lisbon and 9:00 in Singapore. On first contact the bot asks each person to confirm their timezone with one tap.
One reminder, one snooze
Non-responders get a single nudge after a delay you choose. Everyone can push a prompt back two hours. Nobody gets spammed.
A digest people actually read
One channel message per run: answers grouped by person, blockers highlighted, and the names of anyone who did not answer.
Configure it in a tab
Standups, participants from the channel roster, schedule, questions and history live in a Teams tab, not in a chat command. A personal tab lists the standups you are in.
Ordinary Teams messages
The prompt and the digest are normal Teams messages, so they work in Teams on desktop, on the web and on mobile. There is nothing extra to install on a phone.
As many standups as you need
Each standup belongs to one channel and has its own participants, schedule, send and digest times, reminder delay and questions. The defaults are What did you do? What will you do? Any blockers?
History in the tab
Every run's answers are kept per standup: the last 30 days on Free, the full history on Core and Premium.
A clean uninstall
Removing Standly from a team stops every prompt and digest for that team and deletes its data.
For teams on Azure DevOps
On the Premium plan, a standup can be linked to an Azure DevOps organization, and optionally a project, with a personal access token. Standly verifies the token against Azure DevOps before saving it and stores it encrypted. An optional WIQL query narrows which work items count. Teams that do not use Azure DevOps never see any of this.
Pre-fill
What did you do? arrives already drafted from the work items you changed and the pull requests you authored since your last standup. Edit it or send it as is.
Write-back
Mention AB#1234 or #1234 in an answer and the note lands on that work item as a comment after the digest. Optionally the digest is also saved to an Azure DevOps wiki page.
Digest summary
Two to four factual sentences at the top of each digest naming the shared themes and the blockers.
Participation analytics
Per standup and per person over the last 14 days: runs, answers expected against answers received, and the response rate.
Compared with Slack-first tools
Geekbot, DailyBot and Standuply started on Slack and Jira. Standly started on Teams and Azure DevOps.
| Geekbot, DailyBot, Standuply | Standly | |
|---|---|---|
| Home platform | Slack, with a Teams port | Built on Teams: Bot Framework and Adaptive Cards |
| Dev tool integration | Jira first | Azure DevOps first: pre-fill and write-back |
| Timezones | Per user | Per user, DST-correct, confirmed on first contact |
What Standly stores
- Your Microsoft 365 tenant id and user object id, display name and email, timezone, standup responses, Teams conversation references, and Azure DevOps credentials if you connect them.
- Conversation references and Azure DevOps tokens are encrypted at rest with AES-256-GCM and decrypted only in memory when needed.
- Standly asks for delegated Microsoft permissions only: User.Read and offline_access. The channel roster comes from the Teams bot API, so no directory permission is requested.
- Sub-processors: Vercel for hosting and the scheduler, Neon for Postgres, and Microsoft for Teams and the Bot Framework. Azure DevOps is contacted only for teams that connect it.
- No advertising use and no selling of data. Uninstalling from a team removes that team's data. For earlier deletion, email support@standly.io.
The full text is in the privacy policy.
Questions
Does it work on mobile?
Yes. The prompt and the digest are normal Teams messages, so they work in Teams desktop, web and mobile.
Does my admin need to approve it?
Standly asks only for delegated permissions (User.Read and offline_access). Depending on your tenant's settings, an admin may need to consent on first use.
What happens when we uninstall it?
All prompts and digests stop and the team's data is removed. Email support@standly.io for earlier deletion.
What counts as an active participant?
One distinct person across all your standups. The same person in three standups counts once.
How much history do you keep?
Free shows the last 30 days per standup in the tab. Core and Premium keep the full history.
Can non-developers use it?
Yes. The Azure DevOps features only appear when a standup is connected to Azure DevOps.
Do you support Jira, GitHub or Slack?
Not today. GitHub is the first planned addition.
How do I get it?
Standly is coming to the Microsoft Teams store. Until then, email us for early access and we will reply within two business days.
Get early access
Send a short note with your team's name and roughly how many people would take part. We reply within two business days.
Free for up to 10 active participants. Planned pricing.