Release Notes

Live co-creation suggestions — Sage now suggests activities and transport options directly in your itinerary as you chat, with accept, reject, and modify controls. A pre-build progress indicator shows you what Sage is working on the moment you open a trip.

• •Pre-build progress indicator: when you open a trip, Sage starts researching your destinations in the background. A status bar appears showing the current phase — scanning (checking what Sage knows about your destinations), researching (gathering activity data), enriching (adding details to activities), and complete. The indicator includes a progress bar and counts the activities found so far. Once complete, it briefly shows 'Sage found {n} activities for {destinations}' and fades out.
• •Live suggestion cards: as Sage generates ideas, activities appear directly in the itinerary panel with a green 'Sage suggested' badge and accept/reject/modify buttons. Accepting a suggestion confirms it into your itinerary. Rejecting removes it with a fade animation. Modify flags the suggestion for adjustment — describe the change you want to Sage in chat and the suggestion updates accordingly. Transport suggestions work the same way — suggested connections between destinations appear with accept/reject controls.
• •Audit warnings on suggestions: when Sage suggests an activity that comes with a known concern (like 'Booking recommended — this activity fills up quickly' or 'Price may increase closer to the date'), a severity-colored warning card appears below the suggestion with details on what to watch out for. Warnings come in three levels: info (blue), warning (amber), and critical (red). Each can be dismissed individually.
• •Decisions are saved: when you accept or reject a suggestion, your decision is recorded immediately and survives a page refresh. If anything goes wrong saving it, you'll see a clear error message and the suggestion stays right where it was so you can try again.
• •Real-time updates: suggestions appear on the trip page as Sage generates them, not all at once after Sage finishes responding. Activity additions, removals, moves between days, and transport suggestions all appear as they happen — no page refresh needed.
• •Research always completes: previously, if Sage needed to research a destination while its background research was still starting up, the request could be accepted and then never picked up — so Sage's results for that destination could be incomplete. Research requests are now always carried through to completion regardless of the order things start up. Combined with the research reliability work in v0.7.3, Sage's recommendations and search results are reliably backed by current data, with no more requests that sit unfinished.
• •Property images now load: a behind-the-scenes fix updates the list of image sources Voyonder trusts, replacing test-only placeholder addresses with the real photo services used by our travel data partners — Booking.com, Google, and Unsplash. Property images that were silently blocked by the v0.7.0 trust controls now display correctly throughout the trip planning experience.
• •Pricing page loads correctly: the /pricing page could get stuck on a loading skeleton in some browsers. The page now loads its content properly for everyone — no more permanent loading state on pricing.
• •The homepage demo now works even when JavaScript hasn't loaded yet — it opens a standalone version of the same demo at /demo, and there's a link to a finished sample itinerary for anyone who'd rather see a complete plan first.
• •Trial follow-up email: if your Explorer trial ends without an upgrade, Voyonder now sends one extra check-in three days later — a short reminder of what's included (Sage's itinerary planning, multiple active trips, curated activities), a note that your existing trips stay viewable, and a direct link to resume on your billing page. It is email only (no push notification), and each account receives it at most once.
• •All other features — trips, Sage web chat, subscriptions, billing, team settings, API keys, and support — work exactly as before.

Smarter trip planning on mobile, research pipeline reliability, and a sign-in fix — the itinerary view on your phone now includes a live suggestions panel that watches your plan and highlights schedule gaps, booking needs, and other trip-smart recommendations as you build your itinerary. Research is now more reliable than ever: no more stuck research jobs, magic-link sign-in no longer hangs, and the research behind your trip keeps itself up to date in the background.

• •Live suggestions panel (mobile): the itinerary view on your phone now includes a new suggestions panel that analyzes your trip and highlights things you might want to address — empty days where nothing is planned, packed days that could use more breathing room, big time gaps between activities, overnight location changes (e.g. sleeping in one city but starting the next morning somewhere else), low activity-type diversity, items that mention advance booking or reservations, and per-day cost alerts when you've set a budget cap. The panel is collapsible, filterable by category, and includes a manual refresh button that re-fetches your itinerary from the server.
• •Research reliability: when Sage doesn't have cached research for a destination — for example, when you ask about a place Sage hasn't researched before — the research job is now reliably processed from start to finish. Previously, some of these requests could be accepted and then never completed, meaning Sage's search results could be missing. Now, research always runs to completion — whether started fresh by your request or scheduled to keep older research fresh — so Sage's recommendations and search results are reliably backed by current data.
• •Magic link sign-in fix: the 'sign in with email' flow no longer hangs on the first request during server warm-up. If you experienced a delay or timeout when signing in with a magic link, that should now be resolved.
• •Research stays current on its own: destination research, accommodation and activity details, transport options, and dining suggestions are re-checked on a schedule, so the options you see stay current instead of ageing out. A new request from you is never left waiting behind older background work, so the research behind your trip is there when Sage needs it.
• •All other features — trips, Sage web, subscriptions, billing, team settings, API keys, and support — work exactly as before.

A smoother, more polished Voyonder experience — when you chat with Sage, your itinerary now updates in real-time on the trip page as Sage works. Lost pages (404 errors) now show a friendly Voyonder-branded page instead of a bare error screen. Sign-up and sign-in forms now show clear inline validation messages when something needs correcting. And the hidden brand-bleed characters that appeared in some page titles have been cleaned up.

• •Real-time itinerary updates: while Sage is generating your itinerary, the trip page checks for updates every few seconds. Day descriptions, activities, and suggestions now appear as Sage produces them — you no longer have to wait for Sage's entire response to finish before seeing changes. Your itinerary stays current throughout the conversation.
• •Branded 404 page: if you land on a page that doesn't exist (a broken link, an outdated bookmark, or a mistyped URL), Voyonder now shows a friendly branded page with navigation instead of a bare '404 — This page could not be found' error screen. You can easily find your way back to the dashboard or documentation.
• •Inline form validation: the sign-up and sign-in pages now show branded error messages below each field when something needs correcting — like a missing email or a too-short message. No more browser-default pop-up tooltips. The validation messages match Voyonder's visual style and disappear as soon as you fix the field.
• •Brand-bleed cleanup: a behind-the-scenes fix removes stray brand-reference characters that could appear in HTML page titles on some pages. Page titles now consistently show the Voyonder brand only.
• •All other features — trips, Sage, subscriptions, billing, team settings, API keys, and support — work exactly as before.

Sign-up page cleaned up — the 'Continue with Google' button on the sign-up page now works (it previously led to an error page). The sign-in page now also shows the Google sign-in button (the Google sign-in fix has been deployed). Also includes a behind-the-scenes database improvement that keeps account handling fast as Voyonder grows.

• •Fixed the sign-up dead end on /join: the 'Continue with Google' button previously appeared on the sign-up page but led to a 501 error page instead of an account. Google OAuth is now configured in production — the button works correctly and takes you through the Google sign-in flow. New users who sign up with Google receive a 7-day free trial automatically, just like email signups.
• •/login note: the Google sign-in button is now visible on the sign-in page (the Google sign-in fix has been deployed). Returning users can sign in with Google or via email magic link. Both /join and /login show the button identically.
• •All other features — trips, Sage planning, chat, subscriptions, billing, team settings, and support — work exactly as before.

More reliable accommodation details — Voyonder now only accepts property information from sources it recognises, and duplicate listings for the same hotel are recognised and combined instead of appearing twice. This is a behind-the-scenes improvement: no changes to how you use Voyonder day-to-day.

• •Trusted property details: photos now come only from recognised image services, booking links only from known travel sites, and guest-review text is cleaned before it is stored. Information offered by a source Voyonder does not recognise is no longer kept, so what you see on a property page has a known, verified origin.
• •No more duplicate hotels: when the same hotel turns up twice — for example, the same Booking.com property arriving as two separate entries — it is now recognised as one place and the duplicates are combined, without flagging hotels that were already being merged from several partners.
• •Faster property pages: the details behind each property are found in one step instead of several, so pages load more quickly and support can tell you which partner a hotel came from. Properties already in your trips are unaffected and stay fully usable.
• •Better duplicate detection: when two searches find the same hotel at once, Voyonder now compares where each result actually is. Close matches are combined automatically; uncertain ones are checked by a person instead of being assumed correct.
• •No feature changes: no new UI, settings, or workflows. Sage, trips, chat, subscriptions, and everything else work exactly as before. This release makes the information behind Sage's recommendations more robust and trustworthy.

Stronger quality assurance for every Voyonder release — all of Voyonder's automated checks now run together before a release goes out, including checks that had previously been skipped. This is a behind-the-scenes reliability improvement: no changes to how you use Voyonder day-to-day, but it means every future release is verified against the same comprehensive set of automated tests.

