Structured task updates for small teams
Every task gets a real update. Every day.
RubyTrack is the task tracker for small teams that enforces structured progress updates — time spent, honest estimates, and visible blockers — so team leads always know where work stands.
Migrate billing webhooks
Move webhook handlers to the new queue and verify retries against staging.
How it works
From task to trusted status in four steps
RubyTrack doesn't evaluate your team's work — it makes sure progress is reported when it matters, so status is something you read, not something you chase.
- 01
Set up teams and tasks
Create your organization, add teams, and create tasks with a title, description, and estimated completion date. Team leads assign work, or members pick up unassigned tasks themselves.
- 02
Update daily, with structure
Every active task asks its assignee for a daily update — progress notes, time spent since the last update, and blocker status — through in-app and email reminders.
- 03
Make status changes carry proof
Moving a task to In Progress, Blocked, or Done requires the right data: a time entry, a fresh estimate, or an explanation. RubyTrack rejects transitions with missing information.
- 04
Review progress and history
Team leads see progress, blockers, estimate changes, and time totals per task and per team — backed by a complete activity log of who did what, when.
Features
Everything accountability needs — nothing it doesn't
Structured status transitions
Moving a task requires the right data — a time entry, a fresh estimate, or an explanation. Incomplete updates are rejected by the backend.
Daily update reminders
Every active task asks its assignee for a daily update, in-app and by email — blocked tasks included.
Incremental time tracking
Report time in units: 1U = 15 minutes by default, configurable per organization. Totals add up automatically.
Honest estimates, not deadlines
Estimated completion dates can move — but every change needs an explanation and lands in the task history.
Blocker tracking
Blocked needs a reason, and every day blocked needs a note on what was tried. Blockers stay visible until resolved.
Teams, roles & permissions
Owners, team leads, and members — across multiple teams and organizations, with different roles per team.
Complete activity log
Every status change, time entry, estimate change, and override is recorded — auditability by default.
In-app & email notifications
Assignments, comments, status changes, and daily reminders reach people where they actually look.
Daily rhythm
Updates happen by design, not by discipline
Every active task requests an update each day — a progress note, time spent, and an estimate check — through in-app and email reminders. No progress is fine too; it just takes a note.
Provide Status Update
Keep your team lead informed
What have you accomplished?
Current Status
Blockers
Blocked work stays loud until it's resolved
Marking a task Blocked takes an explanation, and every day it stays blocked takes a note on what was tried. Blockers get attention instead of gathering dust at the bottom of a board.
Lea N.
SSO integration
Waiting on SAML metadata from the customer's IT team.
🚫 Blocker: SAML metadata missing
Day 2
Followed up by email, CC'd their admin.
Day 3
Metadata received — resuming the integration.
Visibility
Team leads see the week breathe
Updates received, time logged, estimates moved, blockers open — per task, per member, per team. And behind every number, a complete activity log for handovers and reviews.
This week
Up to Date 89%9
Active Tasks
1
Pending Updates
2
Blocked Tasks
Principles
Opinionated where it counts
RubyTrack is intentionally small: accountable progress reporting and team transparency — not another everything-tool.
No hard deadlines
Estimates over deadlines: dates can move, but every move is explained and recorded.
The system asks
Reporting is part of the workflow, not a favor — so team leads never have to chase.
Blockers stay loud
A blocked task is an active task. It keeps asking what was tried until it's resolved.
History is the record
Estimates, time, comments, overrides — the task history tells the true story of the work.
Built by Alpine Edge
Engineered by the team behind Swiss cloud & DevOps projects
RubyTrack is developed, hosted, and supported by Alpine Edge — a Swiss-Albanian consultancy for cloud infrastructure, DevOps automation, private AI, and call center technology across Europe and MENA. The engineers who run production infrastructure for other companies run yours too.
FAQ
Common questions
What is RubyTrack?
RubyTrack is a task management app for small teams that enforces structured progress updates. Every active task requests a daily update from its assignee, and every status change requires real information — time spent, an updated estimate, or an explanation — so team leads always know where work stands.
How is RubyTrack different from other task trackers?
Most task trackers make updates optional, so boards go stale and team leads end up chasing people. RubyTrack makes updates part of the workflow: moving a task requires a time entry, changing an estimate requires an explanation, and a blocked task requires a note on what was tried. Progress reporting happens by design, not by discipline.
How does time tracking work in RubyTrack?
RubyTrack tracks time incrementally in units called U. By default 1U equals 15 minutes, and the unit is configurable per organization. Whenever a task update requires time input, the assignee enters the time spent since the last update and RubyTrack computes the total time taken automatically.
What happens when a task is blocked?
Marking a task as Blocked in RubyTrack requires a comment explaining the blocker. While the task stays blocked, each daily update must describe what was attempted and how the blocker is progressing. Blocked tasks remain active and visible instead of quietly disappearing from view.
Does RubyTrack enforce deadlines?
No. RubyTrack deliberately has no hard deadlines. Each task carries an Estimated Completion Date that the assignee or team lead can adjust at any time — but every change requires an explanation and is recorded in the task's history, so estimates stay honest.
Who is RubyTrack for?
RubyTrack is built for small teams and their team leads — software teams, agencies, studios, and any group where a lead needs reliable daily progress without chasing people. An organization can hold multiple teams, and users can hold different roles in different teams.
What roles does RubyTrack support?
RubyTrack has three roles. Owners manage the organization, its members, and its settings. Team leads create, assign, reassign, and archive tasks in their teams. Members work on tasks, post updates, and can pick up unassigned tasks. A user can be a team lead in one team and a member in another.
How much does RubyTrack cost?
RubyTrack is currently in early access. Contact Alpine Edge at info@alpineedge.ch to join the early access program and help shape the product — pricing will be announced with general availability.