Client: Ainovaty (Internal)
Platform API
A unified backend platform that powers multiple Ainovaty products with domain isolation, real-time collaboration, background processing, and shared identity.
One API to run them all
As our product portfolio grew, we made a deliberate architectural decision: instead of separate backends per product, build one platform API capable of serving multiple apps in isolation. Every Ainovaty product — Habitracker, Subracker, and whatever comes next — runs on the same shared backend foundation.
Domain isolation by design
Each domain gets its own isolated data boundary:
- auth — sessions, users, passkeys, multi-app identity
- habits — tasks, streaks, completions, goals, gamification
- finance — subscriptions, transactions, budgets, accounts, exchange rates
- audio — tracks, providers, Jamendo/FMA sync, Minio storage
- issues — bug reports and user feedback
This is not row-level multi-tenancy. Domains are separated as hard boundaries, so cross-domain coupling stays low and each area can evolve safely.
One platform, many product domains
The platform covers the full product surface: authentication, habit tracking, community features, collaborative sessions, finance workflows, AI assistance, media, notifications, file handling, analytics, promotions, and internal tooling.
It is intentionally modular, so teams can ship in one domain without destabilizing others.
Coordination and scale
- Real-time delivery for live collaboration features such as sessions, messaging, and community activity
- Background processing for long-running or scheduled workflows such as reminders and reconciliation
- Domain events for clean coordination between product areas
Authentication
Identity supports passkeys, multi-factor flows, and app-scoped sessions from one shared account system.
Engineering principles
The core principles are clear boundaries, modular services, reliable real-time coordination, and a shared platform that can support multiple products without re-architecture.