Nerd fest
Inside each system — subsystems and functionality.
These notes are intentionally high-level and do not expose customer-sensitive internals. They show the shape of each platform and the operational responsibilities IATRT carries.
Alabanos Taxi — multi-tenant fleet operations platform
Alabanos Taxi is a real customer system under active support: a live multi-tenant operational platform combining booking, dispatch, real-time monitoring, provisioning workflows, authenticated portals, SMS OTP, and business-system integrations.
Architecture & subsystems
- Multi-tenant platform structure supporting fleet and service workflows without treating each operational unit as a one-off build
- Real-time dispatch, monitoring, and status visibility for live taxi operations
- Provisioning engine for vehicles, drivers, and related operational entities
- Authenticated customer and administrator portals with role-aware workflows
- SMS OTP flows, booking management, dispatch logic, and supporting business automation
- Hosting, monitoring, support, maintenance, and staged change under an active operating model
Capability signals
- Operational platform, not brochureware
- Built for live users, real transactions, and supportable change
- Customer-facing and admin-facing interfaces under one accountable delivery path
- Documented handover, retained support, and long-life maintenance posture
Aesthetica By Andy — owned booking, CMS, and storefront
Aesthetica By Andy is a Darwin-based cosmetic-nursing practice that needed to escape a Square Online subscription stack. IATRT designed and built a custom site, booking flow, CMS, and storefront so the owner controls the platform end-to-end and pays for hosting instead of per-feature SaaS.
Architecture & subsystems
- Static frontend served by nginx with TLS, fronting a Flask-based booking and CMS backend
- Self-serve admin SPA for treatment cards, blog posts, gallery, and pre-treatment content — designed for a non-technical owner
- Calendar-backed booking integrated with the same shared mail and calendar infrastructure that runs the rest of the practice
- Customer accounts via Google sign-in, with magic-link fallbacks where useful
- Stripe-ready storefront for products and treatment packages, with placeholder keys until commercial cutover
- Postgres data store, structured uploads under a single media path, and operator-friendly admin telemetry
Capability signals
- Subscription-replacement build: owned software in place of recurring SaaS fees
- Designed for a non-technical operator — admin UX is obvious, forgiving, and documented
- Migration-aware: shares the same mail, calendar, and hosting backbone as other IATRT-managed systems
- Customer-owned IP, source, and design files with handover prepared from day one
PawAWhere — multi-tenant QR pet-tag SaaS
PawAWhere is a live consumer SaaS built and operated end-to-end by IATRT: customers buy QR-coded metal pet tags, claim them under an authenticated account, and pay a small per-tag subscription that keeps the lost-pet flow active. Vets, admins, finders, and owners all interact with the same platform under different roles.
Architecture & subsystems
- Next.js application served behind nginx, process-managed for zero-downtime reloads
- Postgres schema modelling tags, pets, owners, vets, transfers, and per-tag billing lifecycle
- Stripe checkout and webhooks for activation invoices, metal-tag upgrades, and renewal payments
- Per-tag subscription model — expiry lives on the tag, not on the user — with manual, automated monthly, and first-month-included cadences
- Auth.js with Google OAuth and magic-link email sign-in; role enum covering owner, vet, and admin
- Admin scope gated behind SMS-TOTP, with a session flag tracking elevated access
- Vet portal: read-only search across the whole pet database by chip, name, breed, owner contact, tag ID, label, or care notes
- In-process scheduler running expiry reminders, retention sweeps, and rotating IP-hash salts
- Weekly systemd-driven backup of database and uploads, retained off the application path
Capability signals
- True multi-tenant SaaS with billing lifecycle, not a brochure or single-tenant tool
- Real-money flows handled with Stripe, webhook reconciliation, and audit-friendly invoice records
- Privacy-aware design: hashed IPs with rotating salt, retention sweeps, and stranger-reclaim protections
- Operations-aware: scheduled jobs, backups, and structured logs are first-class, not afterthoughts
Why these matter together
- Three different industries — transport, cosmetic nursing, consumer pet safety — under the same delivery model
- Each one is a live system with paying users and ongoing IATRT involvement, not a launch-and-leave
- The same building blocks — authenticated portals, payment integration, scheduled jobs, structured handover — recombined to fit the operator
- Customer-owned IP across all three: source, design files, and credentials live with the operator, not behind a vendor wall