Startups Using HAML in Boston

Via their job posts and information submitted by startups themselves, these are the Boston HAML startups we've found.

Interested in other technologies? Browse or search all of the built-in-boston tech stacks we've curated.

“Find, compare, and review doctors.” Reviews are individually human-moderated.

Tech Stack Highlights

Ruby On Rails – We use RoR for our core site implementation, enabling users to search for medical Providers and easily leave ratings & reviews. Our web pages are built using Bootstrap, HAML, SASS and Javascript technologies. We’ve built a data model system in Python that replaces ActiveRest. That model system is shared as a reusable Library by many of our other applications.

Postgres & Redis – All this is backed up by RDS instances in AWS running PostgresDB. We heavily use Redis and SOLR for data caching and queue management.

Flask/Python – The rest of our apps and services – Email systems, data analysis, internal tools – all run in Python based Flask/Flask-Restless environments.

ELK – Our logging system is run as an Elasticsearch-Logstash-Kibana stack utilizing Filebeat and Logspout for streaming the log output. From this stack we’ve also created a comprehensive Technical SEO Dashboard where we can monitor crawlers and their activity and measure the cause & effect on new site features.

DevOps – Our apps are deployed using Docker Swarm orchestration via Ansible scripts for independence from specific cloud providers. We’ve built a structure with Docker in a Blue/Green deployment methodology so there is zero downtime when releasing code updates. The system is front ended with Jenkins-CI for automated execution of Unit/Integration/Acceptance test suites.

Show more details

Peer-to-peer local business marketing platform.

Show more details

Matching patients with post-hospital care.

Show more details

Video hosting, sharing, optimization.

Tech Stack Highlights

Ruby on Rails – We use Rails for most of our services. It’s easy to read, easy to test, reasonably fast to learn, and opinionated in ways that we find helpful.

Elixir – We’re using Elixir for select services where high concurrency is important.

React – We are using React on new frontend features because it’s stateless paradigm makes for code that is easier to reason about and winds up with fewer bugs. It’s also nice to have a single framework across our services, so folks don’t have to learn an entirely new system every time they work on something different.

MariaDB – It seems like everyone is moving to NoSQL data stores, but we love SQL! It turns out that databases that have been around for several decades are very good at what they do — indexing, locking, transacting — and using this proven technology means we get a lot of DBMS features “for free” that NoSQL variants force you to build yourself. We do have a service at scale beyond what a single SQL database can support, and in that instance we are sharded across several database instances.

Docker – All new application servers that we build are containerized and thus entirely immutable. This eliminates an entire class of problems that arise when servers are otherwise left in an unexpected state. We never have to worry about rogue processes, old open ports, or artifacts on the file system impacting a newly-deployed set of code.

Show more details

Health data analysis and social tools for people with chronic illness.

Show more details

Personal savings and investment insight tools.

Show more details

Employee engagement platform.

Tech Stack Highlights

Ruby on Rails – We’re a Ruby on Rails application running on Heroku with PostgreSQL as our primary database and Redis available for ephemeral data. We use the Fastly CDN for our assets and Cloudinary for file management, in particular, image management. For search, we leverage Postgres’s full-text search with the pg_search gem.

Segment and Redshift – We use Segment to collect analytics about the usage of our app. We use their analytics-ruby gem and analytics.js library for back-end and front-end analytics respectively. We then leverage them to pipe the data into an Amazon Redshift data warehouse where we can analyze the data. Recently implemented Chartio to visualize that data with dashboards.

Front End Technologies – We use SASS for CSS management, Haml for HTML, and coffeescript to more cleanly write javascript. We also use Modernizr for gracefully degrading CSS features. We use Foundation Framework to make our application responsive.

CircleCI – We use continuous deployment as our deployment strategy. Every pull request is code reviewed in GitHub and deployed to an integration environment where it’s available for the reviewer, the developer, and anyone else in the organization to test and review. Additionally, we have a suite of thousands of unit tests built on MiniTest and feature tests built on Capybara, running continuously on every commit with CircleCI. Assuming it passes all our checks, manual and automated, it’s then merged into master and deployed to production by Heroku.

Show more details