StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Product

  • Stacks
  • Tools
  • Companies
  • Feed

Company

  • About
  • Blog
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2025 StackShare. All rights reserved.

API StatusChangelog
  1. Home
  2. Companies
  3. TrackJS
TrackJS logo

TrackJS

Verified

JavaScript Error Monitoring for Production Web Applications

Stillwater, MN, USAtrackjs.com
43
Tools
3
Decisions
104
Followers

Tech Stack

Application & Data

8 tools

C# logo
C#
JavaScript logo
JavaScript
.NET logo
.NET
HTML5 logo
HTML5
TypeScript logo
TypeScript
CSS 3 logo
CSS 3
.NET Core logo
.NET Core
ASP.NET Core logo
ASP.NET Core

Utilities

5 tools

Stripe logo
Stripe
Slack logo
Slack
Google Analytics logo
Google Analytics
Elasticsearch logo
Elasticsearch
Baremetrics logo
Baremetrics

DevOps

1 tool

Kibana logo
Kibana

Team Members

Todd Gardner
Todd GardnerPresident

Engineering Blog

Stack Decisions

Todd Gardner
Todd Gardner

Nov 29, 2018

We've moved our transactional email away from Mandrill to Mailgun. We had continued using Mandrill after Mailchimp deprecated the service awhile back, because the amount of credits we were offered essentially made it free.

However, following a couple weeks of frequent downtime and poor service transparency from Mandrill, we decided it was time to make the switch. It appears they no longer had any engineers with the ability to identify the core problems.

Mailgun has been more reliable, yet not as reliable as we expected. We still see issues a few times per week with the API failing when we attempt to make a call. The Reporting UI is way better.

236k views236k
Comments
Todd Gardner
Todd Gardner

Nov 29, 2018

We migrated the hosting of our CDN, which is used to serve the JavaScript Error collection agent, from Amazon CloudFront to MaxCDN. During our test, we found MaxCDN to be more reliable and less expensive for serving he file.

The reports and controls were also considerably better.

1.72M views1.72M
Comments
Todd Gardner
Todd Gardner

Nov 29, 2018

We recently needed to rebuild our documentation site, currently built using Jekyll hosted on GitHub Pages. We wanted to update the content and refresh the style to make it easier to find answers.

We considered hosted services that could accept our markdown content, like ReadMe.io and Read the Docs, however both seemed expensive for essentially hosting the same platform we already had for free.

I also looked at the Gatsby Static Site generator to modernize Jekyll. I don't think this is a fit, as our documentation is relatively simple and relies heavily on Markdown. Jekyll excels at Markdown, while Gatsby seemed to struggle with it.

We chose to stick with the current platform and just refresh our template and style with some add-on JavaScript.

773k views773k
Comments