Seven domain-management products: feature inventory and Roster.Domains opportunities

Reviewed 2026-09-05. Purpose: a comprehensive, source-linked breakdown of the features discovered on the seven requested vendors' public sites, documentation, pricing, release notes, and available demonstrations; an explanation of their workflows; and a capability-level assessment of how Roster.Domains could adopt equivalent ideas.

The seven products are Lemon Domains, Domain Locker, Watch My Domains Desktop, domainnotifications.com, DomainBook Pro, Efty Investor, and TLDops. DomainMOD and other alternatives were not added to this review. Related Server Edition and Efty Pay/distribution capabilities are explicitly separated from the original product where the vendor's own site covers them.

Reading the evidence

• Observed: a public page or demonstration actually displayed the behavior described. DomainBook's demo is explicitly synthetic and read-only; this establishes screen structure, not working account integrations or correct financial results.
• Documented: a specific vendor guide or reference describes the feature. It may still require a paid account, configuration, supported provider, or plan.
• Advertised: marketing lists a capability without enough procedural or runtime evidence to verify its depth.
• Planned/conflicting: a page marks it coming soon, or official pages disagree. The discrepancy is preserved rather than resolved by guessing.
• Candidate adoption: our own product analysis. It is not an approved implementation plan, cost forecast, provider-eligibility assessment, or change to Roster's current free-product direction.

The review covers publicly discoverable feature families and the meaningful detailed controls found within them. It cannot certify undisclosed features behind paid accounts. No real portfolios were imported, registrar connections configured, messages sent, offers made, or purchases performed. Domain Locker's vendor-provided demo login was attempted once and failed because that demo had exceeded its database quota. Several late browser navigations failed when the shared browser stopped responding; those coverage gaps are listed in the relevant sections.

What each product contributes

The detailed inventories follow. The final section consolidates the overlaps into one Roster.Domains capability map, so seven vendors do not become seven duplicated development backlogs.

Lemon Domains and Domain Locker research

Read-only review completed September 5, 2026, covering public feature/pricing pages, linked documentation, individual tools, and relevant official source. Features below are documented or advertised, not fully tested inside paid accounts.

Three major Lemon corrections emerged: email/webhook reminders are planned; OAuth connectors for ChatGPT/Claude Desktop are planned; MCP tokens currently grant full read/write despite homepage claims of read-only scopes.

Lemon Domains

Positioning and price: A portfolio organizer centered on registrar accounts, project grouping, expiry visibility, and AI access. Currently $0 with unlimited domains/projects and no per-seat fees. Future premium examples include audit-log export, SAML, and advanced automation; the vendor says core personal use will remain free. Pricing

Portfolio features and workflows

Typical flow: Create an account → create registrar/account labels and projects → paste/upload domains → check the preview → review expiry windows and auto-renew information → make renewal decisions at the registrar → refresh/reconcile the portfolio. Lemon explicitly does not renew domains itself. Renewal workflow

Registrar coverage: do not confuse directory coverage with integration coverage

The integration directory lists 50 registrars, but says the additional 47 are supported by paste or CSV. GoDaddy, Porkbun, and Namecheap are described as “first-class.” Each of those three detailed guides nevertheless teaches copying/exporting the registrar list and importing it into Lemon, with no API configuration steps. Therefore:

• Cross-registrar recordkeeping/import is well documented.
• Monthly auto-sync is advertised.
• Universal account synchronization, provider coverage, credential permissions, and auto-renew accuracy remain unverified.
• Their “all registrars supported” claim should not become “50 working API adapters” in our comparison.

Sources: directory, GoDaddy, Porkbun, Namecheap.

AI/MCP capabilities

The reference lists 21 tools:

• Domains: list, fetch one, add, update, delete, bulk add, and expiring-soon query.
• Projects: list, add, update, delete.
• Registrars: list, add, update, delete.
• Registrar accounts: list, add, update, delete.
• Sync: recent logs and latest session/checklist.

Bulk add accepts 200 domains, returning successful rows and individual errors. Lists support pagination, summary/full fields, and a maximum of 500 results. Notes are limited to 2,000 characters. Expiry queries can optionally include already-expired records. Project/registrar/account deletions can cascade; those tools require an explicit confirmation argument. Registrar credentials cannot be set or exposed through MCP. Tool reference

