Project Trident

Why it exists

FINNS welcomes about 1.3 million guests a year, and almost none of them are known to us when they walk in. Trident turns them into members: they sign in once, and from then on each booking, gate check-in and in-app activity is tied to that one member and earns points.

The platform at a glance

People

GuestMember once signed in

StaffGuest services, admins

Touchpoints

FINNS PassApple/Google Wallet

Guest appFlutter (mobile app + web)

Booking websiteCTG

Gate scannerVendor TBD

Admin consoleSvelteKit

Trident platform

API

LoyaltyPoints ledger and membership

AssetsWallet balance, wristbands

AccessesGym

Relationships

ReservationsEvents

Transactions

Customer PII

Services

Guest identityKeycloak

Staff identityJumpCloud

Transactional emailAmazon SES

Payment gatewayAirwallex

POSShiji

PMSDaylight

Customer engagementSota Platforms

CDPInsider

In this portal

Start hereWhat Trident is, how guests sign in, and the conventions every integration follows.Read ArchitectureThe system landscape, deployment, data model, points ledger and security model.Read Our servicesCore, the guest app and the admin console, down to the tech stack.Read External servicesGuest and staff identity, payments and POS: what each is for and which vendor provides it.Read Booking engineSigning members in from the app, and earning points on paid bookings.Read Customer engagementPartner widgets inside the app, and the Points API behind them.Read Gate & check-inChecking members in with a one-time QR, and the points it earns.Read Project ManagementFrom the vendor brief to the platform: scope, horizons and the decisions still open.Read