Check GitHub, deployments and revenue across projects on Mac

Keep each product’s connections together

The video uses two fictional projects, Orbit and Bloom, with their own code, deployment and payment connections. Configure each connection first; switching the project then shows its saved tools. Opening a provider’s website still uses your browser session.

If you maintain several products, your tools may be spread across personal accounts, organisations and teams. MakerNotch groups the connections for each product into a named project, so the repository you check and the deployment you open belong to the same context.

It is useful for indie developers and small studios that repeatedly check shipped products during the day. It does not provide shared team workspaces or replace the provider dashboards.

Browser profiles or a project status panel?

Separate browser profiles are useful when you need to work inside different provider accounts: review code, change deployment settings or manage billing. They keep those website sessions apart, but you still open each dashboard to check its data.

MakerNotch is useful when you first need a short status check. Once its connections are configured, selecting a project changes which credentials and resources the app reads. You still use the provider’s website for actions that the panel does not offer.

What you need	A suitable workflow
Work inside several signed-in accounts	Keep separate browser profiles for those accounts.
Check code, deployments and payments for one product	Select its MakerNotch project and inspect the connected tools.
Investigate a problem found in the panel	Open the provider and use the appropriate browser account.
Monitor every product continuously while your Mac sleeps	Use a hosted monitoring service; MakerNotch does not provide this.

You can use browser profiles and MakerNotch together. The practical benefit is fewer dashboard visits for routine checks, not the removal of every login or a guaranteed amount of time saved.

Want to see the project switch? Watch the demo with sample data. To compare this workflow with other apps, see notch apps for developers.

Set up two projects you can recognise

Use this example to establish the pattern. Orbit and Bloom are fictional products.

1. Create a MakerNotch project named Orbit and select it before adding connections.
2. Connect Orbit’s GitHub repository and Vercel projects. Confirm the returned repository and deployment labels.
3. Create a separate project named Bloom, select it, and configure its own repository, token and Vercel context.
4. Switch back to Orbit using the project selector. Confirm that you see Orbit’s data, then repeat for Bloom.
5. Add only the other services you actually need to check for each product.

The detailed guides cover GitHub token permissions and Vercel projects and environments. Configure one connection successfully before adding the next.

Choose connections around a question

Start with what you need to know when changing tasks:

• Did the change pass CI? Use GitHub pull requests and Actions, or GitLab merge requests and pipelines.
• Did it reach the intended environment? Use Vercel and check Production or Preview.
• What happened to payments? Use Stripe or Polar for the product’s payment metrics.
• What needs investigation? Use Sentry for production errors, Supabase for project status and service health, or Linear for issues assigned to you.
• How are visitors and email doing? DataFast and Resend provide different signals for those tasks.

A credential can have a wider scope than one product. In particular, Polar supports an optional product UUID: leaving it empty shows organisation-level metrics. Do not label organisation totals as one product’s revenue. Check each connection’s scope before relying on a comparison.

What happens when you switch accounts?

Each MakerNotch project stores its configured credentials in the Mac Keychain. Those credentials determine the data the app can read, so checking another configured project does not require changing a browser session first.

When you open GitHub, Vercel or another provider in your browser, the website uses its own signed-in account. You may still need to switch browser accounts to review a private resource. MakerNotch does not sign you into the provider’s website or bypass its permissions.

Keep your checks current

Automatic refresh applies to the selected MakerNotch project. It is optional and periodic; the app does not continuously monitor every product while you are away.

After switching projects, look at the connection status and refresh if needed. If the data does not match your expectation, check the active project name, repository, Vercel team and any product filter before changing credentials.

If the data looks like another project’s

Before replacing a key, check the resource each connection is reading:

What you see	What to check
PRs from a different repository	Active project and configured GitHub repository.
An unfamiliar deployment	Vercel team, project and Production or Preview filter.
Revenue from several products together	Polar organisation and product UUID; an empty filter covers the organisation.
Old data after switching projects	Connection status, last update and refresh of the selected project.

For separate revenue figures, follow the Polar product setup. If you deploy on Cloudflare, use the Cloudflare Pages guide.

A repeatable daily routine

Select the product you are about to work on, check its code and deployment state, and open the provider for any item that needs action. Use notes and the focus timer to support the work that follows. Move to the next project when you change tasks.

To see how the panel fits that routine, read the Mac notch app guide, or watch the app tour. MakerNotch also works on Macs without a physical notch.