You can now share Huntertech with friends directly from your account. VIP members get three VIP passes to attach to invite emails. When you send an invite, one pass is reserved and the friend receives a branded email with a signup link that unlocks 30 days of complimentary VIP access. If they do not sign up within 30 days, the pass returns to your account.
The Invite a friend card on your account page shows a segmented VIP pass meter for VIP members so you always know how many passes remain. After all three are used, VIP members can still send unlimited free plan signup invites. Non-VIP members can send free plan invites anytime.
New members may also see a first-session prompt to invite a friend, using the same pass model and referral tracking. Referrals appear on your account with status badges for pending invites, VIP sent, and VIP active once a friend joins.
Invite emails use the same Huntertech branding as other product communications: logo header, VIP callout, feature highlights, and a clear claim-your-access button. That makes it easier for friends to understand what they are getting and why the invite is worth opening.
Account notification settings are now a full delivery hub for watchlist alerts. Instead of treating the bell menu as the only outlet, you can configure in-app, email digests, a personal RSS or Atom feed, HTTPS webhooks, Slack direct messages, and PagerDuty Events API v2 from one page.
Each channel uses the same watchlist scope: vendors on your list, minus any you mute, with default category toggles for incidents, advisories, maintenance, updates, vulnerabilities, and vendor news. Incident delivery also respects ongoing, monitoring, and resolved status filters. Per-vendor overrides let you tighten or loosen any vendor without rebuilding the whole policy.
Personal feeds generate secret RSS and Atom URLs that honor those same filters, so feed readers stay in sync with the rest of your notification preferences. Webhooks support multiple payload formats, including simple JSON, canonical events, Slack Block Kit, and Discord embeds. PagerDuty connects with an Events API v2 integration key and sends trigger and resolve events with deduplication.
The page uses the same elevated card treatment as vendor surfaces, with a consistent setup panel at the top of every channel tab and category controls below. That makes it easier to scan what is configured, send a test, and move on to vendor-specific tuning.
We added dynamic page preview cards for vendor links so shared Huntertech.io URLs look better in iMessage, X, Slack, and other social platforms. When a supported vendor route is shared, Huntertech.io can now render a 1200x630 preview image for that specific vendor and section.
The new preview card highlights the vendor favicon, logo-derived color palette, website, a concise vendor description, and the available capabilities for that vendor. The active route is emphasized in the badge row, so overview, incidents, maintenance, advisories, updates, press releases, and compliance links can each feel specific in previews.
This gives us a reusable standard for future page previews. Instead of creating static images by hand, the card is rendered from structured vendor data, cached, and served through the same preview pipeline used by the Updates page.
We added a dedicated Updates page for following new Huntertech.io features, launch announcements, and platform enhancements in one place. It is designed to complement the blog: updates stay focused on what changed in the product, why it matters, and how teams can use it.
Each update now has its own canonical URL, making launches easier to share, index, and reference over time. The archive still brings everything together in one place, while individual update pages give search engines and readers a cleaner destination for a specific announcement.
Updates also ship with feed support for teams that prefer to subscribe outside the site. JSON Feed, RSS, and Atom are generated from the same structured update data, so feed readers, automation workflows, and internal notification systems can track product changes without manual scraping.
Vendor incident pages now include Community Pulse: a near-real-time signal built from users reporting whether a service appears down or up from their perspective.
The pulse chart groups reports into 15-minute intervals across a 24-hour window. That makes early spikes easier to see without waiting for an official vendor update. Vendor-level reports show the broad health signal, while incident-level reports provide local confirmation on specific incident cards.
Community reports are intentionally labeled as unofficial. They do not replace vendor status pages, but they add practical context during the early minutes of an outage when teams are trying to answer whether a problem is isolated or widespread.
We added support for the Model Context Protocol, making it easier for AI-assisted workflows to work with vendor intelligence in a structured way.
The homepage now includes an Add to Cursor button for Vendor Insights, plus a copy-config fallback for teams that prefer to add the MCP server manually.
MCP gives connected assistants a cleaner path to the same operational context teams already use: vendor incidents, maintenance windows, advisories, product updates, and related signals. Instead of treating those details as static pages, teams can bring them into workflows where investigation, summarization, and follow-up work already happen.
This is an important foundation for the platform. As more teams use AI tools for incident response and vendor monitoring, structured context matters. MCP support fits into that workflow without turning vendor intelligence into another place people need to manually check and copy from.
We rolled out a refreshed enterprise shell theme across core product surfaces, bringing the same deck language, metric tiles, navigation patterns, and ambient page treatment into more places.
The update is most visible on vendor overview pages, tools, incident views, and announcement surfaces. Cards now share a more consistent frame, controls feel more deliberate, and dense operational content has more room to breathe.
The goal is simple: make high-volume vendor intelligence easier to scan. Teams should be able to move from signal to context quickly without each page feeling like a separate product.
We redesigned the sign-in page and improved the authentication flow around it. The updated page makes the main login options easier to understand, keeps social and email paths visually consistent, and gives users clearer routes to sign up or return home.
We also improved what happens after sign-in. When someone starts from a specific page or workflow and needs to authenticate, the app can remember the intended destination and send them back after login completes.
This is especially important for OAuth sign-in, where intermediate redirects can strip query parameters. The improved flow preserves the intended destination across the handoff and clears it once sign-in completes.