Tracklane is the purpose-built issue tracker for planning cycles and shipping modern software.
Model your real process with tailored issue states.
Break quarters into focused, time-boxed cycles.
Plan work that spans squads without duplicate boards.
Watch scope, velocity, and burn-up in real time.
Product teams at 2,400 companies plan their cycles in Tracklane
Faster triage
11min
Median time a team spends on weekly triage after moving to Tracklane, down from more than two hours.
Weekly triage time, median team
Fewer stale issues
-38%
Issues untouched for 30 days, after one quarter of auto-close rules and backlog reviews.
Cycles finished on time
1.7x
More cycles closed with at least 85% of the scope the team committed to.
Median change across 212 workspaces in their first two quarters on Tracklane. Tracklane customer data, Q2 2026.
Intake, discussion, permissions and backlog health live next to the issues they belong to, not in a separate tool.
Tobi Adeyemi2 h ago
Backoff caps at 6 attempts over 24 hours. Anything older goes to the dead-letter queue in PLT-472.
Tobi linked #1184
Mara Lindqvist48 min ago
Can we log each attempt, so support can answer "did it send?" without asking us?
Tobi Adeyemi20 min ago
Added to the delivery log in PLT-491. It ships with this cycle.
142issues older than 60 days18 fewer than August
Cycles give your roadmap a heartbeat: scoped batches of work with a clear start, a clear end and an outcome everyone can see.
A board that mirrors reality. States, rules and automations match how your team actually works. Rename, reorder and rewire them in seconds.
Milestones that hold. Break the quarter into two-week cycles, pin the dates that matter and check capacity before you commit.
Cycle 44 is 3 points over capacity. Move PLT-502 (3 pts) to Cycle 45?
Projects across teams. One plan for work that spans several squads, with progress and written updates from each of them.
Noor Haddad posted an update on Tuesday
Metering is live in staging and the invoice preview ships with Cycle 43. Mobile starts the plan picker next week.
Progress you can trust. Velocity, scope change and cycle completion are calculated from the work itself, not from status meetings.
Branches, pull requests and merges update Tracklane for you, so status is never a chore someone forgets.
Copy a branch name from any issue. Pushing it moves the issue to In progress.
Opening a pull request links it to the issue and moves it to In review.
Merging to main closes the issue and adds it to the cycle summary.
$ npm install -g @tracklane/cli
$ tl issue create "Retry failed deliveries with backoff" --team PLT --estimate 5
Created PLT-479 in Platform, Cycle 42
$ tl branch PLT-479
Switched to branch 'mara/plt-479-retry-failed-deliveries'$ git checkout -b mara/plt-479-retry-failed-deliveries
$ git commit -m "Retry failed deliveries with backoff (fixes PLT-479)"
$ git push -u origin HEAD
tracklane: PLT-479 moved to In progress
Open a pull request to move it to In review$ curl https://api.tracklane.dev/graphql \
-H "Authorization: Bearer $TRACKLANE_TOKEN" \
-d '{"query":"{ cycle(team: \"PLT\", number: 42) { progress scope completed } }"}'
{ "data": { "cycle": { "progress": 0.47, "scope": 58, "completed": 27 } } }Most teams decide within two weeks. Here is what that looks like, and what we handle for you.
Bring issues, labels, cycles and assignees over from CSV or your current tracker's API. You preview the mapping before anything is written.
Pick one team, plan a two-week cycle and run standups from the board. A solutions engineer joins your kickoff call.
The SOC 2 Type II report, DPA, pen test summary and an SSO trial are ready before procurement asks for them.
Planning a pilot for more than one team? We will scope it with you.
Platform teams put Tracklane through procurement every week. Everything you need is documented and available on request.
Audited every year by an independent firm. The report is available under NDA.
Provision and remove members from your identity provider automatically.
Every permission, export and setting change, kept for 400 days.
Host each workspace in the US (Oregon) or the EU (Frankfurt).
AES-256 at rest and TLS 1.3 in transit, with keys rotated every 90 days.
Team-level access, guest roles and private teams for sensitive work.
From ten-person startups to platform organizations with forty teams, plans stay honest and shipping stays visible.
“Triage used to eat our Monday. Now it is a ten-minute pass before standup, and every issue lands with the right team.”
“The burn-up chart quietly replaced our status meeting. Leadership opens the cycle page instead of asking me.”
“Design, product and engineering finally plan in the same cycle. Handoff stopped being a ceremony.”
“Nobody keeps a private to-do list anymore. Branch names and pull requests do the status updates for us.”
Start free with the whole team. Upgrade when you need cycle automation, insights and admin controls.
Enterprise. Over 500 seats, a custom contract or a dedicated region? We will put a plan together with you.
Something we did not cover? Our team replies within one business day.
Most teams import in under an hour. The importer brings over issues, comments, labels, cycles and assignees from CSV or your current tracker's API, and shows a preview of the mapping before anything is written.
Yes. Cycles are optional per team. Support and operations teams often run a continuous board with triage and SLAs, while product teams in the same workspace plan in two-week cycles.
Guests are free on Team and Scale. They can see only the teams you share with them and can comment, create and update issues there. Contractors who need access to several teams are billed as members.
Tracklane syncs two ways with the major Git hosts, including self-hosted instances on Scale. Any CI system that can call a webhook can post build and deploy status to an issue.
Workspaces are hosted in the US (Oregon) by default. Scale customers can choose the EU (Frankfurt) region at sign-up, and we migrate existing workspaces on request with no downtime.
It rolls into the next cycle automatically, keeping its history and estimate. You can choose to roll over everything, only work that was started, or nothing, and the cycle summary lists every issue that moved.
Free for up to 10 members. Import your backlog in minutes and plan your first cycle today.
We sent a sign-in link to . It works for the next 30 minutes.
Every plan includes unlimited issues, the full keyboard-first app and imports from your current tracker. You pay per member, never for guests.
Invoices, seats and plan changes, explained.
Anyone with access to more than one team, or with admin rights. Guests limited to the teams you share with them are free on Team and Scale.
On yearly billing, new members are added at a prorated price on your next monthly true-up. We never charge for members who were removed before the true-up date.
Yes. Yearly Scale plans can pay by bank transfer with 30-day terms. Team plans pay by card; receipts and VAT invoices are available in workspace settings.
Registered nonprofits and open source maintainers get Team for free. Startups under two years old get 50% off their first year of Team.
Not sure which plan fits? Tell us about your teams and we will recommend one.
New features, improvements and fixes, shipped every two weeks with our own cycle.
Try a different word or clear the filters.
Welcome back. Use your work email or your company's SSO.
Opening the workspace for . This preview stops here, so nothing else happens.
Back to the siteEnter the email you sign in with and we will send a reset link.
If has an account, a reset link is on its way. It expires in one hour.
New to Tracklane? Start free
Set up takes about two minutes. Invite your team, import your backlog and plan your first cycle today.
“We had all 9 teams on Tracklane before the next cycle started.”
Jonas Wexler, Engineering Manager, Orrelby
We sent a confirmation link to . Your team will find you at .
A 30-minute call with a solutions engineer, shaped around how your teams plan and ship today.
Lucía will email with three times that suit your timezone, usually within four business hours.
Back to the siteHow we protect your workspace, who can access it and what we share with your security team during review.
SOC 2 Type II report, pen test summary, DPA and our completed security questionnaire. Shared under NDA, usually the same day.
We will send an NDA and the security pack to today.
Found a vulnerability? Email security@tracklane.dev. We reply within one business day and never pursue good-faith research.
Vantri builds routing software for regional freight carriers. When the platform group grew past 140 engineers, planning in spreadsheets stopped scaling.
Before Tracklane, each of Vantri's 14 teams kept its own spreadsheet of work, and a shared one rolled them up for leadership. Every Monday, team leads spent the morning reconciling the two. Every Thursday, a status meeting tried to answer what would actually ship.
"We knew the work was getting done," says Rhea Kapoor, Head of Platform. "We just could not see it without asking forty people."
Vantri started with a single pilot cycle on the Routing API team. The importer brought over 2,900 rows from that team's sheet in eleven minutes, including owners and estimates. Two weeks later the team had finished 91% of what it committed to, and the other leads asked to move.
“Triage used to eat our Monday. Now it is a ten-minute pass before standup, and every issue lands with the right team.”
Rhea Kapoor, Head of Platform, VantriTriage moved into one queue with suggested owners, so incoming requests from support stopped bouncing between teams. Pull requests now move issues on their own, which made the Thursday status meeting unnecessary. Leadership reads the cycle page instead.
Carry-over, the work a team planned but did not finish, dropped by 61% within two quarters. Rhea's team now uses the extra planning time to review the backlog health view and close stale issues before they pile up.
The company is moving its customer-facing roadmap into Tracklane projects, so account managers can see delivery dates without asking engineering.
Tracklane started in 2021, when three engineers got tired of updating tickets that nobody read. Today 46 people build it, and we plan every release in Tracklane itself.
Most trackers are built for the people who read reports. We build for the people who do the work: engineers, designers and product managers who want to know what to do next and then get back to doing it.
That is why Tracklane opens in under a second, works from the keyboard and updates itself from your code. Reports come out of that work for free, instead of being a second job.
We are a remote company with studios in Portland and Lisbon. We are profitable, independent and answerable to our customers.
Every interaction should finish before you notice it started. We budget milliseconds the way other teams budget headcount.
Good workflows out of the box, with room to change them. Settings exist for real needs, not to avoid decisions.
Decisions live next to the work, in issues and project updates, so anyone can understand why later.
We plan in two-week cycles, publish a changelog after every one and fix what customers report first.
Remote within Europe and the Americas, with optional studio days.
Own the sync engine that keeps every client up to date in under 100 ms. You have shipped real-time systems in TypeScript or Rust and care about offline behaviour.
careers@tracklane.devRun pilots and migrations with platform teams across Europe. You have been an engineer or engineering manager and like explaining how tools fit into real workflows.
careers@tracklane.devDesign the charts and reports leaders use to understand delivery, without turning Tracklane into a dashboard tool. Strong data visualization portfolio required.
careers@tracklane.devLast updated September 1, 2026. This policy explains what Tracklane Labs, Inc. collects, why, and the choices you have.
Account details you give us (name, work email, workspace name), the content you create in your workspace (issues, comments, attachments), and technical data needed to run the service, such as IP address, browser type and error logs.
To provide and secure Tracklane, to send service emails such as sign-in links and invoices, and to improve the product using aggregated usage data. We never sell personal data and never use workspace content to train machine learning models.
Subprocessors that host and operate the service under contract, listed on our security page. We disclose data to authorities only when legally required and notify you first unless prohibited.
Workspace content stays until you delete it. Deleted workspaces are removed from production within 30 days and from backups within 35 days after that.
You can access, correct, export or delete your personal data at any time from account settings, or by contacting us. EU and UK residents may also lodge a complaint with their local supervisory authority.
Email privacy@tracklane.dev or write to Tracklane Labs, Inc., 1120 NW Couch Street, Portland, OR 97209.
Last updated September 1, 2026. These terms govern your use of Tracklane. Scale and Enterprise customers may have a separate agreement that takes precedence.
You must provide accurate information and keep your sign-in credentials secure. Workspace admins are responsible for the members and guests they invite.
Paid plans are billed per member in advance, monthly or yearly. Prices may change with 30 days' notice and apply from your next renewal. Downgrades take effect at the end of the current billing period.
You own everything you put in Tracklane. You grant us only the rights needed to host, display and back it up for you. You can export your workspace at any time.
Do not use Tracklane to break the law, to send spam, to probe or overload our systems outside the published API limits, or to store data you have no right to process.
You can cancel at any time from billing settings. We may suspend workspaces that break these terms after notice, except where immediate action is needed to protect other customers.
Tracklane is provided as is. To the extent allowed by law, our total liability is limited to the amount you paid us in the 12 months before the claim.
The link may be old, or the page moved in a recent release. These are good places to continue.