You don’t need more metrics — you need better insights

We recommend getting started by scheduling a meeting with one of our product experts. They’re happy to give you a tour of the product, answer any questions you may have, and work with your team to tailor a trial/POC plan for your organization.

Alternatively, you can start a free 14-day trial.

Getting started with Swarmia is straightforward and you can either set it up on your own or get support from our customer success team.

The main set up steps include:

• Connecting GitHub to Swarmia. After you’ve selected the repositories you’d like to connect, it typically takes us a few hours to import your historical data, or up to 24 hours in with large organizations.
• Connecting Jira/Linear to Swarmia. Importing historical data typically takes a few hours, or up to 24 hours in with large organizations.
• Setting up the organizational structure and teams. You can automate team membership management from GitHub or your HR system.
• Configuring investment categories. You can quickly set up rules that determine the categories in which PRs and Jira tickets are assigned.
• Onboarding your first teams. Each team can control their own settings, set up Slack notifications, and adopt working agreements that are relevant for them. For larger organizations, we recommend a gradual roll out with onboarding support from our customer success team.

We hear from customers who’ve used competing tools that the data quality in Swarmia is generally better than in any other tool they’ve used.

There are a few reasons for this:

• Swarmia is not a black box: instead of only showing aggregate metrics, Swarmia allows you to drill down to the numbers behind each aggregate. This way, you can quickly validate the accuracy of the data you’re seeing.
• Rule-based automation: there’s no secret sauce or magic “algorithm” behind the way we categorize data in Swarmia. Instead, you can use flexible rules to decide which data points to include and where.
• Real-time data sync: the changes you make in GitHub and Jira are reflected in Swarmia in near real time.
• Teams control their own data: unlike competing products that only offer leadership dashboards, Swarmia also contains powerful features for engineering teams. By using Swarmia’s tools and insights in their daily work, engineering teams are motivated to keep their data in good shape.

No. One of our product principles is that every software team is different. In practice, this means that Swarmia works for your engineering teams as well as the whole organization, no matter how they’ve decided to use Jira.

We often hear from customers that even a short trial with Swarmia has had a positive impact on their Jira hygiene.

Absolutely. Reach out to hello@swarmia.com or your account manager to get your copy.

We’re happy to share the report with anyone we have a legitimate business relationship with. If you’re a security team member looking for an answer to this question, please make sure that your point of contact for the Swarmia evaluation has talked to your account manager about it.

We’d be happy to complete a security questionnaire for any company considering one of our paid plans. Please reach out to your account manager or hello@swarmia.com to get started.

Swarmia supports Single Sign-On (SSO) through Okta and Google as well as secure login through GitHub.

With SSO through Okta or Google, you can give Swarmia access to people in your organization who don’t have GitHub credentials.

The typical Single Sign-On features work through the GitHub authentication:

• Anyone with access to the relevant GitHub organization will also be able to access Swarmia, so you don’t need to create Swarmia user accounts for each employee.
• When an account is disabled from your SSO provider, if you’ve configured it to be deleted from GitHub the change will also propagate to Swarmia automatically.

Yes. You can read more about on-premise installations and contact your account team if you’re interested in hearing more.