• •Complete verification on every release: previously, some of Voyonder's automated checks had to be added to the release checks by hand, and any that were missed simply did not run. All of them are now included automatically, so the full set of automated tests runs before every release reaches you — no manual step, nothing skipped.
• •Earlier warning when something regresses: if a change would reduce how much of the product is covered by automated checks, that is now caught before the release ships rather than being noticed later during an audit.
• •More than two dozen automated checks that existed but had not been running are now included in every release — verification for parts of the product that previously shipped without it. Those areas are now covered on every release.
• •No feature changes: all Voyonder features — trips, chat, subscriptions, billing, team management, and everything else — work exactly as before. This release is purely about making Voyonder's release verification more thorough.

Stronger quality checks for subscription billing — the automated checks that verify cancel-subscription behavior (race-safe cancel, idempotency, rollback when a billing step fails) now run before every Voyonder release. This is a quality-assurance fix: no changes to how you use Voyonder day-to-day, but it means every future release is verified against the same guarantee that canceling behaves correctly.

• •Cancel verification: cancelling a subscription is now checked end to end before every release — including double-cancel protection and the automatic rollback if a billing step fails after Stripe succeeds — so a cancel path that used to be verified only when someone remembered to run the checks is now verified every time. Each part of the cancel flow is checked, not just the happy path.
• •No feature changes: cancellation, billing, and checkout behavior are unchanged in this release. Existing subscriptions and cancel flows work exactly as before.
• •This is the same cancel guarantee documented in v0.5.0 — this release only ensures that guarantee stays verified for every future release.

Session tracking for saved accommodations — when Sage saves an accommodation to your trip, it now records which planning session it came from and its position in the ranked results. This is a behind-the-scenes improvement: no changes to how you use Voyonder day-to-day, but it means support can trace saved properties back to their originating session.

• •Session provenance for saved accommodations: each accommodation saved to your trip now carries the ID of the planning session it came from. If you ask support "which session was this hotel saved from?", they can look it up directly. Previously, saved accommodations had no link back to their planning session.
• •Rank position tracking: when Sage shows ranked results and you save an accommodation, its position in the ranking is now preserved. This helps support understand your relative preference when reviewing past selections.
• •Improved data validation: the planning API now checks that session IDs and rank values are valid before saving — invalid values return a clear error message instead of being silently ignored.
• •This is a small, focused fix — existing accommodations saved before this update will not have session provenance data. Only new selections after the update will carry this information.

Smarter pricing and more reliable accommodation details — price estimates for accommodation now come from real market prices, and each estimate shows how confident we are in it. Concurrent searches no longer conflict, a price stays correctly attributed when the same property is found in more than one place, and ratings now stay stable once a property has been researched. Most of this release is behind-the-scenes — no changes to how you use Voyonder day-to-day.

• •Real-time pricing with confidence levels: Sage's accommodation price estimates are now calculated from actual market prices contributed by multiple travel sources. Each price carries a confidence level — the more sources confirm a price, the higher the confidence. Previously that confidence was simply assumed rather than measured. Sage's price comparisons are now grounded in actual data and show you how reliable each estimate is.
• •Concurrent search reliability: when Sage rapidly searches for several properties at the same time, a property can no longer be saved twice, and a rare timing clash no longer makes the search fail — such a clash is now recovered from automatically.
• •One price per property: when Sage compares prices across different booking sources, each property now keeps a single, correctly sourced price. Previously a property could pick up a second price from another source, which wasted research capacity and made costs harder to predict.
• •Confidence indicators from real data: when Sage shows a confidence level for pricing data (e.g., "high" or "medium"), that level is now derived from how many travel sources contributed to the price — the more sources, the higher the confidence. Previously, high confidence was assumed by default regardless of data depth.
• •Stable ratings: once Voyonder has researched a property, its displayed rating and review count no longer shift when the property is checked again. Previously a rating could drift as newer data was averaged in; it now stays stable after its first calculation.
• •Clearer errors when saving an accommodation: an incomplete or invalid selection — for example a price that is not a positive nightly amount, or a stay that does not add up to whole nights — is now rejected with a clear message instead of being saved with default values. Saving the same selection twice no longer creates a duplicate.
• •API documentation for planning routes: the Voyonder API now includes documentation for the planning endpoints — covering session lifecycle, status polling, and the property selection flow. Available in the API docs section.

Same hotel, listed once — when accommodation is found on more than one booking site, Voyonder now recognises it as one property instead of several near-duplicates, so Sage's accommodation options are cleaner to compare. This is a behind-the-scenes improvement: no changes to how you use Voyonder.

• •The same hotel found on different booking sites is now matched into a single property, so Sage compares one entry per hotel rather than several near-duplicates.
• •More booking sites and market data: Sage now checks a wider set of accommodation sources, including major booking sites and short-stay market data, so the options behind its recommendations and price comparisons are broader than before.
• •Matching uses where a property actually is (coordinates, name and address) to decide whether two listings describe the same place, and each match records how confident the pairing is.
• •New market metrics are collected: occupancy rates, average daily rates (ADR), and RevPAR (revenue per available room) — laying the groundwork for future market analysis features in Sage.
• •This release is entirely behind the scenes: no interface changes, no new settings, and no changed workflows. Everything you see and use in Voyonder works exactly as before — Sage's results simply rest on a wider, cross-checked set of accommodation data.

Release Notes search highlighting — search results on the Release Notes page now highlight matching keywords, consistent with the Documentation search experience. Search now behaves the same way on both pages, so results look and highlight consistently wherever you search.

• •Release Notes search highlighting: searching on the Release Notes page now highlights matching keywords in version numbers and summaries — previously, release search results displayed plain text with no highlighting. Highlighting follows the same whole-word matching as Documentation search, so only complete words are highlighted (no partial matches).
• •Nothing you can see or click changes in this release.
• •Consistency: what gets highlighted always matches what was actually found, including queries with symbols in them such as 'c++'.

Documentation Search — instantly search all documentation sections and release notes. Find what you need with a single keyword, with results ranked by relevance and highlighted excerpts. Search stays on your own device, with keyboard navigation and screen reader support.

• •New! Documentation search: a search bar at the top of the Documentation page (voyonder.com/documentation) lets you search across all help sections — Getting Started, Using Sage, Subscription & Billing, Concierge Payments, Team Settings, API Keys, Troubleshooting, and Rate Limits. Results are ranked by relevance with title matches weighted highest and are displayed with section labels, highlighted keywords, and content excerpts. Keyboard navigation (arrow keys, Enter, Escape) and full screen reader support are built in.
• •New! Release notes search: a search bar at the top of the Release Notes page (voyonder.com/documentation/releases) lets you search across every release entry by version number, summary, and detail text. Results are ranked with version matches first and newer releases breaking ties.
• •Nothing you type into search is sent anywhere — searching happens on your own device, so results appear instantly and repeat searches are immediate.
• •Word matching: search matches complete words only — "sage" no longer falsely matches "message", while "api" still correctly matches "api-keys". Version numbers like "0.5.1" and terms like "c++" match correctly too. Use complete, correctly-spelled words for best results. Your browser's page search (Ctrl+F) remains available for partial-word searches.
• •A page and its search results can never disagree — what a section says and what search finds for it always match.
• •Search accuracy refinement: the excerpt displayed in search results correctly centers around your match even with accented words — searching for words like "résumé" now shows an excerpt centered on that word instead of falling back to the beginning of the section.

Subscription cancellation reliability, smarter checkout cancellation routing, and dynamic founding-cap pricing — the cancel endpoint is now race-safe by design, first-time subscribers who cancel during checkout land on the pricing page to easily re-subscribe, and the pricing page checks the founding-member cap in real time.

• •Cancellation reliability: cancelling and reactivating a subscription at the same moment can no longer leave your billing in a conflicting state. If anything goes wrong part-way through, the change is undone completely so your billing always matches what you see. Requesting a cancellation that is already in progress simply confirms it rather than charging or changing anything twice.
• •Smarter checkout cancellation: if you're subscribing for the first time and cancel during Stripe Checkout, you now land on the pricing page (voyonder.com/pricing?checkout=canceled) where you can easily re-subscribe. Returning subscribers upgrading their plan continue to land on their billing settings as before. This ensures new users always return to the canonical conversion surface.
• •Dynamic founding-cap pricing: the pricing page now checks the founding-member cap status in real time via the subscription API. When the 50-member founding cap is reached, the page automatically switches from founding pricing to standard pricing — the behavior was already documented but now uses a live API check instead of a build-time switch, so the transition happens the moment the cap is hit.

Payment system reliability and security hardening — cancelling and reactivating at the same moment no longer conflict, receipt numbers can no longer be guessed, a payment can only be recorded in a valid state, and you will not receive the same receipt twice.

• •Cancellation fix: canceling your subscription and reactivating it at the same moment could previously produce conflicting states. Your change is now applied in a fixed order, and if any part of it fails the whole change is undone, so your billing stays consistent with what you see. Requesting a cancellation that is already in progress simply confirms it rather than acting twice.
• •Receipt number security: receipt numbers (e.g. RCPT-20260928-XXXX) can no longer be guessed, so a made-up receipt number can't be passed off as a real one.
• •Admin payment safety: a payment can only be recorded in a state we recognise, so one cannot be created in a state that would skip normal processing.
• •Reliability: payments recorded by an admin no longer risk being left stuck as pending, because their status is set correctly the moment they are created.
• •Duplicate send protection: receipt emails now record delivery status before sending, so a crash recovery never results in duplicate emails to the customer.
• •Admin payments fix: administrators now see every customer's payments on the payments screen. It was previously showing only the signed-in administrator's own payments, which made recorded payments look as though they had gone missing.
• •Admin payment records: a payment recorded on a customer's behalf now keeps a cleaner audit record, and the cancellation fix above applies to admin-recorded payments too.

