FinchLabs.com
FinchLabs uses a shared security layer called Roost. Users sign in once, Roost manages identity and permissions, and each registered application decides what the authenticated user is allowed to do.
https://www.finchlabs.com/index.html
The public FinchLabs entry point and login experience. This is what users see first.
FinchLabs identity and security service
Roost answers the important security questions: Who is this user? Are they signed in? Which FinchLabs applications can they access? What role do they have?
A reference application that shows developers how to implement, exercise, and validate FinchLabs Roost authentication, sessions, and application-level permissions.
The FinchLabs fitness tracker application, based on the earlier FIPFT/FITFT work. Flightpath uses Roost for identity and access while keeping fitness data within the application.
The FinchLabs organization and Kanban application for managing projects, tasks, and workflow. LabBoard relies on Roost for identity and application-level access.
FinchLabs Works is the physical-systems arm of FinchLabs, focused on designing and building real-world devices that combine software, electronics, sensors, automation, and mechanical components.
A mobile, AI-powered computer-vision system with a trainable inference model that detects nuisance animals and uses non-lethal deterrence to encourage them to leave.
Critter Bouncer relies on Roost for authenticated access, user permissions, and secure API access to remote monitoring and control functions.
Don’t let critters crash your party
View Project OverviewNew FinchLabs applications and devices can register with Roost instead of building separate login and access systems.