Keeper: every entry to the community authorised and logged, without the gatehouse notebook
1.53 million visits logged on the platform, 2,500 active users across more than 500 houses, and resident onboarding that takes 40% less time. The platform dates from 2019; I have been its CTO since February 2024.
- Sector
- Residential communities
- Role
- CTO
- My part
- Since 2024: I kept a single Flutter codebase, added the analytics layer and prioritised faster resident onboarding.
- Period
- February 2024 to present. The platform dates from 2019.
- Status
- In production. App on version 3.1.0
- Team
- A small team, with a single mobile codebase
System blueprint
The flow, in text
- The resident announces a visitor from the app.
- The visitor receives a QR pass.
- The concierge scans the pass at the gate.
- The entry is logged: 1.53 million visits so far. Underneath, the platform: a Flutter app and an API in production since 2019.
Platform: Flutter app · Node.js and MongoDB API, in production since 2019 · Diagram. Not live data.
Product in use
Problem and constraints
Every day a residential community gets visitors, deliveries, tradespeople and, now and then, an emergency. In many of them that is still written in a notebook at the gatehouse, and the resident finds out over an intercom.
Keeper puts residents and concierges in the same app so that every entry is authorised and recorded: a resident announces a visitor and sends them a QR pass, the concierge scans it at the gate, and the entry goes into the history.
Constraints
- A small team cannot sustain two native apps.
- Queries over 1.53 million visits must not load the day-to-day operation.
Decisions and architecture
When I took over as CTO, my priority was making it quick for a new community to get onto Keeper: resident onboarding now takes 40% less time.
I kept a single Flutter codebase for iOS and Android, with BLoC for state, instead of two native apps a small team cannot sustain.
I added a separate analytics layer, a Next.js app that reads from MongoDB, so that managers’ queries over the full visit history do not load the day-to-day operation.
The API has been in production since 2019, on Node.js (Fastify and Express) and MongoDB, with Google Cloud Tasks, SendGrid and Sentry for monitoring. The app uses Firestore, push messaging, Crashlytics, Remote Config and a QR scanner. Payments go through Webpay and the admin panel is Angular.
The same app also covers panic alerts, polls and notices from management, which reach the phone as push notifications.
Results
Keeper has 2,500 active users across more than 500 houses, and its visits collection holds 1.53 million records. The iOS and Android app is on version 3.1.0.
Keeper was selected for Startup Chile’s Ignite programme, BIG 6 generation, in August 2023. It belongs to Blanco Brand, but it is a separate company.
- 1.53Mvisits logged on the platform. These are logged entries, not users.
- 2,500active users across more than 500 houses.
- −40%time to onboard a resident.
Limits
- The platform and its API date from 2019: I did not build them from scratch; I have run them since 2024.
- Visits are logged entries, not users.
Do you have a system that cannot be touched?
Tell me the problemWant the full career history?
View the CV