Skip to content

Commit

Permalink
Update h tags
Browse files Browse the repository at this point in the history
  • Loading branch information
seanmitchell committed Jan 9, 2024
1 parent 4b1b0bb commit 041bba2
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions our-internal-systems.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,37 +2,37 @@

Besides the customer-facing applications, like the different versions of Basecamp, we have a number of internal systems that help us support, report, and operate the company. They are as follows:

### Dash
## Dash

Dash is the main hub for everything that has to do with logging (like finding why a request is slow or whether an email has been delivered), reporting (everything from number of support cases handled to split of devices used to access Basecamp), application health (response times, job queue exceptions etc).

[dash.37signals.com](https://dash.37signals.com)

### Queenbee
## Queenbee

Queenbee is our invoice, accounting, and identity system. Here you can look up any customer account, see whether they are comped, refund an invoice, or even login as a customer.

That’s an immense amount of power and we take its use very seriously. We only ever login as a customer after having been given explicit permission to do so, never preemptively. Our customers expect that their information is confidential, even from us, and we intend to honor that expectation at all times.

[billing.37signals.com](https://billing.37signals.com)

### The 37 command
## The 37 command

This is perhaps less of a system and more of an interface to all our other systems. The 37 command gives easy access to the production consoles for all the applications, which is often needed when diagnosing or fixing custom issues. It also allows you to directly grep and tail log files for live debugging, amongst other things.

[github.com/basecamp/37](https://github.com/basecamp/37)

### Sentry
## Sentry

We track programming exceptions on Sentry. When a customer hits a “Oops, something went wrong!” screen, that means there’ll be an entry in Sentry explaining to programmers why they saw that screen. Keeping the exceptions under control and monitored is primarily the responsibility of SIP and Jim via on-call.

[getsentry.com](https://getsentry.com)

### Kandji
## Kandji

[Kandji](https://kandji.io) is how we make sure all work laptops are securely configured and running the latest software updates. It helps us reduce our exposure to security incidents. You can read more about this in [Managing work devices](https://github.com/basecamp/handbook/blob/master/managing-work-devices.md).

### Shipshape
## Shipshape

Shipshape is the OG in-house tool for ensuring your work laptop is safe and secure. We still run it, but it's gradually being superceded by Kandji. When you’re given access to the company’s GitHub account, you can run Shipshape to be sure you’re up to code. Shipshape will also test your machine periodically to let you know (and our SIP team know) if your machine springs a leak and needs bailing out.

Expand Down

0 comments on commit 041bba2

Please sign in to comment.