Flyst puts priorities, projects, cycles and the work itself in one fast, keyboard-first workspace. It stays quick at a hundred projects, and the hundredth teammate never adds a seat fee.
This board is live. Click a card to move it along, or press C to add one.
Moves in from the tools you have, and keeps talking to them
The problem
The roadmap is a spreadsheet, the spec is a doc, the standup is a thread and the truth is in someone's head. Every week somebody pieces it back together.
Flystone source of truthEverything in one workspace
Six building blocks that cover the whole path, from a rough idea in intake to a shipped outcome in analytics.
State, priority, estimate, dates, labels, sub-items and relations, all editable inline and all searchable.
Index work item titles
Rank by recency
Highlight matched characters
Time-boxed delivery with burn-down, scope tracking and automatic carry-over.
Group work by feature or initiative and watch each one fill in.
Specs and decisions written right beside the work they describe.
We rank by recency first because most searches are for work touched this week.
@WEB-214Filter once, save it, share it. Everyone looks through the same lens.
Work distribution, cycle progress and lead time come straight from the work, not from a quarterly export.
Requests from anyone land in one triage queue. Accept, decline or snooze them before they reach the board.
Export to PDF from Pagesvia emailAccept
Dark mode for the portalvia formSnooze
Login loop on iOS 18via SlackAccept
Cycles
Commit work to a time-boxed cycle and Flyst tracks scope, velocity and the projected finish as the work moves. Drag the sliders to see a cycle react.
At 5.5 points a day the cycle closes 1 day early.
Layouts
Board for flow, list for triage, spreadsheet for bulk edits, calendar for dates, timeline for dependencies. They're lenses over the same records, never copies.
Backlog2
Todo2
In progress1
In review2
Done1
Same 8 work items · filtered to Cycle 14 · grouped by state
Same 8 work items · filtered to Cycle 14 · grouped by state
Same 8 work items · filtered to Cycle 14 · grouped by state
Same 8 work items · filtered to Cycle 14 · grouped by state
Same 8 work items · filtered to Cycle 14 · grouped by state
From priority to shipped
Five stages, one continuous record. Scroll through a quarter in Flyst.
Start from an initiative with an owner, a target date and a health signal that leadership can read at a glance.
Initiatives · Q4
Break the outcome into modules and work items, each with a state, a priority and someone accountable.
Search v2 · structure
Module · Indexing6 items
WEB-214 Command palette fuzzy search
WEB-230 Incremental re-index
Module · Ranking4 items
WEB-231 Recency boost
Module · UI5 items
Pull the next slice into a cycle. Scope and capacity are visible before anyone says yes.
Cycle 15 · planning
42 of 48 points committed · 6 spare
Work moves across the board, linked pull requests update it, and the activity feed records every decision.
Activity
MRlinked pull request #482 to WEB-219
AKmoved WEB-214 to In review
BotWEB-219 → Done after #482 merged
NPcommented on WEB-208
Cycle reports and analytics turn what happened into better estimates for the next round.
Cycle 14 · report
Lead time down 18% on the previous cycle
Keyboard first
Every common action has a single-key shortcut, and ⌘K reaches everything else. Go ahead and try the keys on this page.
SWEB-203 → Done
CWEB-229 created in Todo
Shaped to the team
States, properties and views are configured per project, so engineering, product, design and operations each work the way they already do.
Starter work items
ENG-101Migrate auth to OIDC
ENG-102Flaky test in billing suite
ENG-103Upgrade Postgres to 17
Switched on for engineering
Starter work items
PRODUCT-101Usage-based alerts
PRODUCT-102Onboarding checklist
PRODUCT-103Admin audit log
Switched on for product
Starter work items
DESIGN-101Empty states pass
DESIGN-102Mobile nav rework
DESIGN-103Icon set refresh
Switched on for design
Starter work items
OPS-101Quarterly access review
OPS-102Laptop refresh batch
OPS-103Vendor contract renewals
Switched on for operations
Import · sample runs
Illustrative timings. Real imports depend on history and attachments.
Migration
States map to states, people map to people, and comments keep their authors and timestamps. We run the first migration alongside you.
The difference
A spreadsheet, a doc, a chat thread and a board can each hold part of the work. Only one place can hold all of it.
Security and control
Roles, history and backups that hold up when someone asks who changed what, and when.
Work items, pages and attachments are encrypted in transit and at rest, with sessions that expire on your terms.
Sign in through OIDC or SAML, with roles for admins, members and guests per workspace and project.
Every change to every work item is recorded, including who changed it, what changed and when.
The same access rules apply to the interface, the API and webhooks, with no side doors.
Download work items, pages and their history as CSV or JSON, or pull everything through the API whenever you need it.
Nightly backups are verified by actually restoring them, not just by counting files.
FAQ
If it isn't here, write to us and a person who works on Flyst will answer.
Most teams are working in Flyst on day one. We help you set up workspaces, states and views, run the first import with you, and show the team the shortcuts that make updating work faster than skipping it.
Yes. States, properties, labels and views are configured per project, so engineering can run cycles with estimates while operations tracks due dates and recurring work in the same workspace.
Yes. Importers bring over work items, states, labels, assignees and comments, and we run the first migration with you so nothing gets left behind.
Pricing isn't per seat, so inviting the hundredth teammate costs the same as inviting the tenth. Ask us for a quote.
Pull requests can link to and move work items automatically, and updates can be posted to the channels your team already watches.
Yes. A REST API and webhooks cover work items, cycles, modules and pages, and they follow exactly the same permissions as the interface.
Invite them with guest roles that only see the projects you share. Permissions are enforced on every request, not just hidden in the interface.
Open Flyst, create your first cycle, and see where the work actually stands in the time it takes to write a status update.