The server uses remote Streamable HTTP and Bearer tokens. Available documented clients include Claude Code, Cursor, Windsurf, Zed, and compatible custom clients. Tokens can expire after 30 days, 90 days, one year, or never; the token is shown once, hashed, and revocable. Project permissions still apply. Requests have a 60-second timeout. MCP page, authentication, limits

Important discrepancies:

Sources: limits, authentication, renewal tracker.

Complete public tool suite

These are separate public tools, not evidence that every check becomes continuously monitored inside the portfolio. The descriptions/forms were inspected without submitting real domain scans.

Application to Roster.Domains — analysis, not approved implementation

• Fits existing direction: make renewal decisions clearer with keep/review/drop intent, reason, review date, known annual cost, and source/last-verified labels. Strengthen filtered exports and account labels. This extends the existing documented roster; it does not prove current runtime readiness.
• Useful extension: projects/client folders with explicit memberships and viewer/editor/owner permissions. Keep labels and actual access-control boundaries separate; changing a tag must never grant access.
• Useful extension: a sync center listing each provider/account’s last success, coverage, failed fields, and next retry, preserving reviewed user values.
• Separately scope MCP: reuse authorized portfolio operations behind revocable, genuinely scoped tokens. Begin with read-only queries; writes require ownership checks, previewable changes, audit events, and bounded bulk operations.
• Separately scope tools: public tools need rate limits, abuse budgets, and truthful unknown states. Add TLD-cost reference or email-configuration diagnostics only where they support portfolio decisions.
• Outside current foundation: valuation and name acquisition/generation. Their presence on a competitor’s site does not justify copying them into the renewal product.

Domain Locker

Positioning: A domain inventory combined with technical asset discovery, historical changes, alerts, and website health.

Hosted annual prices: Free: 5 domains; Hobby: 20 domains for $60/year; Pro: 100 domains for $240/year. Hobby includes change history, statistics, and notifications; website monitoring is Pro. Self-hosted code is free but requires infrastructure/maintenance, and some hosted channels/features need additional services. Pricing

Core workflow and inventory

Paste a domain → fetch public registration/DNS/TLS/host information → review or complete fields → configure desired notifications → save → examine the portfolio or individual asset views → receive scheduled refresh/change/expiry information.

No registrar password, ownership verification, website installation, or domain modification is required for its documented public-data lookup. Initial enrichment may take approximately 30 seconds. The portfolio has configurable visible fields and individual detail/edit/delete routes. Domain guide, add-domain workflow

The non-guide inventory above is supported by the feature page, official repository, and feature configuration. Source existence is not proof of the running hosted version.

Notifications in detail

The documented selectable events are:

• Domain expiry.
• IP address changes.
• Registrar changes.
• WHOIS changes.
• DNS additions/removals/amendments.
• TLS expiry.
• TLS certificate changes.
• Host changes.
• Security-feature changes.

Preferences can be edited per domain or in a bulk event editor. Self-hosted reminder offsets default to 90, 30, 7, and 2 days, with operator customization. Its documentation warns that failed DNS fetches can generate false positives and that auto-renewing certificates/CDN IPs can create excessive change notices. Notification documentation

Hosted marketing mentions email, push, webhook, Telegram, Signal and additional messaging channels; developer documentation mentions SMS/WhatsApp and associated services. Exact channel entitlement and successful delivery remain unverified. Self-hosted basic alerts use webhooks, with ntfy documented as a push route. Features, notifications, architecture

Important limits and contradictions

1. Subdomain discovery is not exhaustive DNS enumeration. The detailed fetching/troubleshooting pages say it needs DNSDumpster and/or Shodan integration; no configured provider means discovery is disabled. This qualifies the simpler “automatically scan DNS” feature copy. Fetching configuration, troubleshooting

2. Some TLD data cannot be obtained. Detailed docs require manually entering missing registrar/expiry before saving, while the general registrar guide says fetched registrar information is not editable. Those are different documented stages, and the full correction workflow could not be tested. Fetching configuration

3. API/feed maturity is unclear. The feature page marks API, Prometheus, iCal, RSS and widgets “coming soon”; the repository advertises programmatic REST/GraphQL access. Do not count the whole list as delivered hosted functionality. Features, repository

4. Self-hosted does not equal hosted Pro with no setup. Pricing says Pro features, but also flags channel limitations. The default self-hosted edition lacks authentication according to its deployment guide. The current source configuration sets 500 self-hosted domains and disables social login/hosted notification channels by default; code customization is possible. Self-hosting, source configuration

