Get started in 15 minutes
Sign up, connect your tracker and read your first delivery insights in one sitting.
This is the short path from nothing to a working Firebeam workspace. It takes about a quarter of an hour, needs no installation and asks nothing of your team. Firebeam reads the history your tracker already holds, so the first insights appear on day one instead of after weeks of collecting data. If you are still deciding whether Firebeam fits, this page also shows exactly what setup involves.
Before you start
You need an account in Jira, GitHub, GitLab, Bitbucket, Linear or Azure DevOps that can see the project you care about, and the right to approve an app connection there (in some organizations that is a tracker admin). That is all. There is nothing to install, no agent to deploy and no workflow your team has to change.
Minute 0 to 2: Create your workspace
Sign up with your work email and name your workspace. Your free trial starts right away with every module available, and you become the workspace admin. If you would rather look around before connecting anything, tick the sample data option during signup and every module fills with a realistic demo project.
Minute 2 to 5: Connect your tracker
Open Integrations, pick your tracker and approve the consent screen it shows you. The connection is read-only for your source data, so nothing in your tracker is modified. Syncing starts in the background immediately, and the first items usually arrive within a minute.
Minute 5 to 8: Create a project and point it at your work
Under Projects, create a project and link the sources that belong to it: a Jira project, a GitHub repository or milestone, a Linear team or an Azure DevOps project. A project is the lens every module looks through, so choose the scope you would actually report on, for example one product or one team.
Minute 8 to 12: Read your first board
Open FlowLens. Your work is laid out by stage with cycle time, weekly throughput and an aging view, all computed from the real status history of your items. Two things are worth finding straight away: the oldest item still in progress, and the stage where work piles up. Those are usually your first talking points.
Minute 12 to 15: Switch on what you came for
Go back to the dashboard and activate the module that matches your problem. ScopeGuard if scope keeps growing, Promise if you need to know whether a date will hold, Stakemaster if status reports eat your week, Retrospective AI if retros repeat themselves. Then invite a colleague under Team so you are not the only one looking.
What you have after 15 minutes
A live workspace that keeps itself up to date, a project scoped to real work, flow metrics built from your actual history and at least one module switched on. Nothing was tracked by hand, and nobody on your team had to do anything.
Just evaluating? Skip the connection
You can see every module working without connecting a tracker. Choose the sample data option when you sign up, or load the sample dataset from the dashboard later. It can be removed again with one click, and a Demo workspace badge in the top bar shows while it is loaded.
What Firebeam reads, and what it does not
Firebeam asks your tracker for work items and their metadata: titles, descriptions, status history, assignees, estimates, comments, and pull request status for GitHub. It never fetches or stores file contents or source code. Access tokens are encrypted at rest, and you can disconnect an integration at any time under Integrations.