Overview

Overview

The intry-mvp repository is the primary backend and tooling workspace for Intry. The Core API is an Express 5 + TypeScript service backed by PostgreSQL (Prisma) and Redis (BullMQ workers). Operational dashboards and proxies often run on Fly.io; the Core API is commonly deployed to Railway.

Request flow (buzzer → resident)

1. A visitor triggers the intercom / Twilio inbound webhook.
2. Core resolves the unit and virtual number (e164), loads residents, and notifies devices (push, SMS, or voice fallback depending on configuration).
3. The resident approves or denies from the app (or fallback channel).
4. Core signals Twilio (e.g. DTMF) to release the door; Call and Approval rows record the outcome.

Top-level layout

intry-mvp/
├── prisma/              # Database schema & migrations
├── src/
│   ├── server.ts        # HTTP entry
│   ├── workers.ts       # Background jobs (BullMQ)
│   ├── routes/          # HTTP routes (admin, twilio, access, …)
│   └── services/        # Domain logic
├── docs/                # Markdown guides, OpenAPI, runbooks
└── tools/               # Adjacent deployables (portal, app, admin, docs, …)

Tools you will touch most often

Related reading

• Tech stack — dependencies and vendors.
• Data model — Prisma entities and naming.
• API overview — how to call admin vs mobile-facing routes.