5. Public demo was unavailable. One login attempt with the vendor’s published prefilled demo credentials failed with exceed_db_size_quota. The screen said the project owner must change its plan/spend restriction. This proves a demo access failure, not a failure of paid production accounts. Public demo

Application to Roster.Domains — analysis, not approved implementation

• Best fit: cross-domain views for nameservers, MX providers, certificates, registrar accounts, and expiring assets. Reuse existing opt-in observations rather than fetch the same data separately for every screen.
• Best fit: retain dated snapshots and show meaningful before/after differences. A timeout must become check failed, not record removed.
• Useful extension: per-event notification preferences, bulk settings, digesting, deduplication, and clear delivery status. Email plus calendar are a practical initial scope; SMS/messaging adds recurring vendor and support costs.
• Useful extension: TLS expiry and provider-concentration views, with confidence labels for CDN/host inference.
• Separately scope: uptime monitoring, frequent checks, long time-series retention, and subdomain-discovery providers. These create a different operational workload from renewal management.
• Preserve Roster’s boundaries: provider observations must remain distinct from user-entered renewal deadlines/costs; public registration facts do not establish auto-renew, registrar-account access, or private ownership.
• Do not copy the self-hosted authentication model into a multi-user private SaaS. Clerk identity and Roster-owned authorization remain necessary.
• Within a $99 annual price constraint: inexpensive organization, review decisions, clear costs, cached observations, history, and bounded reminders are the strongest candidates. Unlimited high-frequency monitoring, SMS, and third-party intelligence should not be promised without measured per-portfolio costs.

No project files, real accounts, saved demo data, registrar connections, or domain scans were created or changed. This research artifact was saved outside project source as the requested review deliverable.

Watch My Domains Desktop and domainnotifications.com

Completed read-only review of Watch My Domains Desktop / DomainPunch and domainnotifications.com. No accounts, installations, purchases, messages, project changes, or form submissions.

Evidence boundary: Features below are documented vendor capabilities. I inspected public pages and the annual-pricing interaction, but did not test the desktop executable, logged-in workspaces, reminder delivery, or registrar integrations.

Watch My Domains Desktop

This is a local Windows/macOS domain inventory and monitoring application, built around a configurable table backed by local data files. It is distinct from the vendor’s browser-based Watch My Domains SED / Server Edition and the discontinued Watch My Domains Pro, Domain Punch Pro, and Watch My Domains ISP products.

Documented feature inventory and operation

Important documentation conflict: the site/TLS manual says those checks must be initiated manually. The newer October 2025 changelog adds optional automatic website/TLS checks, followed by configurable recheck intervals in June 2026. The current changelog should take precedence. Older manual, current changelog

Editions and budget

These are single-user software licence prices, not confirmed annual SaaS prices. The introductory offer is described as primarily intended for customers of older products. Edition comparison, purchase page

Server Edition features must remain separate

The same vendor’s Server Edition adds always-on hosted/self-hosted operation, subdomain DNS monitoring, DNS-change alerts, email alerts, webhooks, granular user permissions, SAML/SSO, external application API access and configurable reports. The Desktop comparison explicitly marks these absent from Desktop. Comparison

The current SED page additionally advertises audit logging, category and column permissions, scheduled reports, priority lookup queues, custom fields, bulk edits, TXT/SPF/DMARC/selected DKIM data, TLS SAN information, accessibility scanning, Lighthouse reports, interface branding and multiple databases. Enterprise editions offer source access. Managed deployment starts at $60/month, well outside the proposed annual budget. These are separate-product capabilities, not features supplied by Desktop Business. SED capabilities

What Roster.Domains could adopt

The strongest transferable ideas are saved views, clear risk indicators, configurable columns and protection of manual data, rather than reproducing a desktop application or the whole enterprise Server product.

domainnotifications.com

This is a hosted, registrar-independent inventory, collaboration and renewal-reminder workspace. Its core is manually maintained/imported operational records connected to reminders. The public material does not establish automatic registrar account synchronization or live DNS/TLS scanning.

Documented feature inventory and operation

Explicit boundary: renewals, transfers, payments and DNS changes happen at the controlling providers. The application tracks their operational context. “Monitoring” should not be interpreted as verified automatic data refresh from every registrar. Homepage FAQ

Annual price and plan gates

I clicked the public Yearly pricing tab and read the updated pricing section.

