Stride
منصة العمل التي تدير فيها الفرق المهام والأخطاء والإصدارات من مكان واحد: لوحات وسبرنتات وتقارير ونموذج طلب خارجي.
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, the support desk, 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.
Today Stride also talks to the other products in the same family: a request opened at the support desk becomes a development item in one click and the request hears back when the item closes; the personal dashboard shows the active time spent at the computer that week and suggests time entries for the items touched that day.
- 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.
Board (kanban)
Drag-and-drop columns, swimlanes by assignee or epic, a work limit per column and per lane; 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 shows in every sprint heading.
Roadmap & releases
A monthly roadmap of epic bars; the fill of a bar shows how much of the work beneath it is done. Component and release assignment.
Timeline & calendar
Items with start and end dates on a timeline, deadlines in a month view.
Reports & dashboards
Sprint burndown and velocity; cumulative flow, ageing work, cycle time and an epic report. Multiple dashboards assembled from gadgets.
Filters & list
A list across all projects; classic filters or a query language; saved and shared filters; CSV export and import.
External request form
A form per project that needs no sign-in; someone without an account fills it in and the request becomes a work item directly.
Item detail
Description, checklist, links, time log and comments on one page; watchers, cloning and a resolution field.
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. When an item is done a resolution field opens: fixed, won't do, duplicate or cannot reproduce. Frequently opened patterns become templates; when an item is cloned you choose which fields to copy, and its history is never copied.
- Per-project customizable workflow
- Epic → item → sub-task hierarchy
- Links between items: blocks / is blocked by / relates to / duplicates
- Item templates and cloning
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. For the longer horizon there is the roadmap: epics become month-scale bars, and the fill of a bar shows how much of the work beneath it is done. The next sprint gets filled from measured pace, not from a guess.
- Start / close sprint, carried-over work returns to the backlog
- Burndown, velocity chart and roadmap
- Cumulative flow, ageing work, cycle time, epic report
- Work limits per column and lane 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. The editor's insert menu carries structures such as tables, code blocks, coloured panels, status badges, date chips, decision boxes and item cards linking to another item; images are uploaded straight into the editor. 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; if email is connected, the same notifications go out as mail too.
- Comments, mentions, emoji reactions, checklists
- An editor with an insert menu and image upload
- Field-level activity and audit history
- Time logging, estimates and remaining time
Visibility and permissions
Every project has its own members and roles: admin, member, viewer. Teams cross project boundaries; a person can belong to several. At organisation level there is a separate layer: brands, branches and organisation staff. As for search, you can type an item key and jump straight to the record, or filter across all projects with the query language, save the result and share it with the team.
- Project roles + organisation staff + platform admin: three separate layers
- Saved and shareable filters, a query language
- Keyboard shortcuts and quick search
- A read-only audit log
The capability catalogue
- Bug / Task / Story / Epic / Sub-task
- Priority levels
- Per-project workflow
- Resolution: fixed, won't do, duplicate, cannot reproduce
- Work item templates
- Cloning: choose the fields to copy
- Item links
- Checklists
- Labels
- Bulk edit
- Backlog and sprint sections
- Start / close sprint
- Story points and estimates
- Work log and remaining time
- Components
- Releases
- Roadmap
- Due date reminders
- Drag-and-drop kanban
- Swimlanes by assignee or epic
- Column and lane work limits
- Quick add under every column
- List view
- Calendar view
- Timeline
- Summary screen
- Starred projects
- Rich-text comments
- Insert menu: table, code, panel, badge, date, decision, columns
- Image upload in the editor
- Mentions (@)
- Emoji reactions
- Watching items
- Activity history
- Teams
- General file attachments (PDF, zip) · soon
- In-app notification centre
- Assignment, mention, comment, status and due-date notifications
- Live connection, instant updates
- Email notifications (optional)
- Mark read / mark all read
- Search across all projects
- Jump by item key
- Classic filters or a query language
- Saved filters and sharing
- CSV export (with column selection)
- CSV import (with preview)
- Sprint burndown
- Velocity chart
- Created vs completed
- Status and resolution distribution
- Cumulative flow diagram
- Ageing work and cycle time
- Epic report
- Multiple gadget dashboards
- Project roles: admin / member / viewer
- Organisation staff: admin / agent
- Organisation → brand → branch structure
- Role and permission management, menu and screen permissions
- Read-only audit log
- Single sign-on (Passport)
- Personal settings, light / dark theme, colour palettes
- Public request form (no account)
- Form field designer
- Default assignee and priority for incoming requests
- Spam protection and rate limiting
- Personal API tokens: read / write, expiring or permanent
- Relay link: the request hears back when the item closes
- Tally link: weekly active time and end-of-day time entry suggestions
- Module market: the parts you do not use stay off
- A module that is off disappears from the menu
- Free trial without a card
- Subscription status: plan, included features, quota
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. And thanks to the module market only the part you use stays on — a module you switch off even disappears from the menu.
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 Passport, 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: Passport + revocable token
Packages sized to the team
Three packages, monthly per user; every one starts with a free trial that asks for no card. The current list and prices are on the product's own pricing page.
Starter
For a small team focused on one project: items and boards, the personal dashboard, brand and branch structure, the notification centre.
Team
For teams working with sprints and reports: everything in Starter plus saved filters and teams; a wider project and user quota.
Enterprise
For many projects and many modules: everything in Team plus custom gadget dashboards, every module and priority support.
Up and running in five steps
1 · Open the organisation and the project
Sign in with Passport, verify the organisation with the code sent to your email; type the project name, the short key (e.g. WEB) is generated for you and 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 a few sprints the velocity chart begins telling you your real capacity.
Technology
- .NET 9 Web API
- PostgreSQL
- Live connection: board and notifications refresh instantly
- Personal API tokens
- Angular 20
- Drag-and-drop board
- Rich-text editor
- Light / dark theme, colour palettes
- Turkish and English
- Docker containers, continuous delivery with Jenkins
- Passport single sign-on; no password in Stride
- Images stored in Vosetu Crate
- Read-only audit log
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, a roadmap, release management, reports and dashboards, a form that collects requests from outside, and links to the sister products.
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; a deactivated form cannot be reached from outside.
Can we bring our existing list of work over?
Yes. Work items are imported in bulk from CSV with a preview, and exported back to CSV with the columns you choose; your data stays yours, and you are not locked in.
Does it connect to the help desk and time tracking?
Yes. A support request opened in Relay becomes a development item in Stride in one click; when the item closes the request hears back. With Tally enabled, the personal dashboard shows the active-time card for that week and suggests time entries for the items you touched that day. Personal API tokens are issued for external systems.
Are there file attachments?
Images are uploaded into descriptions and comments straight from the editor. General file attachments such as PDF and zip are on the roadmap; rather than describing them as if they existed, we prefer to say they do not yet.
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.