Payment receipts and admin payment recording — when a concierge booking payment succeeds, a branded receipt is sent to your email automatically. Administrators can also record offline payments (cash, check, wire) directly on the concierge request detail page.

• •Payment receipts: when you complete a payment for a concierge booking, you'll receive a branded email receipt showing the amount paid, payment method (card type and last four digits), date, description, and Voyonder branding — automatically, no action needed.
• •Admin Record Payment: administrators can now record offline payments (cash, check, wire transfer) directly on the concierge request detail page. Enter the amount, a description, and optionally toggle a receipt email to be sent to the customer. All recorded payments appear in the payment history list below the form.
• •Admin payments: administrators can record a payment and browse the full payment list, page by page, directly in Voyonder's admin screens.
• •Receipts only for completed payments — subscription checkouts never trigger a receipt, so every receipt you receive matches a payment you actually made.

New Account Portal with full subscription self-service — view your plan, usage, invoices, upgrade, or cancel, all from /account. Also includes the self-service subscription funnel from the pricing page, a trial countdown banner on the dashboard, and checkout hardening for returning subscribers.

• •Account Portal: a new /account page shows your profile summary, subscription status card (tier, plan status, renewal date), and 5 most recent trips. The subscription management hub at /account/subscription gives you full self-service: current plan details, trip usage vs. limits (unlimited for paid tiers), invoice history (recent with PDF links), upgrade, and cancel.
• •Upgrade page: /account/subscription/upgrade shows available tiers inline with pricing and feature comparisons — select a tier and proceed to checkout directly from the hub.
• •Cancel flow: /account/subscription/cancel walks you through confirm → survey → done. Cancelling stops the next renewal — your access continues through the end of the billing period you've already paid for. Free-tier users are redirected away.
• •Trial banner: your dashboard now shows a prominent countdown banner when you're on a free trial — days remaining, a progress bar, and a one-click 'Upgrade Now' button that takes you to the pricing page to choose a plan.
• •Subscribe-intent checkout hardening: if a returning (logged-out) subscriber tries to subscribe again, they're redirected to /account/subscription instead of getting a duplicate subscription and double charge. Founding cap is enforced during checkout, and trial periods are not duplicated when the auto-trial already started.
• •Pricing page: 'Subscribe to Explorer' / 'Subscribe to Adventurer' / 'Subscribe to Elite' buttons replace 'Start Free Trial' for visitors who aren't signed in. Clicking one takes you to signup with your chosen tier pre-selected via the ?subscribe= parameter.
• •Signup with intent: the join page detects the ?subscribe= parameter, shows a tier-specific heading ('Subscribe to Explorer' etc.), and passes your selection through the magic link URL — so even if you open the verification email on a different device or browser, you'll still go straight to checkout after verifying.
• •Direct-to-checkout: after verifying your email via magic link, Voyonder creates a Stripe customer and a Checkout session with a 7-day free trial — you complete payment on Stripe's secure page and land on a subscription confirmation page, ready to plan. This works for both new and existing Voyonder accounts.
• •Changed your mind? If you cancel or leave the Stripe checkout page, you'll be returned to the pricing page — nothing is charged, your account stays on the free tier, and you can subscribe anytime.
• •Monthly billing: plans purchased through the pricing page are billed monthly, and promo codes can be applied at checkout.
• •Graceful fallback: if the checkout setup encounters an issue (rare), you're taken to where you'd normally land after signing in — the welcome page for new accounts, your dashboard for existing ones. Your ability to sign in is never blocked by a subscription error, and you can subscribe later from Settings > Billing or the Account Portal.
• •Analytics: we now measure which pricing buttons people use and when they open the Account Portal, so we can see which plans travelers are most interested in.
• •Founding pricing display: once the 50-member founding cap is reached, the pricing page automatically switches from founding pricing to standard pricing for everyone, including visitors who aren't signed in — the page heading changes, the founding badge is hidden, and each tier shows its regular price with the old founding rate crossed out. Founding members who already locked in their rate keep it.
• •Trial reminder CTA fix: trial-ending reminder emails (day 5 and day 6) and push notifications now point to the pricing page (voyonder.com/pricing?subscribe=explorer) instead of the old billing settings URL — so clicking 'Upgrade' in a reminder takes you straight to the subscription funnel where you can pick a plan. In the app, all trial banner variants — including the dashboard countdown banner — now point to the same pricing-funnel destination.
• •Behind-the-scenes reliability: if a subscription change (signup, upgrade, or cancel) hits a temporary system hiccup, it is retried automatically within 15 minutes — so your subscription changes are always applied and you never miss a welcome email, receipt, or confirmation.

Smarter per-destination scoring for Sage's behind-the-scenes logistics checks — each destination is now scored independently based on its own issues, not the total across your entire trip. This means more accurate logistics intelligence when some destinations have issues and others don't.

• •Behind-the-scenes fix: Sage's logistics advice used to take every issue found across the trip, turn them into a single score, and apply that same score to every destination — so a destination with no issues could carry the same warning as one with several.
• •Each destination is now scored independently: Sydney with one seasonality issue gets a score of 0.88, while Tokyo with zero issues correctly scores 1.0. This makes Sage's logistics advice more accurate — especially for multi-destination trips where some locations have concerns and others are fine.
• •Everything you see and do in Voyonder works exactly as before — this is a behind-the-scenes accuracy improvement that makes Sage's logistics intelligence more precise. No changes to the chat interface, trip creation, or any user-facing feature.

New public contact form — reach the support team directly from voyonder.com without signing in. Your message goes to our support inbox and we reply within 24 hours.

• •Visit /contact to send a message to the Voyonder support team — fill in your name, email, subject (optional), and message, and we'll get back to you within 24 hours.
• •No sign-in required — anyone can use the contact form, whether you're a Voyonder subscriber, a prospective customer, or just curious.
• •Each submission is saved securely and the support team is notified immediately via email.
• •Rate limiting (5 submissions per 60 seconds per IP address) protects against spam — normal use never approaches this limit.
• •Prefer email? You can still reach us directly at support@voyonder.com.
• •If something you type needs correcting, the form tells you before it sends. Whatever you write reaches us as plain text — nothing you type can run in our inbox.

One-click trip creation from welcome page templates — pick a ready-made trip and Sage starts planning immediately, with a live progress indicator showing each step. Also includes internal analytics documentation for the conversion funnel dashboard.

• •Quick-start templates on the welcome page now create trips with one click — no destination typing needed. Pick from six ready-made trips (Paris weekend, Orlando family vacation, Tokyo solo adventure, Bali couples retreat, NYC business trip, London culture tour) and Sage starts planning your itinerary right away.
• •Per-template loading spinner shows which template is being created — no more wondering if your click registered.
• •New progress indicator during trip creation: a 3-step visual bar (Destination → Planning → Your Trip) with contextual messages like "Creating your trip...", "Sage is planning your itinerary...", and "Almost ready! Taking you to your trip...".
• •Template selection is now tracked for analytics purposes — helps us understand which trip types are most popular so we can improve the experience.
• •If you'd rather check the destination before planning starts, templates can still fill it in for you to review.

Sage's behind-the-scenes logistics intelligence got smarter, a daily generation cap protects Sage availability for everyone, and the app feels more polished with pop-up messages replaced by gentle slide-in notifications and smoother trip creation. Also includes a security fix for trip data protection, critical streaming reliability fixes, and performance improvements across the board.

