Everything that renews
Domains, hosting, software, maintenance, insurance and licences, with their cycle and notice period.
No renewal that takes you by surprise
Track domains, hosting and software before they renew, and decide in time to cancel.
Each domain tracks what it pays for again and again (domains, hosting, software, maintenance, insurance and licences) with vendor, account reference, responsible person, amount in INR or another currency, cycle (monthly to multi-year, or one-off), auto-renew and a notice period that gives the cancel-by date. Every upcoming renewal gets a decision (renew, cancel, renegotiate or review) with a reason, also through an expiring /d/<token> link emailed to the responsible person; "Renewed it" records the amount actually paid, moves the date on by the cycle and keeps the price history. A daily 10:00 IST cron rolls auto-renewed items forward, marks overdue ones, sends reminders 30, 14, 7 and 1 days before the cancel-by and renewal dates, and one team digest. RDAP lookups (rdap.org, no key) fill a domain's expiry date and registrar, refreshed weekly, and the portfolio domains can be added in one step. Views by due window, kind and vendor, a month calendar with an ICS feed, spend per month and financial year, CSV import and export, GET/POST /api/v1/renewals with an upsert by external reference for Contracts, webhooks, and Claude for a 90-day savings summary and vendor cancellation emails.
What Renewals does for you.
Domains, hosting, software, maintenance, insurance and licences, with their cycle and notice period.
Renew, cancel or renegotiate, also through an emailed link, with reminders before each deadline.
What is due each month and financial year, and how prices changed.
A suggested path for Renewals. What you can do depends on your access in the app.
Add items by hand or by CSV, or look up the portfolio domains.
Work through the needs-a-decision list before the cancel-by dates.
Enter the amount paid; the date moves on by the cycle.
Live host, inventory, governance, health checks, verification, dependencies and history.
Each domain tracks what it pays for again and again (domains, hosting, software, maintenance, insurance and licences) with vendor, account reference, responsible person, amount in INR or another currency, cycle (monthly to multi-year, or one-off), auto-renew and a notice period that gives the cancel-by date. Every upcoming renewal gets a decision (renew, cancel, renegotiate or review) with a reason, also through an expiring /d/<token> link emailed to the responsible person; "Renewed it" records the amount actually paid, moves the date on by the cycle and keeps the price history. A daily 10:00 IST cron rolls auto-renewed items forward, marks overdue ones, sends reminders 30, 14, 7 and 1 days before the cancel-by and renewal dates, and one team digest. RDAP lookups (rdap.org, no key) fill a domain's expiry date and registrar, refreshed weekly, and the portfolio domains can be added in one step. Views by due window, kind and vendor, a month calendar with an ICS feed, spend per month and financial year, CSV import and export, GET/POST /api/v1/renewals with an upsert by external reference for Contracts, webhooks, and Claude for a 90-day savings summary and vendor cancellation emails.
Contract terms belong to Contracts; paying the vendor stays outside; newsletter sign-ups belong to Subscriptions.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
renewals.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.