VAT excluded. Monthly prices are $19.99/$39.99. A displayed 50%-off-first-subscription code could bring Pro to approximately $99.95 for the first annual term if applicable; checkout eligibility was not verified and this is not a continuing $99/year offer. Official pricing

What Roster.Domains could adopt

The most useful lesson is connecting each renewal to its owner, customer, hosting dependency, cost and delivery history.

Coverage and limitations

• Desktop: homepage; comparison; purchase page; current changelog; all linked Desktop guide sections covering introduction, categories, saved defaults, import, filtering, lookups, DNS, website/TLS, queries, table, display groups, alerts, edits, columns, backups and themes; Desktop-versus-Server comparison; SED capability page.
• domainnotifications.com: homepage including FAQs and monthly/yearly pricing; portfolio, reminders, agencies and IT product pages; blog index; eight detailed articles covering import, inventory, hosting, customers, custom attributes, Slack, costs and privacy.
• Four additional repetitive workflow articles remained unreviewed after a browser navigation timed out. No claim of access to private documentation or every authenticated feature.
• All Roster suggestions are research recommendations requiring an approved plan, not implementation decisions or claims about current verified functionality.

Additional reviewed sources

• Desktop guide index
• Desktop introduction
• Desktop alerts
• DomainNotifications IT workflow
• DomainNotifications blog index
• Maintainable inventory guide
• Slack reminders guide

DomainBook Pro and Efty Investor: competitor feature research

Research date: September 5, 2026. Research deliverable only; no implementation authorization.

Research complete with evidence limits: DomainBook Pro was inspected in its explicitly read-only public demo; Efty was reviewed through official product pages, all eight Investor help categories, detailed articles, recent releases, API documentation, and its vendor-linked public landing-page example. No accounts, purchases, imports, live scans, messages, or persistent product changes were made.

DomainBook Pro

Its main purpose is investor/broker recordkeeping, renewal decisions, and portfolio economics. Current published pricing remains $20/month for unlimited domains, with a seven-day trial and no card required. That is $240/year at monthly pricing, above $99. No annual discount was found. Product, features, pricing and FAQ

Sources: public demo, active domains, registrar overview, integration screen, release history.

Sources: renewals and review demo, watchlist demo, reputation demo, settings demo, integration screen, product FAQ.

Sources: reports demo, sold ledger, dropped ledger, valuation explanation, ROI calculator, price comparison, renewal strategy, release history.

Important DomainBook findings

• Homepage integration list is stale relative to both release history and demo.
• Demo clearly says its brokerage and records are fake. Future-dated sale records and computed totals prove screen structure, not financial correctness.
• Demo displays version 1.42.0 while latest public changelog entry reviewed is 1.41.0.
• No public general-purpose DomainBook API or SDK documentation was found. Outgoing webhooks are documented.
• Network Solutions and Afternic cards explain manual/export alternatives. Treat the cards’ claims about those providers as DomainBook’s statements, not an independent provider-capability assessment.
• No reliability, synchronization, export contents, email delivery, valuation accuracy, role isolation or security implementation was tested.

What Roster can borrow: the strongest adjacent ideas are account-level renewal totals, named registrar connections, record-source visibility, preserved manual pricing, a review queue for detected changes, customizable table columns, quarterly renewal decisions, useful CSV/Excel exports and configurable digest/notification channels. A transaction ledger is needed before claiming real historical cost basis. AI valuations, watchlists for acquisition, Sedo writes and payment/lander functions are separate scope.

Efty Investor

Efty is a broader domain selling operation: portfolio records feed public landers, a branded shop, leads, payment services and distribution. Its current root website is buyer-oriented; Investor has a separate product page. Investor product

Current monthly prices are Basic $22/50 domains; Launch $29/100; Starter $34/500; Growth $49/1,500; Scale $69/2,500; Professional $89/5,000; Professional Plus $149/10,000; Enterprise $249/25,000. Annual billing advertises 16% savings; the browser annual toggle could not be verified because the pricing page remained on Cloudflare verification. Even the discounted entry tier is above $99/year. Basic/Launch/Starter include landers, shop, DNS, payment integrations, financial insights and Smart Tools. Growth/Scale add chat, Mailchimp, UserWay and Zapier; Professional/Professional Plus add Stripe and white-labeling; Enterprise adds priority support. Current pricing

