Pricing

Standard
$20
per contributor per month
up to 15 contributors
  • $40/mo per additional contributor
  • Unlimited number of teams
  • Unlimited number of repositories
  • Unlimited access our integrations
Start a trial
Enterprise
Let's talk!
Custom pricing per active contributor per month or per year.

Custom POC and flexible trial periods.

Integrations

Frequently asked questions

Send any questions to sales@echoeshq.com
How long is the free trial?
The free trial is 4 weeks on a case-by-case basis depending on the size of the organization.
Does Echoes require access to the codebase?
Short answer: no, Echoes does not need access to the codebase! The long answer however depends on your source control manager.

With GitHub we explicitly do not request for repository access and are therefore prevented from accessing the content of your files by GitHub itself.

GitLab doesn't offer the same level of fine-grained permissions, which means that even although Echoes won't access the content of your git repositories, it is technically in possession of a token that would allow it to do so.
What is the overhead to using Echoes?
Echoes reports require day-to-day efforts to be tagged with their intent. This is typically as simple as adding labels to GitHub pull requests or GitLab merge requests, but there are multiple ways in which Echoes makes this task even easier.

  • A GitHub pull request or GitLab merge request automatically inherits its intent from the issue it resolves, if any. This makes it possible to express the purpose of the change only once during the filing of the issue.
  • Echoes optionally integrates with the most popular issue trackers and follows linked issues to determine the relevant intent without any developer action. For example with JIRA: a pull request may inherit an intent from a linked task, a parent user story, and a parent EPIC, in such way that a single annotation at the topmost level will propagate to the entire subtree.
  • Untagged units of work are transparently reported in the dashboards, where they can be linked to an intent directly from Echoes' interface. This makes it extremely easy to tag leftovers and reach 100% coverage in reports.
  • When used with GitHub, Echoes integrates with the GitHub Checks API and can report a CI failure when an intent annotation is missing. This behavior is optional, and disabled by default for members of the organization who have not been onboarded to Echoes as well as external contributors.
It's an interesting approach, but how do you know it works?
Arnaud Porterie, the founder of Echoes HQ, has extensive experience in engineering management and has successfully deployed many of the ideas built in Echoes. More specifically:
  • At Docker, Arnaud has managed one of the most active open source communities with over a 400 weekly contributors. Running a project at this scale has taught him both the importance of data for decision making and the importance of developer experience.
  • At Veepee, Arnaud has scaled a team of 350 to a European-wide organization of 900. He realized there how unequipped were engineering leaders to make data informed decisions and effectively communicate on their teams' activity in a way that their business partners and bosses could understand.
Our founding team is composed of highly senior engineers, including former FAANG.