Revenue from Stripe, issues from GitHub and Linear, errors from Sentry and Bugsnag, hosting costs from AWS. There are six integrations, and this page says what each one reads and how often.
A connection is mapped to the project it belongs to: a Stripe product, a GitHub repo, a Sentry project, an AWS tag. One account can feed several projects.
Stripe revenue and AWS costs are pulled once a day. GitHub, Linear, Sentry and Bugsnag are fetched when you open a project and cached for a few minutes. Nothing here is real-time.
Integrations are part of the Builder plan. On the free plan you enter revenue and costs by hand, and the rest of the dashboard works the same way.
Stripe brings in revenue and AWS brings in costs. The other four put issues and errors on the project page so you can see them without opening another tab.
Stripe is the only automatic revenue source today. Revenue from anywhere else is typed in by hand.
Connect through Stripe, then map each Stripe product to a project. Shipchart reads paid invoices and charges and records a monthly total per product, split into recurring and one-time revenue, with refunds taken off. It syncs once a day, and there is a Sync now button if you are impatient. The first sync goes back 12 months. You can connect more than one Stripe account.
See the repo and the open issues on the project page, next to the revenue and the roadmap.
Install the Shipchart GitHub App on the repos you choose. Each project shows its repo, open issues, recent pull requests with their review and check status, and the last few commits. The data is fetched when you open the project and cached for 15 minutes. You can create an issue from a roadmap item or an error, and assign an issue to Copilot.
Connect with OAuth. Each project shows issue counts by state, the current cycle and recent issues, cached for 15 minutes. You can create Linear issues from Shipchart, export a roadmap item as an issue with sub-issues, and pass an issue to a Linear agent.
Recent production errors for each project, with a way to turn one into an issue.
Connect with OAuth. Each project shows its unresolved errors, event counts for the last 24 hours and 14 days, and the number of users affected, cached for about 10 minutes. You can resolve or ignore an error from Shipchart, or turn it into a GitHub or Linear issue, and Shipchart can write the issue up from the error details.
Connect with a personal API token. You get the unresolved count and the most recent open errors for each project, with the same resolve, ignore and create-issue actions as Sentry. Event volume and affected-user counts are not shown for Bugsnag yet.
Put the AWS bill next to the revenue of the project it pays for.
Create an IAM role that can only read Cost Explorer and paste in its ARN, so no access keys change hands. Costs are pulled once a day, grouped by service, and you link them to a project by tag or by service. They appear as their own line in the project financial summary, separate from the expenses you enter yourself.
If a project is paid through Paddle, Lemon Squeezy, an app store or a bank transfer, you type the monthly figure in yourself. It takes about a minute per project. More revenue sources are planned, and the button below is the quickest way to tell us which one you are waiting for.
The free plan covers four projects with manual revenue. Integrations come with the Builder plan, and you can connect them whenever you upgrade.