Startups Using Slack in Boston
Via their job posts and information submitted by startups themselves, these are the Boston Slack startups we've found.
Interested in other technologies? Browse or search all of the built-in-boston tech stacks we've curated.
“Host monitoring platform built on top of Facebook’s legendary osquery agent [..] transforms your infrastructure into a rich database that you can query with standard SQL.”
Knowledgebase within your Slack to organize and share information with your teams.
Tech Stack Highlights
Draft.js & React – We recently rebuilt our text editor from the ground up on top of Draft.js. Building on Draft.js lets us create a smooth, rich editing experience that gets out of the user’s way so they can focus on sharing great content with their team. We also use Babel and Webpack to transpile and bundle up our front-end assets.
Slack – Tettra is built on top of the Slack platform. We use Slack for login and authentication and have built in notifications and slash commands. Our CEO even wrote an article about it.
PHP/Laravel – Our web application is built on the PHP web framework Laravel. Laravel comes with a ton of great building blocks including an ORM, queuing system, templating framework, and a prebuilt Vagrant box (VM) for local development to get us up and running and keep iterating quickly.
GitHub/Travis/Heroku – We use a combination of GitHub, Travis and Heroku for our continuous integration/deployment process. All pull requests get code-reviewed by a team member and have tests run automatically. Once code is merged to master, Travis runs the build and deploys to our staging environment on Heroku. We use the Heroku pipeline feature to promote staging code to production.
Intercom – At Tettra, everyone talks to customers. We use Intercom to get user feedback directly in the app, resolve bugs and inform our product process every day.
Tech Stack Highlights
Flask – we migrated to Flask from Django to increase the flexibility with which we build and manage our portfolio of workflow applications. We manage our own library of plugins and cookiecutters to enable efficient setup for new team members and team members picking up new projects.
React – we moved to React from Ractive as our JS framework for its performance, component oriented architecture, and server side rendering. React raises the level of abstraction in our front-end code base, making it more predictable and allowing our engineers to focus on building functionality versus wrestling with the framework.
AWS – as a healthcare IT company, we need to maintain a very high bar for our security and privacy infrastructure, given the high-stakes nature and stringent requirements of our large hospital system customer base. Our users rely on our ProviderMatch platform to match millions of patients to the right providers every year. AWS is our core cloud platform that allows us to accomplish this at scale.
ElasticSearch – our core patient-provider matching engine is enable by multi-faceted search. We have customized ES to our domain-specific data models, query types, and end user stories. ES recently migrated away from search as a core area of innovation (in lieu of analytics), so while we are investing in ways to optimize our utilization of ES, we also continue to keep an eye on the landscape of alternatives!
Slack – Slack is core to how our team communicates and gains critical insight into how our platform is performing. The ProviderMatch platform’s services are tightly integrated into Slack, and provide notifications and real-time performance insights that allow our team to stay on top of all platform activity.