Renewal dates and external to-dos, clearly organized

Stop hiding important renewals across different platforms

Put subscriptions, domains, servers, and software licenses on one clear calendar. External alerts can join the same to-do list. You maintain the facts; TutuYes makes the next action visible.

See how it works
  • No bank connection
  • Original amounts preserved
  • Same capabilities on mobile
  • Disable or delete your records

Next actions

Next 30 days · 3 items

Monthly cost planning

$60

Review upcoming renewals

3

Integrations

Availability

Domain renewals

2026-08-01 · $12

Software licenses

2026-08-09 · $20

Infrastructure renewals

2026-08-20 · $28

Fewer steps make habits stick

A short path from record to action

Renewal list and calendar

Save with a name and next date; add cost, currency, and notes when useful. Lists drive action and calendars show timing.

Reminders in your inbox

Create to-dos from each reminder policy. Advance the next cycle after renewal or disable future in-app reminders.

Webhooks into to-dos

External systems create, update, or resolve to-dos through signed requests. Credentials can be revoked and rotated.

Scheduled HTTP Pull

When no webhook exists, read a count from a controlled HTTPS JSON endpoint with time, size, and destination bounds.

Start from a real use case

Not one page claiming to do everything

Each page answers one concrete question and states its workflow, boundary, and final responsibility.

SaaS subscription tracking

A renewal list for individuals and small teams.

Domain renewal reminders

Registrar, date, and purpose together.

Server renewals

Leave time to act before infrastructure expiry.

Multi-currency costs

Keep original values and plan on one basis.

Renewal calendar

Spot expiry clusters by month.

Webhook to-do

Turn external events into actionable state.

A three-step closed loop

Confirm the fact, then make the decision

  1. 1

    Record the next date

    Confirm it from the invoice, agreement, or service dashboard and start with minimum fields.

  2. 2

    Review in list or calendar

    See what is coming, its expected cost, and the context needed to decide.

  3. 3

    Complete it at the provider

    Renew, change, or cancel there, then update the record in TutuYes.

External integrations

Push when possible, pull when necessary

Choose the shorter path for each source: signed webhooks for immediate events, HTTP Pull for read-only APIs, and a dedicated Prometheus path for alert and recovery to-dos.

Webhook HTTP Pull

Webhook

Signed · create · update · resolve

HTTP Pull

HTTPS · JSON path · timeout · size limit

No illusion that automation did the final job

TutuYes does not read bank transactions or cancel at vendors. It organizes dates, costs, and external states you can verify. Upstream authentication has server-side storage boundaries, and pull requests have network and resource limits.

Security

Questions to answer before starting

Do I need to connect a bank or payment method?

No. TutuYes does not read transactions or charge you. You maintain amounts and dates from the actual invoice.

Does disabling a subscription stop vendor billing?

No. It stops future reminders here. Disable auto-renew or cancel at the original provider.

Does mobile have fewer features?

Core flows are not intentionally reduced. Responsive layouts keep the same actions and change their arrangement and density for narrow screens.

Can an external API failure break the whole page?

A pull failure becomes connection error state while existing records remain available. Later successful checks can recover; requests have time and size limits.

Start with the next thing that actually expires

You do not have to complete every detail now. Save the name and date, then add context later.