Sources: bulk import workflow, complete template field definitions, bulk editor, WHOIS refresh, ownership review, exports, preferences.

Sources: lander setup, customization, Smart Landers overview, formats, forms, shortcodes, custom CSS, redirect options, TLS, TXT/MX, Arctic/Moonshot release, public lander.

Sources: shop setup, shop settings, featured ordering, categories, Arctic shop release, analytics, spam, verification, Smart Tools/token limits, Lead Score release, integrations catalog, Zapier, consent.

Efty ecosystem features requiring separation from Investor

• Public marketplace: subscription portfolios are listed by default according to help, with hide/show and profile privacy controls. Latest marketplace offers keyword plus AI concept/intent search. Roster should never copy this default for private inventories. Listing behavior, hide controls, 2026 marketplace release
• Payments: personal shops/landers support Efty Pay, Escrow.com, PayPal and gated Stripe. Efty.com BIN exclusively uses Efty Pay; absent Pay onboarding, listings become make-offer. Paypal hands buyers to PayPal and leaves domain delivery with the seller; Escrow.com hands over to its transaction wizard. BIN policy, PayPal, Escrow, Stripe
• Efty Pay: separately onboarded service for buyer payment, seller verification, holding/transfer workflow, transaction communications and payouts. Imported leads can be entered after agreeing terms. It has transaction commissions separate from Investor subscriptions. Pay product, initiate transaction workflow
• Lease-to-own: current release covers marketplace, imported deals, landers and Domain Shop. Account-level duration/down-payment settings, enable/disable, and per-domain overrides; CSV documents maximum 48 installments. April release introduced percentage down payments at account level, while per-domain settings remain fixed amounts. LTO rollout
• Distribution: approved partners publish eligible marketplace inventory; BIN distribution requires a price and completed Pay onboarding. It is a partner network, not an included unrestricted feed for every subscriber. Distribution product, eligibility
• Developer API: official Node/PHP SDKs concern Efty Pay, with access credentials requested separately. API families cover transactions, buyers/sellers, messages and onboarding. No open Investor-wide CRUD API was established. Official SDK, API catalog

Roster adoption implications

1. Directly adjacent: preview-before-commit CSV updates, error downloads, domain categories, visible refresh dates, bulk edit/review, filtered exports, archived/sold/dropped lifecycle records where approved, and renewal/cost reporting.
2. Worth a separate proposal: ledger-based cost history, authenticated official registrar synchronization, saved table preferences, notification channels, explainable renewal triage and opt-in technical reputation checks.
3. Separate product direction: public shop/landers, lead CRM, buyer scoring, AI listing copy/valuation, marketplace distribution, DNS writes, payments and LTO. These create buyer data, publication, transfer/support and transaction operations well beyond the approved private renewal roster.
4. Best transferable interaction: Efty’s staged import and DomainBook’s detected-change review. Preserve user edits, provenance and explicit approval rather than importing their marketing promises.
5. $99/year: both competitors exceed it. A Roster offering at that eventual price would need bounded domains, refresh jobs and notification/AI usage assumptions; the present research does not authorize pricing or billing changes.

Coverage and remaining evidence limits

DomainBook: homepage, full current changelog, four official guides, both public tools, demo Dashboard, Domains, Registrars, Integrations, Reports, Renewals, Watchlist, Reputation, Settings, Sold and Dropped. Domain Search navigation was reached but detailed final read was blocked when the shared browser became busy. Support page was not verified. The two additional guides read are portfolio tracking and selling domains.

Efty: all eight Investor category indexes were catalogued: Integrations, Account basics, Marketplace, Smart Landers page 1 and page 2, Landers, Shop, Portfolio, Billing.

Additional substantive articles read:

• Smart Lander basics, settings, elements, languages, assignment, meta, footer.
• Custom lander domain, subdomain, minimum offer, shop BIN.
• Tawk, WhatsApp, Mailchimp, UserWay.
• Deletion, billing timing, plan changes, cancellation.

Efty paid interface, current annual total, exact AI allowances, integration reliability, renewal notification delivery, financial formulas, and security/role enforcement remain unverified. One profile-privacy article returned HTTP 429. Current docs conflict on selected-row limits, older transaction currencies and deprecated Dan shortcodes; do not flatten all historical claims into current capabilities. The shared browser eventually stopped responding; it was not restarted.

TLDops: detailed feature review

Research date: 2026-09-05. Purpose: document the public product's features, working model, limitations, and candidate applications to Roster.Domains. This is a report-only competitor review. Availability statements are vendor documentation unless explicitly described as observed. No TLDops account, provider connection, scan, or external change was created.

TLDops is primarily an operations and governance product for agencies, IT, security, and multi-brand teams. It organizes domains around what services they support, who is responsible, what has changed, and what requires action. This differs from a domain-investor sales ledger.

Portfolio and onboarding

Sources: platform, pricing feature inventory, home.

Technical observations, history, and findings

The detailed correlated-rule reference currently lists four patterns: email domains without both SPF and DMARC; possible dangling CNAMEs in active families; expiration within 30 days with no operational/legal owner; and domain families fragmented across both registrars and DNS providers. It describes severity elevation and hiding fully absorbed duplicate contributors. Treat the vendor's strong security language as interpretation, not verified impact.

Sources: platform, correlated findings, transparency.

Governance, reporting, and account features

Sources: platform, security, transparency, pricing.

Provider connections and proposed writes

The general product works from public observations. Optional provider connections are intended to replace inferred/manual information with account-authoritative data. A DNS zone list and a registered-domain inventory remain different operations.

Sources: integration directory, Cloudflare DNS, Cloudflare Registrar, Porkbun, Namecheap, Domeneshop, Route 53.

The detailed write workflow is: propose a current-to-new diff with a 14-day expiry; review pending/approved/applied/failed/expired/dismissed proposals; approve/apply under one-person or enforced two-person rules; execute and record provider result followed by fresh sync; offer reversal as another proposal with its own approval. It also describes deduplicated reverts, missing-scope errors, a DNS-write kill switch, and auto-renew/lock posture rules that generate proposals but never auto-apply. Bulk proposals succeed/fail individually rather than as one external atomic transaction.

Availability caution: the platform and detailed write reference describe live Cloudflare writes, while pricing says writes will ship later and security/transparency still use observation-only/future language. Report this as a documented capability with contradictory availability evidence, not a hands-on verified integration. These pages cannot establish actual provider API permissions, account eligibility, or a working end-to-end implementation. Write workflow

For Roster, this is a possible future governance pattern. Registrar credentials, DNS changes, renewals, transfer locks, and auto-renew writes require separate product and integration scope. We did not perform an official-provider SDK/API feasibility study in this seven-site review; those checks are required before an implementation decision.

Public tools and educational surfaces

The tool directory lists Domain Health Check, DNS Lookup with filtering/export, SPF Record Check, DMARC Record Check, MX Record Lookup, DNSSEC Check, New gTLD Operational Readiness Check, and a domain scanner producing a persistent infrastructure report. The site also has learning guides, direct-answer pages, glossaries, service/record/issue/provider/verification references, and aggregate State of DNS views with annual archives and TLD slices. These were reviewed as public product surfaces; no checks were submitted. The specialized new-gTLD readiness checker is distant from Roster's current renewal workflow.

Sources: tools, documentation hub.

Plans, economics, and evidence limits

The vendor says feature access is shared across plans while volume, team/client capacity, and support targets vary. Response/resolution targets are measured during European weekday business hours. This is not evidence that a $99/year product can economically promise the same monitoring, support, and agency capacity. Pricing

Rendered pages reviewed successfully: home, platform, documentation hub, integrations directory, all six provider pages, proposed-write reference, correlated-findings reference, pricing, security, transparency, and tools. No authenticated application or live-provider workflow was exercised. A final attempt to read the issue/service reference indexes encountered a busy browser daemon and was stopped; those catalogs are not counted as fully reviewed. Broad feature families were already described by the platform and reference pages above.

The strongest Roster candidates are responsibility fields, evidence-backed findings, reviewable change history, ownership/freshness completeness, and useful reports. DNS writes, external AI interpretation, agency access, and advanced API/governance features are separate candidates, not approved implementation work.

How these capabilities could fit Roster.Domains

This section is our synthesis from the seven reviews. It describes ways to add equivalent user value, not a decision to copy vendor software, change the product's pricing, or begin implementation.

Start from the actual documented foundation

The current implementation-status document records local implementations of CSV/paste normalization and conflict review; a private domain roster, search and bulk editing; renewal/cost views; purpose/tags/notes; RDAP observations and a bounded worker; explicit review/adoption of observations; opt-in DNS/TLS/MX; reminders/calendar; and exports/history. It also records material outstanding evidence for real identity, provider coverage, email delivery, and hosted deployment.

That is a useful foundation, not a claim that these features are already production-ready. This review did not audit the application source or rerun its tests. Existing features should be extended and verified rather than recreated simply because a competitor gives them a different name.

Consolidated capability map

Each row is one capability family, even where several competitors implement it. Relative running-cost descriptions are qualitative engineering judgments, not measured forecasts.

Features that would create a separate product operation

The following ideas were fully included in the vendor inventory but should not be treated as small additions to the current private renewal roster:

Security/privacy distinctions are grounded in the current project provider policy and security requirements. No official registrar SDK, live-account or transaction-provider feasibility review was performed beyond the seven vendors' published claims.

A coherent workflow to borrow

An illustrative future user journey combining the useful ideas is:

1. Bring records in. Paste or import an official export, associate a registrar account/project, and resolve duplicate/conflicting rows before saving.
2. See data quality. Display actual renewal deadline and cost where known, public observations separately, missing responsibility, and last successful checks.
3. Review a useful queue. Present approaching deadlines, changes, missing values and meaningful technical findings, each with evidence and a specific action.
4. Decide deliberately. Record keep/review/drop intent, reason, decision owner and next-review date. Actual renewals still happen at the registrar unless a future write feature is separately approved.
5. Know the exposure. Show exact known upcoming cost, unknown-cost count, and separately identified shared hosting obligations. Do not add mixed currencies without a labeled conversion basis.
6. Notify the responsible person. Preview timing and recipients, send through verified channels, preserve delivery history, and reconcile uncertain outcomes safely.
7. Hand over cleanly. Export the selected project/client/portfolio with deadlines, responsibility, provenance, coverage gaps and change history.

This is a product-research sketch, not the project's required office-hours/autoplan cycle or approval to implement it.

Priorities under a possible $99/year price point

$99/year is $8.25/month in gross subscription revenue before payment costs, infrastructure, support, taxes and other expenses. That arithmetic is not a profitability model. The current project direction remains free unless explicitly changed; this review does not introduce billing.

First candidates to investigate: saved views/columns, named accounts and responsibility, clearer renewal decision/review states, accurate cost coverage, meaningful history, and useful exports. They provide recurring value using mostly existing stored data.

Next candidates after the existing live paths are proven: reminder inheritance and delivery evidence, official registrar adapters, client/project access, hosting-plan records, bounded custom fields and technical asset grouping. These involve more support and data integrity work, but directly serve portfolio management.

Candidates that need a separate measured business case: unlimited frequent monitoring, SMS, arbitrary subdomain discovery, large AI workloads, price/intelligence feeds, enterprise support commitments, and public sales/transaction operations. A published domain cap, refresh/retention policy and channel budget would need measured workload evidence. We have not determined a defensible numerical allowance in this research.

Material corrections to the earlier high-level comparison

• Lemon's detailed documentation says email/webhook reminders, some OAuth-based AI connectors, and granular MCP token scopes are not yet delivered. Its current token documentation describes full read/write access. Broad home-page language should not be reused as verified capability.
• Domain Locker's rich hosted feature list does not establish that every self-hosted capability/channel works without configuration. Its public demo quota failure limited hands-on verification.
• Watch My Domains Desktop is distinct from its Server Edition and retired products. Its changelog supersedes older scheduling instructions; Desktop Enterprise is still described as under development.
• domainnotifications.com's normal annual Pro price is $199.90. A first-term promotion is not a lasting $99/year offer, and custom fields/private-record features have plan gates.
• DomainBook's changelog/demo extends the homepage's registrar list; its 'drop-catch' description is monitoring, not demonstrated automatic acquisition. Valuations and financial calculations were not validated against real transactions.
• Efty combines several distinct products and flows. Its documented WHOIS update workflow is manual after initial import; its payment SDK is for Efty Pay, not proof of a general Investor API. Marketplace publication defaults should never be inherited by private Roster portfolios.
• TLDops has inconsistent official statements about Route 53 and provider writes. Its detailed governance design is useful research, but actual operation and provider eligibility remain unverified.

The opportunity suggested by this review is to make a private portfolio dependable enough to act on: what needs review, who is responsible, what it will cost, what changed, and how certain the underlying information is. That would combine the strongest transferable capabilities without assuming Roster must operate every adjacent sales, monitoring and enterprise service found across the seven vendors.