1 · Connect
Authorize Gmail read-only access.
Rellio uses the inbox as an input stream for billing signals. It cannot send, edit, or delete email.
How it works
Rellio keeps the path from email to subscription record narrow and explainable.
The platform is built around one rule: every useful state change should be traceable. That means deterministic ingestion, review-first handling of uncertainty, and async enrichment only after the core record exists.
Workflow
The system is shaped around four short steps.
Each step narrows ambiguity instead of expanding it. That is the difference between subscription intelligence and another inbox filter.
2 · Classify
Run the classifier before anything else.
Messages are evaluated for subscription intent first so deterministic behavior stays the default.
3 · Review
Keep ambiguous records visible until they are resolved.
The review queue is where confidence, evidence, and user judgment meet.
4 · Enrich
Use async AI enrichment only when the core record already exists.
AI adds context after ingestion. It never blocks the Gmail sync path or rewrites the source of truth.
Deterministic behavior
Why the pipeline stays stable when mailboxes are rescanned.
The service is built so repeated ingest runs do not create duplicate subscriptions or drift in state. That keeps review decisions meaningful instead of noisy.
Stability
Idempotent ingestion keeps the record set compact.
Subscription records are deduplicated and updated rather than recreated, which makes auditing easier over time.
Explainability
Confidence and evidence travel with the record.
People can see why a subscription was classified, why it is still uncertain, and what changed after review.
Ready to try it
Connect one inbox and inspect the full chain of reasoning.
If the workflow matches how you like to review spending, scale it up. If not, the evidence trail will make the mismatch obvious quickly.