• •Daily generation cap: Sage now has a per-user daily limit of 50 generations (rolling 24-hour window). Normal use never approaches this limit — it only protects against excessive usage. If you hit the cap, you'll see a clear message and can try again the next day. (This cap can be lifted by operations as capacity grows — no update needed on your end.)
• •UI polish: messages that used to interrupt you as pop-ups now slide in gently and never block what you're doing — read them and keep planning. Additional polish: the billing page now shows its messages the same way as the rest of the app instead of with its own one-off notice; 10+ screens that used to fail silently now tell you when something goes wrong; loading skeleton pages added for blog, gallery, settings, and blog articles; notifications now fade away smoothly when dismissed.
• •Gallery detail page: viewing a trip from the community gallery now shows a skeleton loading state while the page loads — no more blank flash before the content appears.
• •Trip creation: the form now has smooth step transitions, a visible spinner while your trip is being created, clearer disabled button states, and better error messages when something goes wrong.
• •Security fix: Sage only reads trip data for the trip you're working on.
• •Smarter temporal checks: Sage now detects impossible transfers, overlapping activities, early departures, late arrivals, and overly long travel days, and flags backtracking when your itinerary zigzags between destinations.
• •Geographic efficiency: Sage clusters your day's activities and checks whether they're grouped to minimize travel — flagging walking fatigue and suggesting spread or regroup options when the route is inefficient.
• •Better transport feasibility: distance-aware mode estimation (car, bus, train, flight) with warnings for long journeys and destinations only reachable by air.
• •Sharper booking urgency: activity-level sell-out risk patterns with the peak-season window extended to 12 months, plus accommodation and transport urgency tiers.
• •Expanded seasonal closure coverage: new destination patterns for Greek islands, Amalfi, Iceland, Cinque Terre, Venice, and ski resorts.
• •Accessibility improvements: the homepage, pricing, login, and signup pages now include skip-to-content links, proper main landmarks, semantic HTML sections, and screen-reader-friendly ARIA labels throughout — making Voyonder easier to navigate for users who rely on keyboard navigation or assistive technology. Interactive demo step buttons have larger touch targets, dynamic content updates are announced by screen readers, and the pricing comparison table includes proper header associations and a caption.
• •Streaming reliability: Sage's chat responses now handle emoji, CJK characters (Chinese, Japanese, Korean), and other multi-byte content correctly — no more mid-response errors when your itinerary includes international destinations or celebratory emoji. Your conversation with Sage is also never mixed with anyone else's, even when other travelers are chatting at the same time.
• •Performance boost: Sage now uses smarter caching, streaming batching, and lazy loading — making chat responses feel faster and reducing load on the backend. Database queries have been optimized across the app, so trip pages, the dashboard, and chat history load more quickly.
• •Sage edge-case hardening: itinerary generation is now more robust in unusual scenarios — Sage handles edge cases like extreme date ranges, destinations with limited transport options, and complex group dynamics more gracefully without error.

Behind-the-scenes reliability and fair-use safeguards for Sage — automatic retry logic, usage limits, and operational monitoring. No changes to how you use Voyonder — the chat experience looks and works exactly as before.

• •Fair-use safeguards: Sage now has per-user hourly limits (soft warning at 50,000 tokens, hard limit at 100,000 tokens). Normal use never approaches these limits — they only protect against excessive usage. If you hit the hard limit, you'll see a clear message and can try again after a short wait.
• •Smarter retries: If Sage briefly loses connection to its AI provider, it now retries automatically up to 3 times before showing an error. Most transient issues resolve without you noticing.
• •Behind-the-scenes monitoring: we now spot Sage slowdowns and failures early, so problems are caught before they reach you.
• •Your Sage conversations are now stored more durably, along with their usage figures, so they survive reconnects and retries.
• •Improved group dynamics intelligence: Sage now detects compatibility mismatches between travelers (differing activity interests), separates safety from mobility constraints for more nuanced handling, and factors group tension and alignment into its coordination suggestions — helping your group find compromises that work for everyone.

Sage now automatically checks the logistics of your trip with every message — five dimensions in parallel: whether your dates and destinations make sense together, whether destinations are grouped efficiently, whether transport realistically exists between them, how urgently you need to book, and whether any seasonal closures might affect your plans. Sage adjusts its advice based on what it finds — automatically, with nothing new to click.

• •With every message you send, Sage automatically runs five behind-the-scenes checks on your trip's feasibility: temporal consistency (are the dates and destinations realistic together?), geographic efficiency (are destinations grouped to minimize travel?), transport feasibility (can you realistically get between destinations?), booking urgency (how soon should you book?), and seasonal closure awareness (are any attractions or services affected by the season?).
• •These checks happen with every message you send and shape Sage's answers. There is no separate logistics dashboard to open — you get better advice without having to ask for it.
• •If you want to know what Sage is checking, just ask: 'Is this itinerary realistic?' or 'Do I need to book anything now?'
• •This release also introduces the underlying chat infrastructure for real-time streaming responses and parallel intelligence — making Sage faster and more responsive as we build more capabilities on top.

Research features now require a signed-in account. Sign in and every research feature works exactly as it did before.

Documentation pages now stay current faster — release notes and help articles reflect the latest information within minutes of a new release, instead of lingering on a previous version until the next full site build.

• •The documentation and release notes pages now refresh automatically every 5 minutes. When a new version ships, the updated content appears within minutes instead of showing stale information from the previous build.
• •The first visitor after a release now sees the latest version, not the previous one.
• •This is a behind-the-scenes reliability improvement. Everything looks and works the same — the documentation and release notes pages just stay more current after each release.

Faster trip planning and a smoother signup and sign-in experience — one-click trip templates on the welcome page, a live progress indicator while Sage works, clearer errors when things go wrong, and easier magic-link sign-in.

• •Quick-start trip templates on the welcome page: six ready-made trips (romantic Paris weekend, family Orlando vacation, solo Tokyo adventure, Bali couples retreat, NYC business trip, London culture tour) pre-fill the destination, travel style, and group size — start planning with one click instead of typing a destination.
• •Live progress indicator in chat: while Sage works on your request, a progress bar shows the stage of processing — Thinking, Researching, or Responding — so you always know Sage is on it. (If streaming events are slow, the indicator falls back to time-based estimates, so it keeps moving either way.)
• •First-trip creation failures now show a clear inline error message below the destination field on the welcome page. Previously the button just silently re-enabled and nothing appeared to happen — now you'll see what went wrong (the server's message or a generic fallback).
• •Sign-in page now has a 'Resend email' button (30-second cooldown) — the same as the sign-up page. If you miss the magic-link email when signing in at voyonder.com/login, you can resend it right from the same screen instead of starting over.
• •Any old voyonder.com/chat links now redirect (307) to your dashboard. There is no standalone /chat page — all planning happens on trip pages. This closes the last 404 path for /chat URLs after the email-CTA fix in v0.2.58.
• •After verifying your magic link, the short 'Welcome to Voyonder!' moment is slightly shorter (400ms instead of 1000ms) — fast enough to feel instant while still registering the success.
• •Behind-the-scenes: old links to pages we have retired keep working while those pages are rebuilt for a future release; when a subscription step is needed, you are taken to the right page with a clear message instead of a generic error; and the 'Resend email' timers on the sign-in and sign-up screens now stop as soon as the countdown finishes instead of continuing in the background.

Email link fixes and faster gallery — links in welcome emails and receipts now go to working pages instead of error pages, and the community gallery loads noticeably faster.

• •Fixed broken links in transactional emails: the welcome email, day-3 inspiration email, day-5 pro-tip email, founding-member celebration email, and post-purchase receipt all previously linked to a page that didn't exist (voyonder.com/chat, which returned a 404 error). They now link to the correct pages — /welcome for new users and /dashboard for returning customers.
• •If you clicked a link in one of these emails before and landed on an error page, we're sorry about that — those links now work correctly.
• •The community gallery now loads faster: pages are cached on the server for about a minute, so browsing trips, filtering by destination or occasion, and sorting by popularity or rating all feel snappier.
• •Behind-the-scenes reliability improvements: signing up with a magic link is now more robust under heavy load (the system no longer trips over itself when two identical-email signups arrive at nearly the same moment), and the referral code system now handles concurrent claims safely.

Keeping our emails useful: we now measure how the emails we send you — welcome messages, trip inspiration, and pro-tips — perform, so we can improve the ones that aren't landing.

• •Email opens and link clicks are now counted quietly in the background — this tells us which emails actually help people plan trips and which ones to improve.
• •No new data about your trips is collected: this only measures how our own emails are received.
• •Delivery failures and spam reports are also tracked, which helps us keep our email program reliable — and if an email of ours ever seems missing, checking your spam or promotions folder is still the first step.

A welcome email sequence for your first week — and faster gallery and blog pages. New trial accounts now receive a day-3 inspiration email and a day-5 planning pro-tip over their first week, and the community gallery and blog load faster thanks to behind-the-scenes caching.

• •Day-3 email: 'This week in Voyonder' — real traveler stories showing what other people asked Sage, from a first-timers' Japan trip to a budget train tour of Portugal, with a jump-back-in link to plan your own trip.
• •Day-5 email: a planning pro-tip from our favorite power users — ask Sage about closures and construction on your dates, re-pacing a packed day for kids, and the least-miserable way to get from Rome to the Amalfi Coast. It also quietly reminds you your free trial ends in 2 days.
• •The sequence runs daily in the background and only goes to accounts that are still in their free trial — paying customers are never sent these follow-ups.
• •Delivery is retry-safe: if a brief email hiccup happens on delivery day, the email is automatically retried instead of being silently dropped — the same reliability fix that protects your founding-member celebration email.
• •Faster browsing: gallery trip pages and blog articles now refresh on a short cache — pages load quicker, and content stays current without a redeploy (gallery refreshes about every minute, blog about every 5).

More reliable welcome emails for paying customers and trial users — founding-member celebration emails, post-purchase receipts, and welcome-day5 templates now handle transient delivery failures without permanently suppressing messages.

