Dev Team Internal

A private server for one engineering team: async standups, sprint rituals, code review, incidents and deploy feeds.

7 categories
40 channels
10 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

TEAM

team-announcements
Team-wide notices from leads: releases, policy, who is joining.
team-chat
The team's main channel. Work talk belongs in Engineering; this is for everything else.
working-agreements
How we work: response-time expectations, review turnaround, meeting rules, on-call norms.
kudos
Thank someone publicly. Name what they did.
whos-out
Holidays, sick days, appointments. One line, dates included.
links-and-docs
Wiki, runbooks, on-call rota, status page, dashboards. Pinned by leads, nothing else posted here.

RITUALS

standup
One message per person per day: done, doing, blocked. Replies in threads.
sprint-planning
Scope, estimates and commitments for the next sprint. The board link lives in #links-and-docs.
retro
One thread per sprint. Tag each post Went well, Needs work or Action item.
demo-day
What shipped this sprint, shown not told. Recordings and screenshots welcome.
decisions
One thread per decision: context, options, choice, consequences. Move the tag when it changes.

ENGINEERING

code-review30s slowmode
Pull requests that need eyes: link, size, urgency. Review on the PR, not here.
architecture
System design, boundaries, the diagram that is out of date again.
backend
Services, APIs, data models and the queue.
frontend
The web app, components, state and the build.
infra-and-data
Infrastructure, databases, pipelines, cost.
qa-and-testing
Test strategy, flaky tests, release sign-off.
tech-debt
One thread per debt item with the cost of leaving it. Tag by size; leads tag Scheduled.
local-setup
Dev environment problems and the fixes that worked.

INCIDENTS

incident-alerts
Monitoring and paging alerts, via webhook. Humans talk in #incidents.
incidents
One thread per incident: severity tag, timeline, who is on it. Mention On-Call once.
on-call-handoff
End-of-shift notes: what fired, what is still open, what to watch.
postmortems
Blameless write-ups, posted by leads and seniors after the incident thread is Resolved.
War Room

FEEDS

deployments
Every deploy to every environment, via webhook.
ci-pipeline
Pipeline results on the main branches, via webhook.
merged-prs
Merged pull requests, via webhook.
error-tracking
New and regressed errors from the error tracker, via webhook.
ticket-updates
Issue tracker changes on the team's board, via webhook.

VOICE

Standup Call
Pairing 1
Pairing 2
Focus
AFK

LEADERSHIP

leads
Engineering manager and tech leads: priorities, staffing, cross-team issues.
hiring
Open roles, pipeline, interview loops and debriefs.
planning-and-budget
Quarterly planning, headcount, tooling spend.
people-topicsHidden from @everyone
Performance, compensation and personal matters. Manager only.
audit-feedHidden from @everyone
Vetox Logs: role, channel and member changes.
Leads Sync

Roles

CTOAdministrator
Engineering ManagerAdministrator
Tech LeadModerator
Senior Engineer
Engineer
On-Call
QA
Product
Design

Overview

An invite-only server for a product engineering team, laid out around the week's rituals rather than around an org chart. Team holds #team-announcements (leads only), #team-chat, #kudos, #whos-out for time off, #working-agreements and a read-only #links-and-docs for the wiki, runbooks and the on-call rota. Rituals gives each ceremony a home: #standup for async daily updates, #sprint-planning, #demo-day, a #retro forum tagged Went well, Needs work and Action item, and a #decisions forum that works as a lightweight decision log with Proposed, Accepted and Superseded tags. Engineering is where the work is discussed: #code-review for pull requests that need eyes, #architecture, discipline channels for backend, frontend, infra-and-data and qa-and-testing, a #tech-debt forum sized Small to Large, and #local-setup. Incidents has its own category with #incident-alerts fed by monitoring, an #incidents forum tagged by severity through to Postmortem, #on-call-handoff and a leads-only #postmortems, next to a War Room voice channel. Feeds collects deployments, CI, merged PRs, error tracking and ticket updates as read-only channels. Leadership is hidden from everyone but the Engineering Manager and Tech Leads, with #people-topics narrowed further to the manager.

When to use it

Your team moved into Discord and recreated one channel per person's whim: standups happen in a thread nobody can find, deploy notifications drown the conversation, and the last incident was coordinated in DMs. This layout separates rituals from work, gives incidents a forum with severity tags and a dedicated voice room, quarantines every webhook into Feeds, and keeps hiring and budget discussions in a leadership category the rest of the team cannot see.

What makes it different

#standup is an async text channel; a scheduled Reminder prompts it so nobody has to remember to.
The #incidents forum tags SEV1 to SEV3 and Mitigated to Postmortem, with a War Room voice room beside it.
#decisions is a forum decision log: one thread per choice, tagged Proposed, Accepted or Superseded.
Deployments, CI, merged PRs, errors and ticket updates are five read-only feed channels, muted in one click.
Leadership is hidden from everyone below Engineering Manager and Tech Lead.

Recommended Vetox setup

Reminders
Schedule a Reminder in #standup at the start of each working day with the three standup questions, and another in #sprint-planning on the last day of each sprint.
Embed Messages
Pin an Embed Message in #links-and-docs with the wiki, runbook, on-call rota and status page links, so the channel is a launcher rather than a scroll.
Self-Roles
Let engineers pick QA, Product and Design as Self-Roles in #team-chat, so a mention reaches the right discipline without a lead maintaining the list.
Logs
Turn on Logs into #audit-feed so role and channel changes on a server that holds internal discussion are recorded, not guessed at.

Questions

How does an async standup work in #standup?

Each person posts one message a day answering what they did, what they will do and what is blocking them, usually prompted by a Reminder at a fixed time. Replies go in a thread on that message so the channel itself stays one line per person per day.

Who declares an incident?

Anyone on the team can open a thread in the #incidents forum and tag a severity. On-Call is a mentionable role, so the opener pings it once; coordination moves to the War Room voice channel and the thread becomes the timeline. Postmortems are written afterwards by a lead in #postmortems.

Can contractors or partners use this server?

Yes, but give them their own role and hide the Leadership category and #postmortems from it explicitly; the template's overwrites assume everyone in the server is on the team.

Common mistakes

Posting deploy and CI webhooks into #team-chat, which is the fastest way to get the whole team to mute the server.
Running incidents in a text channel that also carries the postmortem, so the timeline and the analysis blur into one scroll.
Skipping #working-agreements; a team server without written norms recreates the meeting-culture problems it was meant to fix.

Consider instead

Open-Source Project Hub The codebase is public and outside contributors need a way in.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages