Todd Schiller

We use Webpack for its bundling, code splitting, dev server, and hot module replacement capabilities Webpack

We use JIRA because it's a single tool that can be customized to each of our business processes: product development, customer on-boarding, and internal operations JIRA

We use Confluence for specifications and knowledge sharing. We chose Confluence over other wikis primarily because of its integration with JIRA Confluence

We use Zendesk for customer support and hosting documentation. Additionally, we provide documentation search from within our application using Zendesk's API Zendesk

We use Heroku because it eliminates the hassle of managing our user acceptance testing and sales demo environments Heroku

We use Bitbucket and Bitbucket Pipelines because of its tight integration with JIRA and code authorization features.

The primary drawback is that its extension ecosystem (e.g., PR review tools) is miles behind Github Bitbucket

We use Microsoft Azure because many of our clients are already Azure for their private cloud. Additionally, Azure supports App Service Environments (ASE), which isolates the application resources and gives us a static IP for securely accessing external resources

Additionally, MSSQL supports columnstore tables which is critical for running fast analytics over large datasets Microsoft Azure

We maintain a fork of Celery 3 that adds HTTPS support for Redis brokers. The Winning Model currently uses Celery 3 because Celery 4 dropped support for Windows.

We plan on migrating to Celery 4 once Azure ASE supports Linux apps Celery

Highcharts provided the best tradeoff between customization and pre-built chart coverage Highcharts

We use D3 for creating custom charts that aren't available in off-the-shelf libraries D3.js