Remora
Personal Commitment Manager.
An AISYNX product for organising subscriptions, bills, warranties, documents and renewals in one place — privacy-first, and built so that nothing is created without the user’s confirmation.
- Status
- In development
- Type
- AISYNX product
- Category
- Personal Commitment Manager
- Client
- AISYNX
Design concept with sample data, not a screenshot of a released product.
Important commitments shouldn’t be difficult to keep track of.
The problem
Personal obligations are scattered across apps, inboxes and paper.
A subscription renews from a receipt buried in email. A bill’s due date sits in a banking app. A warranty card is in a drawer, and the vehicle insurance renewal is in a PDF somewhere.
None of these is difficult on its own. The friction comes from keeping track of all of them at once — and the cost of missing one is usually a charge you did not intend, a late fee or a warranty you can no longer use.
Why we built it
Generic reminder apps treat every item the same, and finance apps ask for bank or card access most people are reluctant to give. Remora was conceived as something narrower: an affordable personal commitment manager that turns scattered obligations into confirmed commitments and protects people from forgetting them.
Its principles are deliberate. The user should not have to maintain another complicated app. AI is infrastructure, not the product. And privacy is treated as a feature in its own right.
Home should show what needs attention — not every item you own.
Who it’s for
The solution
Everything in Remora — a subscription, a bill, a document, a warranty, a renewal or a custom date — is a single kind of record: a commitment. Recurring commitments keep their full history of occurrences, so past payments and renewals are never overwritten.
The home screen is planned around urgency: expired and urgent items first, then the next 7 and 30 days, then financially significant items, then everything else.
Confirm, never assume
When AI extraction from documents or screenshots arrives, its output must be reviewed and explicitly confirmed before a commitment is created.
No bank credentials
Version 1 deliberately excludes bank, UPI and card integrations.
Works without AI
Manual entry is a first-class path, and core manual functionality is designed to work offline.
What’s built
Platform foundation
Monorepo with an Expo mobile app, NestJS API, background worker, PostgreSQL and Redis, running in Docker.
Database foundation
Schema and migrations for accounts, commitments and their recurring occurrences, with database-level rules for approved V1 decisions such as family access.
The product is at the end of its database foundation phase. None of the user-facing features below are available yet.
Product & engineering decisions
Money as decimals
Financial values use exact decimal types, never floating point.
Server-authoritative reminders
Reminder schedules are owned by the server so they stay consistent across devices.
Private storage only
Documents use signed, expiring URLs; large files never go into the database.
Provider-independent AI
The AI provider sits behind an abstraction so it can be changed without rewriting the product.
Technical approach
- React Native with Expo and Expo Router — no WebView
- NestJS API under /api/v1, with every resource authorised against its owner
- PostgreSQL with Prisma; Redis and BullMQ for background jobs
- S3-compatible object storage for documents
Current status
Remora is in early development. The platform and database foundation are complete and under review; user-facing features follow the roadmap below, phase by phase.
Development roadmap
Accounts & authentication
Registration, email verification, sign-in and password reset.
Commitment engine
Creating and managing commitments, types, statuses and occurrences.
Attention dashboard
A single home view of urgent and upcoming items.
Recurrence & reminders
Timezone-aware recurrence and server-scheduled reminders, then push notifications.
Documents & AI extraction
Secure document storage, then AI-assisted extraction that always requires user confirmation.
Offline mobile experience
Onboarding, home, items, add, scan, calendar and settings, with local data and sync.
Security, testing & release
Hardening, data export and deletion, full test coverage, then store preparation.
Planned work, in order. None of it is available yet, and timing depends on each phase passing its review.
Screens
Design concepts with sample data, not screenshots of a released product.
Building a product
of your own?
We bring the same problem-first approach to client products. Tell us what you want to build and we will help you scope a sensible first version.