Gmail
Read-only Gmail access is the core input.
Rellio analyzes billing and subscription emails without sending, editing, or deleting messages.
Integrations
Rellio keeps the integration surface intentionally small.
The product is most trustworthy when it depends on a narrow set of well-understood services. That keeps the data model coherent and the failure modes easier to explain.
Supported today
The platform intentionally depends on a short list of services.
Each integration exists to support the main subscription workflow rather than to expand the product into a general-purpose data platform.
Google sign-in
Google authentication keeps account access simple.
Sign-in uses the same identity surface as the inbox connection so the workflow stays familiar.
Stripe
Billing and plan management are handled through Stripe.
Paid access, plan changes, and payment methods live in the billing flow rather than in the subscription record itself.
Boundaries
Not every integration belongs in v1.
We prefer explicit constraints over vague promises. If a connector would weaken explainability or make ingestion less deterministic, it should wait.
Deliberate limits
No broad connector sprawl.
The product should stay good at subscription intelligence before it tries to become a generic platform for everything.
Future work
Any added integration must preserve the trust contract.
That means readable provenance, predictable ingestion, and a review step the user can still understand.
Have a connector question?
Ask before assuming the roadmap is wider than the product can support safely.
If you need a deeper integration story, tell us what data source you want to connect and why it matters to the trust model.