Intry

Tech stack

Languages, frameworks, infrastructure, and third-party services used by Intry.

Overview

Intry is a TypeScript-first system: the Core API and most tools share Node.js runtimes, with mobile on Expo and several UIs on Next.js.

Core platform

LayerTechnology
RuntimeNode.js
HTTPExpress 5
ORMPrisma
DatabasePostgreSQL
Queue / workersRedis + BullMQ
Core deployRailway (typical)

Authentication & access

Use caseMechanism
Admin dashboard APIWorkOS SSO and/or Unkey API keys
Property managers / B2BClerk (clerkUserId on User)
ResidentsJWT + bcrypt (see registration routes)

Telephony & messaging

CapabilityProvider
Voice / buzzerTwilio Voice webhooks (/twilio/*)
Push (mobile)FCM (Android) and APNs (iOS)
SMS fallbacksTwilio (where enabled per user flags)

Billing & analytics

AreaServices
SubscriptionsStripe (webhooks in Core)
Product analyticsMixpanel, PostHog
APM / logsNew Relic (Core start script)

API surface

SurfaceBase pathConsumers
Admin/api/admin/*Admin SPA, MCP, internal tools
Twilio/twilio/*Twilio callbacks
Access / devices / registration/access/*, /devices/*, /registration/*Mobile apps

Frontends & tools

AppStackHosting (typical)
Admin SPAHTML + Tailwind (CDN) via proxyFly.io (intry-admin)
PortalNext.js + ClerkVercel / Fly / custom
MobileExpo / React NativeEAS builds
Prop1Vite + React + ExpressFly.io (separate DB)

Configuration

  • Multi-environment admin: proxy sends X-Admin-Env: DEV, TEST, STAGING, or PROD to route to the correct Core base URL.
  • Secrets: Never commit .env; use platform secrets (Railway, Fly, Vercel) per environment.

On this page