Range publishes a REST API at api.range.co/v1 covering teams, users, check-ins, and activity recording. User-scoped API keys are self-serve; OAuth bearer tokens sit in a closed program. An official Node.js SDK ships today, with about 75 native integrations plus Zapier.
Range scores A on the API Report Card. Range publishes a REST API at api.range.co/v1 covering teams, users, check-ins, and activity recording. User-scoped API keys are self-serve; OAuth bearer tokens sit in a closed program. An official Node.js SDK ships today, with about 75 native integrations plus Zapier.
Range has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
Range is an async team communication and work-coordination platform from Range Labs Inc. (San Francisco), founded in 2017 by Dan Pupius (CEO, ex-Medium VP of Engineering, ex-Google) and Jennifer Dennard, with co-founders Sean McBride and Stephanie Yeung.
Vertical: misc (horizontal team coordination / async standup tool; cuts across every Supergood vertical with no specific industry tilt). Sub-vertical: Async Standups / Team Check-ins / Work Coordination. Async daily standups posted to Slack or Microsoft Teams instead of synchronous standup meetings.
Low-to-moderate, 3/10. Range is a well-regarded product in the async-standup category but is one of many in a crowded, commoditized space dominated by free Slack-native bots and lower-priced alternatives (Geekbot, Standuply, Friday/DailyBot, StandIn).
Owner: Range Labs Inc. (privately held); HQ San Francisco, CA. Founders: Dan Pupius (CEO, ex-Medium VP Eng, ex-Google), Jennifer Dennard, with co-founders Sean McBride and Stephanie Yeung. Founded: 2017; product copyright on site reads ©2025 Range Labs Inc..
Founded 2017 by Dan Pupius (CEO, ex-Medium VP of Engineering, ex-Google) and Jennifer Dennard with co-founders Sean McBride and Stephanie Yeung.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.