IFTTT

IFTTT ranks 430th overall in the SaaS category with a composite score of 40 out of 100. The organization describes itself as Automations for business and home. 1,000+ of your favorite apps, services and devices. Save time and get more done, which frames how developers first encounter the brand on GitHub, in package registries and in search results.

Its documentation and learning material and developer reach come across as solid, and are what most developers will notice first when they land on the organization. By contrast, its developer experience and shipping velocity look minimal today, which is the clearest area where a small amount of focused work would visibly move the needle. Taken together, the picture is of a company whose public developer surface is neither uniformly polished nor uniformly weak, and where different audiences (contributors, integrators, evaluators) will likely form very different first impressions depending on which door they walk through.

IFTTT maintains 75 public repositories on GitHub, built primarily in Objective-C, Swift and Ruby, which together have collected 15,307 stars and drawn contributions from 2 developers outside the core team, 1 of those repositories have seen commits in the last 90 days, a useful proxy for how much of the codebase is genuinely alive rather than archived.

For anyone evaluating IFTTT as a technology choice, weighing a contribution, integrating the APIs, or comparing it against similar companies in the space, the sections below break down each of these signals in detail and link straight through to the underlying repositories, documentation and community threads that inform the score.