• •Founding-member celebration emails are now more reliable: if a brief delivery hiccup happens, the system automatically retries instead of skipping the email entirely. If you locked in founding pricing and didn't see your celebration email, it should arrive on the next retry.
• •Post-purchase confirmation emails are now more reliable too — the same retry logic protects them, so a temporary delivery issue never silently suppresses your receipt.
• •The day-5 pro-tip email now renders correctly in Outlook, Gmail mobile, and Yahoo — a layout fix ensures the tip box and emoji appear as intended instead of being stripped or misaligned.
• •Behind-the-scenes: welcome emails are now reliable — signing up no longer risks your welcome email being skipped, and founding-member emails reach their subscribers every time.

Security fix — API key rotation is now race-safe and scoped to your organization. If two people rotate the same key at the same moment, only one replacement key is created, and knowing a key's identifier is never enough to revoke a key from another organization.

• •Rotating an API key is now safe even if two people do it at the same time — the first rotation succeeds, and the second one returns a clear 'Conflict' message instead of creating a duplicate replacement key or producing a generic error.
• •Organization boundaries are now enforced during key rotation: a valid key from one organization can never be used to revoke a key belonging to a different organization.
• •Key rotation is now logged as its own security event ('key rotated') in the audit trail, separate from scope changes — giving you clearer visibility into key lifecycle actions.
• •Everything about API keys works exactly as before: create, rotate, revoke, and use them the same way. These are behind-the-scenes safety improvements.

Stability: automatic request limits — Voyonder now protects itself from traffic spikes and bursts, so it stays fast and reliable for everyone even at busy times. In practice you'll rarely notice them: normal use never hits the limits, and if a request ever comes back with a 'Too many requests. Please try again.' message, you just wait a moment and try again.

• •Signing in, signing up, planning trips, and chatting with Sage all keep working exactly as before — the new limits only kick in during unusual burst activity.
• •If you ever see a 'Too many requests. Please try again.' message, simply wait a moment and retry: most limits reset within seconds, and the slowest one (sign-in email resends) allows a new send after a few minutes.

Coordination reliability improvements, behind-the-scenes billing hardening, and a smoother sign-up experience — completing a coordination item now tells you if it didn't save, foundational guardrails for the 50-member founding price program are in place, and signing up with a magic link got easier to recover from.

• •Sign-up: if your email doesn't arrive, there's now a 'Resend email' button on the sign-up screen (available again every 30 seconds), so you no longer need to re-enter your email to get a fresh link.
• •Signing in: if your magic link is invalid or expired (links work for 1 hour), the screen where you land now offers a 'Get a new link' form — put your email in right there and a fresh link is sent, no need to go back to the start.
• •Coordination tab: if marking an item complete fails (for example, a brief network blip), the panel now shows a clear 'Could not complete this item' message and keeps the item open — previously it could fail silently. Just tap it again to retry.
• •API Key management reliability hardening — a type-level fix for the usage reporting path feeding your per-key request counts (Settings → API Keys); zero runtime effect, keys and reporting work exactly as before.
• •No founding spot can be claimed twice or held by a checkout you abandon, and the member count corrects itself. The 50-member founding cap is not active yet — nothing about your billing changes in this release.

New Coordination tab on your trip page — see and complete the action items, decisions, and follow-ups Sage tracks as your group plans.

• •The Coordination tab appears in the right-hand panel of your trip page, grouped into three types: Actions (things to do), Decisions (choices to make), and Follow-ups (things to circle back on).
• •Each item shows its priority (High, Medium, or Low), a due date when one applies, and an assignee when Sage has one.
• •A progress bar and completion percentage show how much of the group's coordination work is done — tap the circle next to any item to mark it completed.
• •If Sage hasn't generated coordination items yet, the panel shows a friendly placeholder; items appear automatically as Sage helps your group plan.

Improved search reliability in the Knowledge Base, plus security hardening for upcoming coordination features.

• •Choosing a category right after searching no longer resets your results.
• •“Clear filters” now always fully clears your search.
• •Security hardening: coordination features keep each trip's shared notes and updates visible only to the people on that trip.
• •Behind-the-scenes reliability work: every release now ships exactly the build that passed our automated checks, and a long build can no longer be cut short before it finishes.

New self-serve Knowledge Base — browse, search, and read help articles right from Voyonder.

• •Visit the Knowledge Base to explore help articles on getting started, billing, notifications, trip templates, troubleshooting, and more.
• •Search across all articles and filter by topic — no account needed.
• •Read full articles in a clean view with related articles and quick tag links.
• •Reach the Knowledge Base from the homepage footer or the link in the site-wide footer.

Behind-the-scenes groundwork for a self-serve knowledge base — no visible changes to how you use Voyonder today.

• •Built the backend infrastructure for a knowledge base and FAQ system: a new data model that stores articles with an editorial workflow (draft, in review, published, archived), public API endpoints to browse and search published articles, and admin-only editor tools to create, review, and manage content.
• •Seven starter FAQ articles are loaded into the system covering common topics — Getting Started, Billing, Notifications, Templates, and Troubleshooting — aligned with Voyonder's pricing and free-trial information.
• •There is no customer-facing knowledge base page yet — the API is built and ready, and a frontend will follow in an upcoming release.
• •No changes to your trips, subscription, settings, or any other part of Voyonder you use today.

Reliability release — behind-the-scenes reliability improvements to how updates reach you. No user-visible changes.

• •Every release now goes out exactly as it was verified before shipping, so the version that was tested is always the version that reaches you.
• •No changes to how Voyonder works for you: your trips, conversations, subscription, and settings are unaffected.

Maintenance release — nothing you see or do in Voyonder changes. Your trips, Sage conversations, subscription, and settings work exactly as they do today.

• •Sage's planning was maintained in this release — the advice and itineraries it produces are unchanged.
• •No changes to how Voyonder works for you: your trips, conversations, subscription, and settings are unaffected.

Behind-the-scenes groundwork for enhanced account administration — no visible changes to how you use Voyonder today.

• •Prepared internal plumbing for richer account and team administration, including activity oversight and ownership controls. These capabilities are not enabled yet, and nothing about your experience has changed.
• •No changes to your trips, conversations, subscription, or payment experience — this release only adds groundwork.

Behind-the-scenes groundwork for a future sign-in upgrade — no visible changes to how you use Voyonder today.

• •Prepared internal plumbing for single sign-on (SSO) so organizations can sign in with their own identity provider in a future release. SSO is not available yet, and nothing about signing in changed for you.
• •No changes to your trips, subscription, or settings — this release only adds groundwork.

Sage reliability fix — saved trip context is now kept strictly within your account.

• •Fixed a rare condition in Sage's memory where a saved-context update could be scoped incorrectly under specific circumstances. Updates are now always bound to your account and your account only.
• •No visible change for most users — your trips, conversations, and saved preferences behave exactly as before.

Maintenance release — nothing you see or do in Voyonder changes. Your trips, subscription, and settings work exactly as they do today.

• •Billing and Sage planning were maintained in this release — pricing, billing, and the itineraries Sage produces are unchanged.
• •No changes to how Voyonder works for you: your trips, subscription, and settings are unaffected.

API key reliability — rate-limit recovery is now prompt and truthful. No visible change for most users.

• •If one of your API requests is ever rate-limited, the 'Retry after' time you're given is now accurate — access comes back when it says it will, not later.
• •No change to how Voyonder works for you — this hardens the infrastructure that API keys run on. Nothing to do on your end.

API keys for organizations — programmatic access keys so your team can connect integrations and scripts to Voyonder.

• •Organization admins can now create API keys from Settings → API Keys. Each key carries a name, scopes (defaulting to profile:read), and an optional expiry date.
• •Keys are shown exactly once at creation (they start with sk_) and can never be retrieved again — Voyonder stores only a secure fingerprint. Lost a key? Rotate it: the old one stops working immediately.
• •Any organization member can view the key list and usage dashboard; only admins can create, rotate, or revoke keys.
• •Per-key rate limits (60 requests per minute by default) keep access fair, with clear wait-and-retry guidance if you hit the limit.
• •The usage dashboard shows per-key request counts for the last 30 days (adjustable up to 90) so you can see which integrations are active.
• •No other visible changes in this release. (Single sign-on, the Enterprise plan, and a yearly-billing option are not yet available.)

Fixed the post-survey thank-you step: free accounts who complete the trip survey now see 'Thanks for your feedback!' with a 'Start your 7-day free trial' button, as originally announced. No action needed.

• •After you finish planning a trip and answer the quick 'how likely are you to recommend us?' survey, your feedback is saved and free accounts now see a thank-you step with a 'Start your 7-day free trial' button right there — no need to go hunting for the pricing page.
• •The v0.2.38 release notes announced this thank-you step, but on that release the survey simply closed after you submitted. This release ships the actual fix: the thank-you step and trial button now appear for free-tier users after the survey, and clicking the button starts your 7-day Explorer trial in place — no credit card required.
• •Trialing and paid accounts are unaffected: the survey still closes right after you submit, exactly as before.
• •Nothing about your existing trips, subscription, or data changed — this fix only restores the post-survey thank-you step promised in v0.2.38.

