Stride
Die Arbeitsplattform, auf der Teams Aufgaben, Fehler und Releases an einem Ort steuern: Boards, Sprints, Berichte und ein externes Anfrageformular.
The shared memory of a team
Stride is a work platform that keeps what a team does, what breaks and what it has promised to ship in a single place. Wherever a request comes from — a customer, someone inside the team, or a form you opened to the outside — it turns into the same thing: a work item with an owner, a priority, a state and a history.
The product came out of our own need. For a team building dozens of products at once, the questions 'who is working on what, which bug is waiting on whom, what ships in this release' get asked every single day; when the answers are scattered across chat windows, they are stored nowhere. Stride was written to bind those three questions to a durable record — and then a product came out of the product.
- Multi-project: every project has its own key, team and workflow
- Real-time: the board and notifications refresh by themselves
- Two deployment models: cloud subscription or your own servers
- Audit trail: every field change is recorded with who and when
The screens a work item passes through
You ask the same record different questions: what do I do today, how full is this sprint, what ships in this release, what happened last week. Each screen answers one of those questions — all of them running on the same data.
Dashboards
You assemble your own dashboard from gadgets: distribution, weekly trend, workload, overdue items.
Board (kanban)
Drag-and-drop columns, swimlanes and a per-column work limit; a moved card changes place for everyone at once.
Backlog & sprint
Upcoming work waits in a pool, a sprint is started and closed; the point total is visible while you plan.
List & filters
A server-side filtered table, saved and shareable filters, CSV export and import.
Timeline & calendar
Items with start and due dates on a timeline, deadlines in a month view.
Roadmap & releases
A monthly roadmap of epic bars; a release card showing how much is left, as a percentage.
Reports
Sprint burndown and velocity charts; project comparison at portfolio level.
External request form
Someone without an account fills in a form from a link; the request becomes a work item directly.
The heart of the flow
The work item and the workflow
A record can be a bug, a task, a user story, an epic or a sub-task; it lives with priority, assignee, reporter, estimate and point fields. The names and order of the states belong to you: each project defines its own workflow and declares which state is the start and which counts as done.
- Per-project customizable workflow
- Epic → item → sub-task hierarchy
- Links between items: blocks / relates to
Planning and forecasting
Items move from the backlog into sprints, the sprint starts, and finished work is separated at closing. As points accumulate, two charts start to mean something: the burndown that shows how the remaining work melts inside a sprint, and the velocity chart that shows how much the team actually finishes per sprint. The next sprint gets filled from measured pace, not from a guess.
- Start / close sprint, carried-over work returns to the backlog
- Burndown and velocity charts
- Per-column work limits (WIP) make congestion visible
Collaboration and the trail
The discussion lives under the item itself: rich-text comments, mentions, emoji reactions, tick-off checklists and logged time. Whoever changed a field lands in the activity history — the answer to 'why is this waiting' is still in the record six months later. Everyone watching the item hears about the change.
- Comments, mentions, emoji reactions, checklists
- Field-level activity and audit history
- Time logging and watcher notifications
Visibility and permissions
Every project has its own members and roles: admin, member, viewer. Teams cross project boundaries; a person can belong to several. As for search, you can type an item key and jump straight to the record, or filter across all projects, save the result and share it with the team.
- Per-project roles plus system-level permission management
- Saved and shareable filters
- Keyboard shortcuts and quick search
The capability catalogue
- Bug / Task / Story / Epic / Sub-task
- Four priority levels
- Per-project workflow
- Work item templates
- Item links
- Checklists
- Labels
- Bulk update
- Backlog
- Start / close sprint
- Story points and estimates
- Work log
- Components
- Releases
- Roadmap
- Due date reminders
- Drag-and-drop kanban
- Swimlanes
- Column work limits (WIP)
- List view
- Calendar view
- Timeline
- Summary screen
- Starred projects
- Rich-text comments
- Mentions (@)
- Emoji reactions
- Watching items
- Activity history
- Teams
- File attachments · soon
- In-app notification centre
- Live connection, instant updates
- Email notifications (optional)
- Mark read / mark all read
- Search across all projects
- Jump by item key
- Saved filters
- Filter sharing
- CSV export
- CSV import
- Project roles: admin / member / viewer
- Role and permission management
- Menu and screen permissions
- Single sign-on (SSO)
- Personal settings and theme
- Public request form (no account)
- Form field designer
- Default assignee for incoming requests
- Spam protection and rate limiting
- Webhooks / external integrations · soon
- Sprint burndown
- Velocity chart
- Project statistics
- Portfolio comparison
- Workload distribution
- Overdue items
Two deployment models, one product
You can use Stride in the cloud on a subscription: installation, backups, upgrades and monitoring stay with us, and you start working the day you sign up. As the team grows, more projects, users and records create no maintenance work on your side.
The second model is the product installed on your own servers. Where data must not leave the institution — public sector, defence, finance, and organisations running their own data centre — the same product lives inside your network, on your database. These are not two different editions; it is the same core in a different place.
Authentication in both models goes through our central sign-on service: no password is stored in Stride, the session token lives server-side and can be revoked. In an on-premises setup, that service runs on your side too.
- Cloud: subscription, zero maintenance
- On-premises: your servers, your database
- The same core — no feature gap
- Passwordless identity: central sign-on + revocable token
Up and running in five steps
1 · Open the project
Set the project name and short key (e.g. WEB); from then on records are numbered WEB-1, WEB-2.
2 · Shape the workflow
Write the state names and order the way the team actually works; choose which state counts as done.
3 · Add the team and roles
Bring members into the project and give them roles; set up teams and work with the same crew across projects.
4 · Get the work in
Import your existing list via CSV, speed up repeating work with templates, publish the external request form.
5 · Set the rhythm
Start the first sprint; after two sprints the velocity chart begins telling you your real capacity.
Technology
- .NET 9 Web API
- PostgreSQL
- Dapper + parameterised SQL
- Redis cache
- WebSocket live connection
- Angular 20 (standalone, zoneless)
- Drag-and-drop: CDK
- Library-free rich-text editor
- Library-free SVG charts
- Light/dark theme
- Docker containers
- Continuous delivery with Jenkins
- Centralised logs (Elasticsearch)
- S3-compatible object storage
- Server-side session tokens
Work tracking software is not measured by the fields it adds, but by how little the team has to look at it. A good record is the one that still holds the answer when, six months later, you ask why something was done this way.
Frequently asked
What is Stride and what is it for?
Stride is a work tracking and project management platform where teams run tasks, bugs and requests from one place. It includes a drag-and-drop board, customizable workflows, sprint planning, release management, reports and a form that collects requests from outside.
Can it be installed on our own servers?
Yes. Stride runs both as a cloud subscription and as an on-premises installation, with the same core and the same feature set in both. In an on-premises setup the data stays in your own database.
Can each project define its own workflow?
Yes. State names, their order, and which one counts as the start or as done are set per project. A software team's flow and a support team's flow can differ inside the same installation.
Can someone outside the team report a bug?
Yes. You publish a public form attached to a project; someone without an account fills it in from the link, and the request automatically becomes a work item assigned to the defined owner. The form is protected by spam controls and rate limiting.
Can we bring our existing list of work over?
Yes. Work items are imported in bulk from CSV and exported back to CSV; your data stays yours, and you are not locked in.
Are there file attachments and external integrations?
Both are marked 'soon' in the catalogue: the storage layer is ready but not yet wired to work items, and external integration endpoints are on the roadmap. Rather than describing them as if they existed, we prefer to say they do not.
See Stride with your team
Let us listen to how you work and set up your flow together — cloud or your own servers, we decide that together too. You will be talking to the team that wrote the product, not a sales team.
Machen wir heute den ersten Schritt
Beschreiben Sie Ihren Bedarf in einer Nachricht; wir melden uns innerhalb von 24 Stunden.