Repository navigation
Releases: arnaud-ritti/skrum
Release list
Skrüm 0.0.1: first release
Skrüm 0.0.1: first release
Skrüm is an open-source, self-hostable place for a team's rituals: retrospectives, planning poker, whiteboards, surveys and games, in realtime. Workspaces contain teams, teams run sessions, and guests join a session through a link. It is available in English, French, Spanish and German.
Highlights
- Retrospectives: realtime boards from templates, anonymous cards, grouping, votes, discussion, a return-on-time-invested (ROTI) poll, and a summary you can share. Templates can be personal, team or workspace-wide.
- Action items: an owner, a due date, reminders and recurrence, tracked across retros, with export and sync to Jira, Linear and GitHub.
- Planning poker: Fibonacci, modified Fibonacci, T-shirt sizes, powers of 2 or a custom deck; anonymous rounds; tasks imported from an issue tracker; estimate history.
- Whiteboards: a shared canvas for the whole team, with templates and export.
- Surveys: health check, team pulse, eNPS and quick questions, with results and trends.
- Games: Draw and guess, Sprint GIF, Hangman, Decoded, Two truths and a lie, Mood weather and Guess who, to open a session.
- Insights: team pulse on the home page, mood and health trends, ROTI per retro, team activity.
Integrations
Slack, Telegram, Microsoft Teams, Mattermost, Jira (Cloud and Data Center), Linear, GitHub and signed outgoing webhooks, with a documented event reference.
AI assistants
A built-in Model Context Protocol server lets an assistant read and update retrospectives, action items and planning poker, limited to the scopes you grant to a key.
Accounts and sign-in
Password, passkeys and two-factor authentication. Single sign-on with Google, GitHub, Microsoft Entra or any OpenID Connect provider, which can be made required. Personal API tokens, workspace and team roles, and guests.
Administration
Sign-up control (invitation only, open, or allowed domains), branding (name, logos, colour, corners, avatars, GIF provider), mail (SMTP), integration apps, accounts and instance admins, MCP keys, an audit log, and a licence and update-check page.
Self-hosting
- One container for the web server, websockets, queue and scheduler, with a built-in Caddy.
- PostgreSQL, MariaDB, MySQL or SQLite.
- Image:
ghcr.io/arnaud-ritti/skrum:0.0.1, with a ready-to-usecompose.production.yaml. - Migrations run when the container starts. A maintenance page is shown during
artisan down. - The admin footer shows the running version, and an optional daily check tells you when a newer release exists.
Before you start
- The first account to sign up becomes the instance admin. Create it right after starting the instance, and consider
SKRUM_SIGNUP_MODEto control who can sign up afterwards. - Fill
APP_URL,APP_KEYandDB_PASSWORDin.env; everything else has a working default. - Back up the database and the
app-storagevolume before every upgrade, and pinSKRUM_IMAGEto a version tag rather thanlatest.
Licence
AGPL-3.0-or-later. Every feature is included, with no account limit, no key and no expiry.
Documentation: https://arnaud-ritti.github.io/skrum/docs/