Free trial offers now meet you at more steps along the way — the welcome page, the trial banner, and (coming shortly after this release) the post-survey thank-you step. No action needed.

• •Free trials are now easier to start wherever you are. If you sign up and land on the welcome page, your Explorer trial now starts automatically even when your account is still loading — so a quick start never misses the window.
• •The trial banner at the top of the app no longer lets you immediately X it away on first view: the first time you see it, a gentle 'Not now, thanks' snoozes it for 7 days instead of a 24-hour dismissal, so the offer sticks around long enough to be seen.
• •After you finish planning a trip and answer the quick 'how likely are you to recommend us?' survey, your feedback is saved and the survey closes. A thank-you step with a 'Start your 7-day free trial' button is rolling out right after this release — and in the meantime your free trial is one click away on the onboarding checklist, the welcome page, or the trial banner.
• •Nothing about your existing trips, subscription, or data changed. Free trial remains 7 days of Explorer, no credit card required.

Fixed an issue where new accounts could see an error page instead of their setup checklist on the dashboard. No action needed.

• •If you're new and haven't created your first trip yet, the dashboard shows a guided onboarding checklist to get you started — start your free trial, create your first trip, talk to Sage, and complete your itinerary. Some new accounts briefly saw a generic error page there instead.
• •That's fixed now: the dashboard loads reliably for new accounts again, and the 4-step checklist is back on the dashboard for anyone just getting started.
• •Nothing about your trips, subscription, or data changed — this fix only restores the dashboard for brand-new accounts.

Trial offers right where you are — your onboarding checklist now starts with a 'Start your free trial' step, and free trials start more reliably for every account. No action needed.

• •New users now see a 'Start your free trial' step at the top of their guided onboarding checklist. Click it to activate your 7-day Explorer trial in place — no credit card required. The step is complete as soon as your trial is active, already-trialing users see it pre-checked, and accounts that have already used their free trial or are on a paid plan see it as already done — it's never a dead end.
• •Free trials now start more reliably for all accounts. If your account has no subscription record (for example, an older account created before trials were standard), visiting the welcome page now starts your trial automatically — previously those accounts could miss the trial entirely.
• •The checklist itself is unchanged in spirit: four steps total — Start your free trial, Create your first trip, Talk to Sage, and Complete your itinerary — with progress tracked automatically and a progress bar showing how far along you are.

Behind-the-scenes fix — your trip count is now kept up to date automatically whenever you create or delete a trip, so usage displays and upgrade prompts always show accurate numbers. No action needed on your end.

• •Your trip count now updates the moment you create or delete a trip: billing usage displays, tier information, and upgrade prompts always show the right number — previously the count could drift stale between refreshes.
• •Error-safe by design: if a count update ever fails (for example, a temporary database hiccup), your trip is still saved and the count corrects itself on your next trip change. No data loss, no action needed from you.
• •All other changes in this release are internal reliability improvements with no visible effect on how Voyonder works.

NPS survey improvements, guided onboarding checklist, trial expiry auto-cleanup, and growth dashboard reliability fixes — trips without an end date now trigger NPS prompts, you can choose 'Ask me later' for a 48-hour reminder, first-time users get a guided checklist on their dashboard, expired free trials are cleaned up automatically, and the growth dashboard churn rate and trial-to-paid metrics are now accurate.

• •NPS surveys now trigger for trips that are marked complete even when no end date was ever set. Previously, a trip without an end date never showed the NPS prompt. Now Voyonder looks at both your dates and the trip's status, so more travelers can share feedback.
• •"Ask me later" is now a real snooze — if you're not ready to rate your experience, choose "Ask me later" and the NPS survey will reappear after 48 hours. Previously, dismissing the survey was permanent. You can still choose "Skip" to dismiss it forever.
• •New guided onboarding checklist appears on your dashboard when you have no trips yet. It walks you through three steps: Create your first trip, Talk to Sage, and Complete your itinerary. Progress is tracked automatically, and when you finish all three steps, a completion event is recorded. The checklist disappears once you've completed everything.
• •Trip creation tracking is now deduplicated — the analytics event fires exactly once per trip, from the API. Previously it could fire from both the page and the API, inflating creation counts in analytics.
• •Expired free trials that were never converted to a paid plan are now automatically cleaned up. If your trial ends without you choosing a plan, your subscription is transitioned to canceled — keeping your account data accurate and preventing stale trial records from skewing analytics. This is a behind-the-scenes change that does not affect your trips or account access.
• •Growth dashboard fixes: the churn rate now uses the correct denominator (users active at month start), and trial-to-paid conversion now properly filters to subscriptions that actually had a trial period. These were critical accuracy fixes.
• •The sample Rome 5-day itinerary page now shows a large preview image when it is shared on social media.
• •Survey response times: post-trip surveys now load quickly, so rating a trip takes a moment instead of a wait.

Analytics fix — confirming a subscription cancellation now records the cancellation-started event for analytics and compliance again

• •Fixed: when you confirm that you want to cancel your subscription in the cancel dialog, Voyonder now records the cancellation-started analytics event again. This event had temporarily stopped firing after the September 3rd billing update.
• •No change to how cancellation works — your subscription still cancels at the end of your current billing period exactly as before. What's fixed is that your cancellation is recorded correctly again, for analytics and compliance.

Team member revival and invitation reliability fixes — re-inviting a removed teammate now works correctly, accepting the same invitation from two places at once no longer errors, and organization seat-count reconciliation is fully operational

• •Fixed: re-inviting a removed team member now works. When an admin removes someone and later re-invites them, accepting the new invitation correctly restores their membership with the role from the new invitation — instead of failing with an error as before.
• •Fixed: accepting the same invitation from two places at once (two open tabs, or a slow network retry) no longer produces an error for one of the two acceptances. The membership is created exactly once and both attempts complete cleanly — the second one simply confirms the invitation was already accepted.
• •Restored: organization seat-count reconciliation is now fully operational. If a membership change ever fails to sync immediately, a background check corrects the seat count within about 30 minutes.

Organization billing — let your organization pay for one subscription that covers the whole team.

• •Organization billing: an organization can now buy a single subscription that covers the whole team instead of every member paying separately. Admins see a Team section on the billing page where they can upgrade the org's plan; other members see the subscription status read-only.
• •Seat-based pricing: the organization pays for one seat per active member, and the seat count adjusts automatically as members join or leave.
• •Effective tier: your features follow the higher of your personal tier and your organization's tier — for example, an Explorer member of an Adventurer organization gets Adventurer features. If the organization's subscription is past due or unpaid, new invitations and acceptances are paused until billing is resolved (existing members are unaffected).
• •Downgrades are handled through the Stripe billing portal, not the checkout flow — the upgrade flow intentionally supports upgrading or staying on the same tier.

Team settings UI, team invitations, and organization-scoped trips — manage your team from a dedicated settings page, invite people by email, and keep your team's trips private to the org.

• •New Team Settings page at /settings/team — create organizations, view your member roster, manage roles, and send invitations. The page shows all organizations you belong to and lets you create new ones.
• •Organization detail page from your team settings — view the member roster with roles and join dates, change member roles (admin/member/viewer), remove members, and manage pending invitations. Non-admins see the roster read-only.
• •Last-admin protection: an organization always keeps at least one admin — it is not possible to demote or remove the last admin from the settings UI, protecting your team from accidentally being locked out.
• •Invite your team by email: admins can send invitations from their organization, and invitees accept or decline from a link. Invitations expire after 7 days, and re-inviting someone rotates the link so only the newest one works.
• •Invitees don't need an existing account — accepting an invitation automatically creates their account, adds them to the organization, and signs them in.
• •Invitation management is permission-protected: only org admins can create, list, or cancel invitations, and non-members can't even see the organization exists.
• •Organization trips: trips can now belong to an organization, and organization members can find those trips in their dashboard. Admin and member roles can create and edit org trips; viewers can view them. Org trips stay private — they never appear in the public gallery.
• •Org access automatically follows role: an admin's trips are editable by admins and members, a member's trips are visible to all org members, and viewers can only view. Removing someone from the org revokes their access.

Foundation for team management — the behind-the-scenes building blocks for organizations, members, and roles. No visible changes to your trips, payments, or settings in this release.

• •Organizations now exist as a first-class concept: every account can belong to one or more organizations, and each organization has members with a role — admin, member, or viewer. The person who creates an organization automatically becomes its first admin.
• •Organization management is available through the API today: create an organization, view its members, rename it or set a custom address, change a member's role, or remove a member. Organization settings and invitation flows are being built on top of this foundation and will arrive in upcoming releases.
• •An organization always keeps at least one admin — it is not possible to demote or remove the last admin, protecting you from accidentally locking your team out.
• •This release is internal groundwork: no page changes, no new customer-facing features, and nothing about your trips, subscription, or settings is affected. If you do not use the organization API, you will see no difference.

Safer releases — every update is checked end to end before it reaches you, and a version that fails any check never goes live

• •Updates reach you more reliably: preparing a new version no longer depends on a long hand-off finishing first, so a release can no longer stall halfway through and leave you waiting for a fix that is ready.
• •Every new version is automatically verified before it is made live — the freshly built application is checked end-to-end against everything a working release needs, and refused if any check fails. A version that doesn't pass every check cannot go live.
• •Releases are now safer to run: a new version starts once and is confirmed working before it stays live, so a broken update stops instead of reaching you half-applied.
• •These changes are internal: no user-facing features changed, no new data is collected about you, and nothing about your trips, subscription, or settings is affected.

Concierge payment reliability — double-payment protection is now race-free at the database level, larger amounts can be paid online, and abandoned checkouts clear automatically

• •Double-payment protection is now enforced at the database level. If a payment is already in progress or completed for a booking, any further attempt to pay for that same booking is rejected with a clear "This request already has a payment in progress or completed" message — it is no longer possible for a double-click or page refresh to create two payments for the same request.
• •Online payments now support amounts from $0.50 up to $999,999.99, matching the payment provider's own limits. High-value bookings (for example a $15,000+ safari) can now be paid online instead of failing with an error.
• •Abandoned checkouts clear automatically. If you leave a payment page open without completing it — or your session is interrupted — the unfinished payment is automatically cleared once the checkout session expires (typically within 24 hours), so you can simply try again without contacting support. Your payment is never cleared while the checkout session is still active, eliminating any risk of a double charge.
• •If a payment amount is outside the supported range, you'll see a clear message explaining the payable range and asking you to contact your concierge, instead of a generic error.

Concierge payment processing — make one-off payments for confirmed bookings via Stripe Checkout, with status tracking, receipt support, and automatic rate limiting

• •You can now make secure one-off payments for your concierge bookings directly from the chat panel. When a booking is confirmed and requires payment, a "Make a Payment" button appears — click it to open a Stripe Checkout session, complete your payment, and return to Voyonder automatically.
• •Each payment is tracked with a clear status: pending (awaiting payment), processing (payment in progress), succeeded (paid successfully), failed (payment declined or error), or refunded (money returned). You can see the current status and payment history in the concierge chat panel — no more wondering whether a payment went through.
• •A Payment Summary card shows the amount paid, date, payment method (card type and last four digits), and a description of what the payment covers. Refunded payments show the refund amount and date.
• •Payment status badges appear alongside confirmed bookings in the concierge request list, so you can see at a glance which bookings are paid, unpaid, or refunded.
• •Payment receipts are sent automatically via email when a payment succeeds — you'll get a Stripe receipt for every completed concierge payment.
• •Payment history is available: visit any concierge request to see current and past payments, and the same records are available to your own integrations through Voyonder's API, scoped to your account.
• •Support for card and ACH (US bank account) payments is enabled automatically via Stripe's payment methods. The exact methods available depend on your location and the payment amount.
• •Behind the scenes: every payment record keeps a full audit trail — amount, method, date, and a reference from the payment provider — so refunds and disputes can be traced end to end. Payment status updates as soon as the provider confirms it, and refunds are reflected immediately.
• •Rate limiting: payment endpoints are automatically rate-limited to 20 requests per 60 seconds per IP address to protect your account. If you see a "Too many requests" message, wait a few seconds and try again — the limit resets continuously.
• •Checkout reliability: payment status tracking now has a status guard that prevents accidental status reversion. If a payment has been confirmed as successful, it cannot be accidentally reverted to a 'processing' state — giving you more reliable payment status information.

Search-engine optimization for public pages — better titles, descriptions, and sitemap coverage so travelers can find Voyonder more easily

• •The pricing, gallery, and login pages now have page-specific titles and search-engine-optimized descriptions. When these pages appear in search results, they show clear, relevant titles — "Pricing — Voyonder", "Travel Itinerary Gallery — Voyonder", "Sign In — Voyonder" — instead of generic fallback text.
• •The sitemap was updated to include four previously-missing public routes: the Roadmap, Documentation, Release Notes, and the Sample Rome 5-Day itinerary page. Search engines can now discover and index these pages.
• •The sign-in page now shows the correct title and preview when the page is shared as a link.
• •These are search-engine-facing changes only — no new user-facing features, no changes to how Voyonder works, no data collected about you, and nothing about your trips, subscription, or settings is affected.

Pricing page testing — we try a few layout and wording variants to learn which one helps travelers choose a plan

• •Some visitors see an alternate version of the pricing page while we test which layout and wording helps travelers choose a plan. Nothing about a plan's price changes: the price you see is the price for that plan, in every version.
• •What we are testing: a more prominent 'Start Planning Free' button, a short confirmation step before checkout, savings badges on the tier cards, the comparison table placed alongside the plans, and two ways of showing social proof — testimonials and headline numbers.
• •One version per visitor: whichever version you see, it stays the same on later visits, so the page does not switch layouts or offers between your visits.
• •Choosing a plan is unaffected — you can upgrade, downgrade, or cancel exactly as before, and nothing here changes what a plan costs.

Payments fixed — card payments now go through; a safety check that was wrongly blocking releases has been corrected

• •Fixed a bug where the credit-card form could appear blank or fail to load during subscription checkout. A configuration value the payment form needs was missing from the released build; it is now included. Subscriptions load and render correctly.
• •Release reliability: our automated safety check now validates exactly the configuration that ships with a release, so a completed release passes the check instead of being blocked by a mismatch between what was verified and what was published.
• •These are internal infrastructure fixes. No user-facing features changed, no new data is collected about you, and nothing about your trips, settings, or existing subscription is affected. If you experienced a blank checkout form when trying to subscribe, this release resolves it.

Behind-the-scenes release-safety hardening — every new version is checked automatically before it goes live, with no changes to how you use Voyonder

• •Every new version of Voyonder is now verified end-to-end before it goes live: if any part of that check fails, the release stops automatically before anything changes, and the version you are using keeps running untouched. A version that does not pass every check simply cannot reach you.
• •The pre-release checks now run the complete set of automated tests — including newer ones for analytics, research, and billing — instead of a fixed list that could quietly miss tests added later. More problems are caught before a release than before.
• •If the reference settings a release depends on are ever unavailable, the release is refused rather than going out with possibly outdated settings. Going out with something unverified is never the fallback.
• •These changes are internal: no user-facing features changed, no new data is collected about you, and nothing about your trips, subscription, or settings is affected.

Behind-the-scenes billing hardening — test payments are handled safely alongside real ones, no disruption to your billing or subscription

• •Voyonder now separates test payments from real ones with a separate verification key, so internal testing can never touch your billing data.
• •Safeguard: a test payment is confirmed to be a test but is never applied to your account — no accidental subscription changes, no stray billing updates, no side effects from test data.
• •These changes are internal: no user-facing features changed, no new data is collected about you, and nothing about your trips, subscription, or settings is affected. Real payments are processed exactly as before.
• •Behind-the-scenes preparation for future pricing tests — the pricing page can now show a share of visitors a different layout at a time. Nothing is running today: everyone sees the standard pricing page, no prices or display have changed, and this has no effect on your current experience.

Behind-the-scenes analytics reliability fixes — subscription completion is now reported exactly once, no changes to how you use Voyonder

• •Analytics hardening in preparation for launch: subscription completion tracking was firing twice for new subscribers — it now fires exactly once, from a single authoritative source, so conversion and funnel reporting is accurate.
• •Subscriber identity joining was tightened end-to-end: sessions now carry a stable user ID from their very first page view, and event identity follows the same rules everywhere, so analytics events connect to the right account reliably.
• •These changes are internal: no user-facing features changed, no new data is collected about you, and nothing about your trips, subscription, or settings is affected.

Reliability hardening for subscriptions and research — cleaner errors and a more robust billing upgrade path

• •Subscriptions: fixed a race condition where upgrading during a free trial could strand the new subscription — an older billing confirmation arriving late could be mistaken for a current one. Your upgrade is now matched to the right moment in time, so it always lands.
• •Research APIs: invalid search requests now return a clear 400 instead of a generic server error, and semantic search without an embedding provider returns a proper 503. Internal error details are no longer exposed in API responses.
• •These changes are safety and reliability fixes — no new user-facing features, no behavior changes to your trips or billing data.

Behind-the-scenes analytics and release-process hardening — no changes to how you use Voyonder

• •Voyonder's analytics foundation was hardened in preparation for launch: page-view tracking now fires exactly once per page, event identity is stable and correct (your internal user ID is always used for joining analytics events), and analytics configuration is verified automatically before every deploy.
• •The release process gained new safety gates — more automated checks before and after each release — so future updates reach you with fewer regressions.
• •These changes are internal: no user-facing features changed, no new data is collected about you, and nothing about your trips, subscription, or settings is affected.

Billing portal link fix — no more 500 errors for trial-only accounts, smarter portal routing for every subscription state

• •Fixed a bug where trial-only users (those still in their 7-day free trial) would see a 500 error when trying to access the billing portal from settings. The portal link now uses three-state logic: no subscription routes to settings, trial-only routes to settings, and active subscription routes to Stripe's secure billing portal — every state works correctly.
• •Stripe API errors are now wrapped with user-safe messages — if something goes wrong on the payment provider side, you'll see a clear message instead of a generic error.
• •No action needed from you. Existing subscriptions, trials, and payment methods are unaffected. The portal link continues to work as before for active subscribers.

Conversion tracking on pricing & subscribe flow, plus reliable Stripe billing event processing

• •Voyonder now tracks how travelers move through the pricing and subscription flow — which pages they visit, which CTAs they click, and where they convert or drop off. This helps us understand what's working and improve the experience.
• •We measure the steps of that journey — the pages visited, the buttons clicked, and where a purchase starts, completes, or fails — and the results are visible only to the Voyonder team, never shared externally.
• •Fixed a billing reliability issue where some Stripe events — subscription upgrades, cancellations, trial transitions, and invoice updates — could be silently dropped, so your account didn't always reflect what you paid for. Plan changes now apply reliably and promptly.
• •Added protection against event loss: if a billing event can't be processed, the payment provider is asked to retry it instead of treating it as delivered — nothing is lost in transit.
• •Previously announced a Discord community link in the footer; that link was removed in v0.2.66+ because it pointed to a server not owned by Voyonder.
• •No action needed from you. Existing plans, trials, and payment methods are unaffected; billing continues to work as before. Tracking is product-usage only — no payment card data is ever captured by analytics.

Reliability release — research requests recover automatically, updates deploy without the site going down, and www.voyonder.com redirects correctly

• •Research requests that get interrupted mid-processing — for example during a server restart — now recover on their own. A request never stays stuck in limbo: it is retried automatically and finishes, or the system recovers it on the next cycle.
• •Freshness checks on your gathered references now always run once research completes, so the 'outdated reference' flags stay accurate.
• •Duplicate-reference protection is now scoped per research request, so repeating the same question for different trips can no longer mix up their reference sets.
• •www.voyonder.com now correctly redirects to voyonder.com — if you visited the www subdomain before, you may have seen an error page; that's fixed.
• •Updates are safer: new versions of the site now start up with the settings they need by default, and interrupted background maintenance picks itself back up automatically — no more temporary outage or restart loop after an update.
• •No action needed from you. Existing research requests, trips, and references are unaffected.

Research Artifact Service — natural-language research queries, smarter travel detail recognition

• •Ask Sage research-style questions about your trip in plain language. Requests like 'hotels in Paris under $300 for 4 people' or 'flights to Tokyo in December' are now accepted and processed as structured research queries.
• •Smarter travel detail recognition — Voyonder automatically identifies destinations (airports and cities), dates and date ranges, budget limits, hotels and airlines, activity categories, and traveler counts from what you write, then uses those details to drive research and recommendations.
• •Organized research tracking — each research request gets a status you can check, and the supporting references it gathers are stored and reviewed as a per-trip collection, with automatic checks to flag outdated references.
• •Under the hood: research requests now run through a dedicated pipeline (entity resolution → research planning → reference gathering → freshness verification) instead of being handled ad hoc, which makes results more consistent and faster to refine.
• •Reliability fixes included: research routes are now reachable in production (routing fix), duplicate references are automatically de-duplicated, and a fix for a rare parsing edge case that could stall entity recognition.

Discord community, a case studies page, and more resilient releases

• •A Discord community link was briefly added to the footer; it was later removed because it pointed to a third-party server.
• •New Case Studies page at /case-studies — five draft case studies showcasing real Voyonder travel experiences: solo trip planning, couples getaways, group adventures, experienced travelers, and inspiration seekers.
• •Release reliability: a memory-pressure failure that could interrupt a release has been fixed, along with network-transfer improvements that keep a long release from dropping partway through.

Smarter activity discovery — AI-powered research with curated fallback suggestions, nothing to configure

• •Activity discovery is now driven by AI research with remembered results — destinations Sage has researched before return instantly, and new destinations get fresh suggestions in about 3 seconds.
• •Partner pricing and booking links from GetYourGuide and Viator are now an optional extra: activity suggestions work whether or not those partners can be reached, and when they can, you see real prices and booking links alongside Sage's recommendations.
• •A small set of curated activities (city walking tours, local food and culture tours) is always available as a last resort, so you'll see suggestions even when live research is not available.
• •Activity discovery works out of the box — there is nothing for you to connect or configure.
• •Activity results include estimated price ranges (no more "Free" surprises), and activity research now requires a signed-in account.
• •Destination input is now checked before Sage uses it — malformed or suspicious entries are rejected rather than sent along, and a destination that just failed isn't looked up over and over, so one failure no longer slows down the rest of your planning.

Stripe subscription tier sync hardening — your plan always reflects what you're paying for

• •Fixed a race condition where trial subscribers could be shown incorrect tier information after the trial period ends.
• •Stripe status mapping is now safer and more resilient — handles edge cases like deleted customers and mid-cycle changes.
• •Stale account references are repaired automatically when they are detected — during sign-in, on the billing page, or when a payment confirmation arrives.
• •Google sign-in redirects now behave consistently across all environments.

Legal page bug fixes — internal metadata stripped from /terms, address placeholder removed from /privacy

• •/terms no longer shows an editorial Author/Date/Status header above the policy text — the page now opens directly on the Terms of Service content.
• •/privacy Contact section no longer displays a '[company address]' placeholder — the unused address line is gone. Email (privacy@voyonder.com) remains the primary contact method.

Signup checkbox duplicate fix — single terms acceptance checkbox inside the form

• •Fixed a duplicate terms acceptance checkbox on the /join page — the checkbox that was outside the form has been removed, leaving a single, properly-bound checkbox inside the form.
• •The remaining checkbox now submits reliably and gives clear validation feedback.
• •Improved label click behavior (cursor: pointer, select-none) and fixed whitespace/entity encoding issues.

Domain reverted to voyonder.com — canonical domain restored

• •Domain reverted to voyonder.com — the planned move to voyonder.app was paused.
• •Support email addresses updated to @voyonder.com (support@, legal@, privacy@).

Domain migration to voyonder.app — consistent URLs across the entire site

• •All canonical URLs, Open Graph tags, Twitter cards, and schema.org metadata now use voyonder.app — no more mixed references to voyonder.com.
• •Homepage footer now includes Privacy Policy and Terms of Service links (the inline footer was replaced with the shared component).
• •Under the hood: the site's public address is now configurable, for future flexibility.
• •While the move to voyonder.app was being set up, the site also stayed reachable at voyonder.com, so existing links and bookmarks kept working.

Privacy Policy, Terms of Service, and customer-facing documentation — legal pages now live

• •New Privacy Policy and Terms of Service pages available at /privacy and /terms — linked from the footer on every page.
• •New customer-facing Documentation page at /documentation with getting started guides, Sage AI tips, subscription info, and troubleshooting — designed for users, not developers.
• •New Release Notes page at /documentation/releases — curated changelog of what's new in each version, written for customers.
• •Sign-up form now requires accepting the Terms of Service before creating an account — checkbox with links to full terms and privacy policy.
• •Footer redesigned with clear links to Documentation, Release Notes, Privacy Policy, Terms of Service, Pricing, and Gallery.

Stripe subscription sync fix — your tier now matches what you're paying for

• •Fixed a bug where some users saw the wrong subscription tier after signing up (e.g., Elite subscribers shown as Adventurer). Your account now correctly reflects your plan.
• •Improved reliability of Stripe customer account linking — stale references are automatically repaired when detected.
• •Subscription tier syncs at login, on billing page visits, and in the Stripe portal — so your plan always matches what you're paying for.

In-app support chat — get help without leaving Voyonder

• •New support chat widget available on every page after signing in — click the chat icon to ask questions, report issues, or get help.
• •AI-powered support chat can answer common questions and help troubleshoot issues. When the AI identifies a complex problem, it escalates to our team automatically.
• •Support tickets with reference numbers — every conversation creates a ticket you can reference in follow-ups.
• •Knowledge base integration means faster answers to common questions without waiting for a human.
• •New documentation: check /documentation for getting started guides, feature documentation, and troubleshooting tips.

Sage AI reliability improvements — faster responses, better error handling

• •Sage responses now have a 30-second timeout safeguard — if the AI service is slow, you'll get a cached response instead of a hanging spinner.
• •Improved error handling for temporary AI service disruptions — transient rate limits and server errors are handled gracefully without disrupting your planning session.

Sage AI routes fix — chat and model endpoints are now available

• •Fixed a release where Sage's chat could return a 'page not found' error. Chat now works as expected.
• •Clearer problem reports — a brief connection drop and a real AI outage are now told apart, so a passing blip no longer reads as Sage being down.

Better reliability monitoring — problems are spotted before they reach you

• •Voyonder now confirms the AI service is genuinely responding, not merely that the network can reach it, so an AI outage is noticed before it shows up in your planning.
• •Authentication failures, exhausted AI capacity and connectivity problems are now told apart, so the right fix can be applied quickly instead of guessing.
• •Low AI capacity now raises an alert well before it runs out, so capacity is topped up before anyone's planning is interrupted.
• •Fixed an issue that could cause page crashes when link previews for certain social media sites were generated.